'accessibility' 검색 결과

Builds React Native and Expo apps in TypeScript — navigation with React Navigation or Expo Router, lists, forms, styling, gestures and animations with Reanimated, safe areas, accessibility and localization; networking with TanStack Query, response validation, persistence with MMKV, AsyncStorage, SQLite and secure storage; permissions, push notifications, deep links, background tasks, native modules and config plugins; performance with Hermes and the React profiler; and release with EAS Build, EAS Submit and EAS Update or bare Gradle and Xcode builds. Use when writing or changing React Native code, adding a native capability, configuring Expo, preparing a store build or an over-the-air update, or when the user asks how to do something in React Native, even if they do not name the library.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Works on Kotlin Multiplatform mobile projects with shared Kotlin source sets and Android/iOS targets. Use for architecture, tests, debugging, reviews, performance, security, accessibility, dependencies and releases when `org.jetbrains.kotlin.multiplatform` is applied; inspect actual targets, `commonMain`/`commonTest`, target source sets, Compose Multiplatform and the iOS framework/host app before giving platform advice.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Builds native iOS apps in Swift — SwiftUI and UIKit screens, state and data flow, NavigationStack, lists, forms and accessibility; networking with URLSession and Codable, persistence with SwiftData, Core Data, files and the Keychain; permissions, push notifications, universal links, background tasks, widgets, App Intents and StoreKit 2 purchases; performance with Instruments and MetricKit; and release with signing, TestFlight and App Store Connect. Use when writing or changing native iOS code, adding a platform feature, preparing a build for TestFlight or the App Store, or when the user asks how to do something on iOS, even if they do not name the framework.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

WCAG implementation: production-level semantic landmark, focus, keyboard, colors. Use when implementing, reviewing or testing wcag implementation for React, Vite, Next.js or Perfect_AI projects.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

VibeFarsi quality auditing: production-level item audit, accessibility, CSS conflicts. Use when implementing, reviewing or testing vibefarsi quality auditing for React, Vite, Next.js or Perfect_AI projects.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

