923건 · 관련도순
Accessibility testing toolkit using Selenium WebDriver 4+ with Java 21+ and axe-core engine. Use when asked to validate WCAG 2.1/2.2 compliance, scan pages or components for a11y violations, test keyboard navigation, audit color contrast, check ARIA semantics, generate accessibility reports, filter axe rules, debug screen reader issues, or implement POUR principles (perceivable, operable, understandable, robust).
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Design, audit, and improve accessibility and inclusive user experiences. Use when Codex is asked about WCAG, keyboard navigation, focus states, screen readers, ARIA, contrast, captions, reduced motion, forms, semantic HTML, accessible UI, game accessibility, inclusive design, accessibility QA, or compliance-sensitive accessibility work.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Auto-invoke when reviewing JSX with interactive elements, forms, buttons, or navigation. Enforces WCAG compliance and inclusive design.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Expert accessibility tester specializing in WCAG compliance, inclusive design, and universal access. Masters screen reader compatibility, keyboard navigation, and assistive technology integration with focus on creating barrier-free digital experiences.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Web accessibility specialist for WCAG compliance, ARIA implementation, and inclusive design. Use when auditing websites for accessibility issues, implementing WCAG 2.1 AA/AAA standards, testing with screen readers, or ensuring ADA compliance. Expert in semantic HTML, keyboard navigation, and assistive technology compatibility.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Implement WCAG 2.1 AA accessibility compliance with ARIA labels, keyboard navigation, screen reader support, and color contrast. Use when ensuring accessibility or fixing a11y issues.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Ensures designs meet accessibility requirements including WCAG compliance, color contrast, keyboard navigation, screen reader support, and focus management. Reviews designs for accessibility issues and provides recommendations.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Audit and improve web accessibility following WCAG 2.2 guidelines. Use when asked to "improve accessibility", "a11y audit", "WCAG compliance", "screen reader support", "keyboard navigation", or "make accessible".
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
This skill enables Claude to perform comprehensive accessibility audits. It uses the accessibility-test-scanner plugin to identify WCAG 2.1/2.2 compliance issues, validate ARIA attributes, check keyboard navigation, and assess screen reader compatibility. Use this skill when the user requests an accessibility scan, audit, or compliance check, or when terms like "WCAG", "ARIA", "screen reader", "accessibility testing", or "a11y" are mentioned. It provides actionable insights for improving web application accessibility.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Expert in web accessibility (WCAG 2.1/2.2 AA/AAA compliance), ARIA patterns, keyboard navigation, screen reader testing, color contrast, focus management, and automated accessibility testing
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Accessibility testing for web applications using Playwright (@playwright/test) with TypeScript and axe-core. Use when asked to write, run, or debug automated accessibility checks, keyboard navigation tests, focus management, ARIA/semantic validations, screen reader compatibility, or WCAG 2.1 Level AA compliance testing. Covers axe-core integration, POUR principles (perceivable, operable, understandable, robust), color contrast, form labels, landmarks, and accessible names.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Kotlin Multiplatform (KMP) / Compose Multiplatform (JetBrains, Kotlin) の公式リファレンス。 expect/actual, source set hierarchy, Multiplatform Gradle DSL, org.jetbrains.compose, Compose Resources (Res), Compose for iOS / Compose Desktop (Window, Tray, MenuBar, nativeDistributions) / Web, iOS 統合 (SwiftPM export, CocoaPods), Navigation / ViewModel / Lifecycle, Compose Hot Reload, Kotlin Toolchain, CI (GitHub Actions / TeamCity), Maven Central / npm 公開, AGP 9 移行, 互換性表。
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Design, refine, implement, or review application UI and user journeys with minimal controls, clear actions, shared components, realistic prototypes, and polished behavior. Use for product screens, forms, onboarding, navigation, settings, and chat/task interfaces; not backend-only work or general graphic design.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Use when the task requires automating a real browser from the terminal (navigation, form filling, snapshots, screenshots, data extraction, UI-flow debugging) via `playwright-cli` or the bundled wrapper script.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Guide for implementing smooth, native-feeling animations using React's View Transition API (`<ViewTransition>` component, `addTransitionType`, and CSS view transition pseudo-elements). Use this skill whenever the user wants to add page transitions, animate route changes, create shared element animations, animate enter/exit of components, animate list reorder, implement directional (forward/back) navigation animations, or integrate view transitions in Next.js. Also use when the user mentions view transitions, `startViewTransition`, `ViewTransition`, transition types, or asks about animating between UI states in React without third-party animation libraries.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Build mobile apps with React Native and Expo — navigation, platform-specific code, performance, and native modules.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Onboarding tour with AdwCarousel and navigation dots, skippable welcome screens. Use when adding a first-run tour or feature showcase to a GNOME app.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Make a GTK4/libadwaita app accessible — accessible labels and roles, tooltips on icon-only buttons, keyboard navigation, contrast, and testing with Orca/Accerciser. Use when fixing a11y issues or running the accessibility category of a HIG audit.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Design charts, metrics, and data tables that help users interpret and compare data. Use when the user asks to visualize data, choose chart types, improve dashboard analytics, or make data presentation accessible. Dashboard navigation and shell layout alone belong to add-ui or arrange.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Systematically audit and remediate accessibility issues in UI, focusing on keyboard navigation, screen reader support, color contrast, semantic HTML, ARIA usage, and motion sensitivity. Use when the user wants to improve accessibility, make a component accessible, fix WCAG violations, add keyboard support, or ensure screen reader compatibility.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Audit site navigation — find dead-end features, missing backlinks, and poor discoverability. Produces an improvement list, no code changes.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Guide for implementing smooth, native-feeling animations using React's View Transition API (`<ViewTransition>` component, `addTransitionType`, and CSS view transition pseudo-elements). Use this skill whenever the user wants to add page transitions, animate route changes, create shared element animations, animate enter/exit of components, animate list reorder, implement directional (forward/back) navigation animations, or integrate view transitions in Next.js. Also use when the user mentions view transitions, `startViewTransition`, `ViewTransition`, transition types, or asks about animating between UI states in React without third-party animation libraries.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Find external documentation, web sources, or remote code with citations. Local code navigation uses the configured code tools.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Google Maps and Mapbox integration for Flutter applications
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.