Accessibility
Accessibility testing and improvements
wicked-garden-qe-acceptance-test-reviewer
by mikeparcewski
Evaluates evidence artifacts against test plan assertions independently. CRITICAL ISOLATION: Receives ONLY evidence file paths. Never sees execution context. Catches semantic bugs that self-grading misses. Use when: acceptance test review, evidence evaluation, test verdict <example> Context: Executor produced evidence and it needs independent evaluation. user: "Review the evidence from the file upload acceptance tests and render a verdict." <commentary>Use acceptance-test-reviewer for independent, unbiased verdict on test evidence.</commentary> </example>
wicked-garden-product-a11y-expert
by mikeparcewski
Audit accessibility compliance - WCAG guidelines, keyboard navigation, screen reader support, color contrast, semantic HTML. Use when: accessibility audit, WCAG compliance, keyboard-navigation review, screen-reader support check, or dispatched as the a11y lens of the product skill's ux-review --focus all. NOT THIS WHEN: axe-core/pa11y must actually RUN and produce evidence artifacts + a ledger verdict row (a scenario-driven a11y test run) — use wicked-garden-qe-a11y-test-engineer (executor). THIS skill renders design/review-phase accessibility judgment; it does not write QE evidence.
wicked-garden-product-ux-review
by mikeparcewski
Use when evaluating UX quality — user flows, information architecture, user research synthesis, personas, and usability assessment. Also covers generative UX flow design from requirements. NOT for visual design consistency (use visual-review) or accessibility code audits (use product/accessibility).
wicked-garden-product-accessibility
by mikeparcewski
Use when auditing code for WCAG 2.1 AA compliance — keyboard navigation, ARIA patterns, color contrast, and semantic HTML. Produces prioritized remediation with code-level fixes. NOT for running automated a11y tools (use product:a11y command) or visual design review (use product/visual-review).
wicked-garden-engineering-frontend
by mikeparcewski
Frontend engineering specialist for React, CSS, browser APIs, component design, accessibility, and performance. This skill should be used when the user asks about UI implementation, component review, or frontend-specific questions. Use when: "build a React component", "CSS layout issue", "frontend performance", "browser API", "component design", "accessibility check", "responsive design"
impeccable-audit
by SebastiaanWouters
"Skills-only equivalent of impeccable.style /audit. Perform comprehensive audit of interface quality across accessibility, performance, theming, and responsive design. Generates detailed report of issues with severity ratings and recommendations. Use for frontend and UI design tasks."
database_design
by vuralserhat86
Schema tasarımı, migration stratejileri, indexing, query optimization ve database best practices.
design_components
by vuralserhat86
Button, card, input ve icon sizing kuralları. Component boyutlandırma standartları.
clerk_auth
by vuralserhat86
Clerk modern authentication, WebAuthn, passkeys ve social auth entegrasyonu rehberi.
browser-automation-agent
by besoeasy
Automate web browsers for AI agents using agent-browser CLI with deterministic element selection.
accessibility-checker
by armanzeroeight
Validate WCAG compliance, check screen reader support, and audit accessibility issues. Use when ensuring accessibility, fixing WCAG violations, or implementing inclusive design.
ux-design
by sebnow
"Use when designing user interfaces, improving UX, or creating design specifications. Enforces user-centered process, WCAG 2.1 AA accessibility, mobile-first approach. Triggers: 'design interface', 'improve UX', 'user experience', 'accessibility', 'responsive design', 'user flow'."
form-accessibility
by Bbeierle12
WCAG 2.2 AA compliance for forms, ARIA patterns, focus management, keyboard navigation, and screen reader support. Use when implementing accessible forms in any framework. The compliance foundation that ensures forms work for everyone.
kobalte
by joncrangle
Specialist in Kobalte, a headless, accessible UI component library for SolidJS. Focuses on accessibility (ARIA), composability, and styling unstyled primitives.
Forms Router
by Bbeierle12
Secure Auth Forms: Any framework + security + validation
forms-router
by Bbeierle12
Router for web form development. Use when creating forms, handling validation, user input, or data entry across React, Vue, or vanilla JavaScript. Routes to 7 specialized skills for accessibility, validation, security, UX patterns, and framework-specific implementations. Start here for form projects.
reactive-ui
by githubnext
Build or revise CAO dashboard UI with Dashboard Language, reusable UI elements, and the reactive.js framework.
platform-building
by Bbeierle12
Platform-specific building systems for mobile, VR, and accessibility. Use when implementing touch controls for building games, VR spatial input, colorblind-friendly feedback, or cross-platform building mechanics. Covers input adaptation and inclusive design patterns.
structure
by Owl-Listener
"Structure content for screen reader and assistive technology use. Chains: heading-structure, alt-text-design, table-accessibility, form-labelling. Use when building a new page, document, or content template and you want to get the structural accessibility right from the start."
review
by Owl-Listener
"Review content for accessibility across cognitive and literacy levels. Chains: readable-content, alt-text-design, heading-structure, link-text-design, table-accessibility, form-labelling, multimedia-accessibility. Use when auditing existing content for accessibility."
multimedia-accessibility
by Owl-Listener
"Design accessible video, audio, and multimedia content with captions, transcripts, and audio descriptions. Use when creating or reviewing video, audio, podcasts, webinars, animations, or any time-based media. Triggers on: captions, subtitles, transcript, audio description, video accessibility, podcast accessibility, multimedia, closed captions, sign language, media player, autoplay."
subscription-signin
by rolandcanyon-cmd
The standard, proven procedure for keeping Claude Code and Codex subscriptions signed in — Google-account profiles, normal-browser sign-in, repair, verification, and when to hand off. Use whenever a subscription shows "needs sign-in", a repair fails, or you set up a new account on a machine.
handoff
by Owl-Listener
"Generate an accessibility decision handoff for engineering. Chains: decision-documentation, compliance-mapping, accessibility-testing-strategy. Use when a design is ready for implementation and the engineering team needs clear accessibility specifications."
form-labelling
by Owl-Listener
"Design form labels, instructions, and grouping that work for screen readers and cognitive accessibility. Use when designing or reviewing forms, input fields, checkboxes, radio buttons, select menus, or any data entry interface. Triggers on: form label, label, input label, fieldset, legend, placeholder, form instructions, form group, radio group, checkbox group, required field, form accessibility."