UI visual audit: production-level screenshots, accessibility, alignment, density. Use when implementing, reviewing or testing ui visual audit for React, Vite, Next.js or Perfect_AI projects.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Accessible motion: production-level reduced motion, seizure prevention, pause controls. Use when implementing, reviewing or testing accessible motion for React, Vite, Next.js or Perfect_AI projects.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Color vision and contrast: production-level WCAG contrast on composited layers. Use when implementing, reviewing or testing color vision and contrast for React, Vite, Next.js or Perfect_AI projects.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Review or design FriendlyBet user experience, visual direction, mobile-first flows, premium sports interface, Hebrew/English copy fit, RTL behavior, accessibility, interaction patterns, and product UI polish. Use when a task touches screens, flows, layout, visual hierarchy, onboarding, prediction UX, share UX, or design quality.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Use when the user wants to design, redesign, shape, critique, audit, polish, clarify, distill, harden, optimize, adapt, animate, colorize, extract, or otherwise improve a frontend interface. Covers websites, landing pages, dashboards, product UI, app shells, components, forms, settings, onboarding, and empty states. Handles UX review, visual hierarchy, information architecture, cognitive load, accessibility, performance, responsive behavior, theming, anti-patterns, typography, fonts, spacing, layout, alignment, color, motion, micro-interactions, UX copy, error states, edge cases, i18n, and reusable design systems or tokens. Also use for bland designs that need to become bolder or more delightful, loud designs that should become quieter, live browser iteration on UI elements, or ambitious visual effects that should feel technically extraordinary. Not for backend-only or non-UI tasks.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Review UI code for Web Interface Guidelines compliance. Use when asked to "review my UI", "check accessibility", "audit design", "review UX", or "check my site against best practices".

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Analyzes genetic variant effects on gene expression (RNA-seq), chromatin accessibility (DNASE), histone marks (ChIP), and transcription factors using the AlphaGenome API. Use when the user asks about non-coding variant effects, pathogenicity, clinical significance, disease associations, functional effects, gene expression changes, splicing disruption, or regulatory effects in promoters and enhancers. Also use for resolving biological terms to tissue/cell-type ontologies (UBERON/CL) or analyzing variants in chr:pos:ref>alt format.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Review UI code for Web Interface Guidelines compliance. Use when asked to "review my UI", "check accessibility", "audit design", "review UX", or "check my site against best practices".

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Visual inspection of live websites to find and fix design issues. Use when reviewing UI layout/design, checking responsive design visually, detecting visual inconsistencies, or diagnosing CSS/accessibility problems at the source code level. Not for automated E2E testing.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Comprehensive web quality audit covering performance, accessibility, SEO, and best practices. Use when asked to "audit my site", "review web quality", "run lighthouse audit", "check page quality", or "optimize my website".

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Design and implement context-fit frontend interfaces with deliberate art direction, accessible interaction, responsive behavior, complete states, and rendered verification. Use when creating or substantially reworking pages, components, product workspaces, dashboards, marketing sites, editorial surfaces, commerce flows, or justified immersive experiences.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Expert en théorie des couleurs (palettes, contraste, accessibilité, couleurs de marque, psychologie des couleurs)

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Solves UI lock-in. Reverse engineers your existing UI, strips all layout/token decisions, preserves every hook, handler, and API call untouched, then rebuilds the UI from scratch with a fresh design system. Use /ui-restructure to fully redesign, --style apple|linear|minimal|dashboard for named styles, --mode layout|theme|grid for partial rebuilds, --god-mode to redesign from the user's perspective using 100-user mindset simulation and 6 UX principles, --keep-tokens to preserve your token system, --prompt for custom redesigns. Applies mandatory world-class polish: spring motion, 5-state micro-interactions, 8pt spacing grid, WCAG accessibility. Supports Next.js, React, Vue 3, Tailwind, CSS Modules, styled-components, shadcn.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Overhaul one app's UI against an audit: UX audit and UI review of the running app, current versus proposed design tokens, a before/after visual plan, a startcycle build, point fixes, accessibility and browser tests, delivered as a PR after GO. Use for "redesign this app", "design overhaul", "audit and fix the UI", "give the app a new look".

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Use when building React components, optimizing Next.js performance, implementing accessibility, or reviewing frontend code quality for modern web applications.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Use when choosing an animation engine, defining motion tokens, adding scroll effects or micro-interactions, or auditing motion for accessibility and performance. Covers engine selection (GSAP, Motion.dev, Anime.js, React-Spring, Three.js, CSS Native), DTCG motion tokens, and the anti-slop/a11y quality gate.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Japanese frontend and web design skill covering typography, vertical writing, form handling, accessibility (JIS X 8341-3), and common Japanese UI patterns. Triggers on requests for 日本語Webデザイン, フロントエンド, 和文タイポグラフィ, Japanese web design.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Liquid Glass material best practices for SwiftUI, UIKit, and AppKit on iOS 26+/macOS 26+ (Tahoe) through iOS 27/macOS 27. Use when implementing, reviewing, or migrating to glass: glassEffect, Glass variants (.regular/.clear/.identity), tint, interactive(), GlassEffectContainer, glassEffectUnion, toolbar glass, ToolbarSpacer, scrollEdgeEffectStyle, sharedBackgroundVisibility, tabBarMinimizeBehavior, backgroundExtensionEffect, NSGlassEffectView, UIGlassEffect, Tahoe window chrome, glass accessibility (Reduce Transparency/Increase Contrast), pre-26 Material fallbacks, UIDesignRequiresCompatibility. Also fires on symptoms: glass renders dark or muddy, glass looks like a flat tinted rectangle, glass button doesn't register taps, tap passes through glass, "'glassEffect' is only available in iOS 26.0 or newer", "ambiguous use of 'opacity'", "'cornerRadius' was deprecated", glass looks different in simulator vs device, screenshots of glass UI don't match. For glass animation, morphing, glassEffectID, transitions, Metal shaders, or performance profiling use the liquid-glass-motion skill instead.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

When designing and implementing web interfaces to ensure they are usable by everyone.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.