accessibility-design-checker
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.
What this skill does
# Accessibility Design Checker Skill ## Instructions 1. Review design specifications for accessibility 2. Check color contrast ratios 3. Verify keyboard navigation support 4. Check screen reader compatibility 5. Review focus management 6. Verify touch target sizes 7. Return accessibility review with: - Accessibility compliance status - Issues found - Recommendations - WCAG level compliance ## Examples **Input:** Review design for accessibility **Output:** ```markdown ### Accessibility Review **Overall Compliance:** WCAG 2.1 Level AA ✓ **Color Contrast:** - Primary text on white: 4.5:1 ✓ (WCAG AA) - Secondary text on white: 4.2:1 ✗ (needs improvement) - Large text on primary: 3.1:1 ✓ (WCAG AA) - Recommendation: Increase secondary text contrast to 4.5:1 **Keyboard Navigation:** - All interactive elements keyboard accessible ✓ - Focus indicators visible ✓ - Tab order logical ✓ - Skip links present ✓ **Screen Reader Support:** - Semantic HTML structure ✓ - ARIA labels where needed ✓ - Alt text for images ✓ - Form labels properly associated ✓ **Touch Targets:** - All interactive elements ≥ 44x44px ✓ - Adequate spacing between touch targets ✓ **Text Resizing:** - Design works at 200% zoom ✓ - No horizontal scrolling required ✓ **Issues Found:** 1. Secondary text contrast below 4.5:1 (should be improved) 2. Missing ARIA label on icon-only button (needs label) **Recommendations:** - Increase secondary text color darkness - Add aria-label="Close" to icon button ``` ## Accessibility Areas to Check - **Color Contrast**: Text/background contrast ratios (WCAG AA: 4.5:1) - **Keyboard Navigation**: All interactive elements keyboard accessible - **Focus Indicators**: Visible focus states - **Screen Reader Support**: Semantic HTML, ARIA labels, alt text - **Touch Targets**: Minimum 44x44px for mobile - **Text Resizing**: Works at 200% zoom - **Reading Order**: Logical content order - **Form Labels**: Properly associated labels - **Error Messages**: Accessible error communication - **Skip Links**: Skip navigation links ## WCAG Compliance Levels - **Level A**: Basic accessibility (minimum) - **Level AA**: Standard compliance (recommended) - **Level AAA**: Enhanced accessibility (ideal) ## Common Issues - **Low Contrast**: Text/background contrast too low - **Missing Alt Text**: Images without descriptive alt text - **Missing Labels**: Form inputs without labels - **Small Touch Targets**: Interactive elements too small - **No Focus Indicators**: Missing visible focus states - **Poor Semantic Structure**: Incorrect HTML structure - **Keyboard Traps**: Elements that trap keyboard focus
Related in Design
contribute
IncludedLocal-only OSS contribution command center. Auto-refreshes the user's in-flight PR and issue state on invoke so conversations start with full context — no need to brief Claude on what's in flight. Helps the user find issues to contribute to on GitHub, builds per-repo dossiers of what each upstream expects (CLA, DCO, branch convention, AI policy, draft-first, review bots, issue templates), runs deterministic gates before any external action so AI-assisted contributions don't reach maintainers as slop. State is markdown-only: candidate files at ~/.contribute-system/candidates/, repo dossiers at ~/.contribute-system/research/, append-only event log at ~/.contribute-system/log.jsonl. No database, no cloud calls. Use when the user asks about their PRs / issues / contributions, wants to find new work to take on, claim an issue, build/refresh a repo's dossier, or draft a Design Issue or PR. Trigger with "/contribute", "what's my PR status", "find a contribution", "claim issue X", "draft a Design Issue for Y", "refresh dossier for Z".
architectural-analysis
IncludedUser-triggered deep architectural analysis of a codebase or scoped subtree across eight modes — information architecture, data flow, integration points, UI surfaces, interaction patterns, data model, control flow, and failure modes. This skill should be used when the user asks to "diagram this codebase," "map the architecture," "show the data flow," "give me an ERD," "trace control flow," "find the integration points," "verify the layout pattern," "audit the UX architecture," or any similar request whose primary deliverable is mermaid diagrams plus cited reports under docs/architecture/. Dispatches haiku/sonnet sub-agents in parallel for per-mode exploration, then verifies every citation mechanically before any node lands in a diagram. Not for one-off prose explanations of code (use code-explanation) or for high-level system design from scratch (use system-design).
mcp
IncludedModel Context Protocol (MCP) server development and tool management. Languages: Python, TypeScript. Capabilities: build MCP servers, integrate external APIs, discover/execute MCP tools, manage multi-server configs, design agent-centric tools. Actions: create, build, integrate, discover, execute, configure MCP servers/tools. Keywords: MCP, Model Context Protocol, MCP server, MCP tool, stdio transport, SSE transport, tool discovery, resource provider, prompt template, external API integration, Gemini CLI MCP, Claude MCP, agent tools, tool execution, server config. Use when: building MCP servers, integrating external APIs as MCP tools, discovering available MCP tools, executing MCP capabilities, configuring multi-server setups, designing tools for AI agents.
react-native-skia
IncludedDesign, build, debug, and optimise high-polish animated graphics in React Native or Expo using @shopify/react-native-skia, Reanimated, and Gesture Handler. Use when the user wants canvas-driven UI, shaders, paths, rich text, image filters, sprite fields, Skottie, video frames, snapshots, web CanvasKit setup, or performance tuning for custom motion-heavy elements such as loaders, hero art, cards, charts, progress indicators, particle systems, or gesture-driven surfaces. Also use when the user asks for fluid, glow, glass, blob, parallax, 60fps/120fps, or GPU-friendly animated effects in React Native, even if they do not explicitly say "Skia". Do not use for ordinary form/layout work with standard views.
plaid
IncludedProduct Led AI Development — guides founders from idea to launched product. Six capabilities: Idea (discover a product idea), Validate (pressure-test the idea against fatal flaws, problem reality, competition, and 2-week MVP feasibility), Plan (vision intake + document generation), Design (translate image references into a design.md spec), Launch (go-to-market strategy), and Build (roadmap execution). Use when someone says "PLAID", "plaid idea", "help me find an idea", "product idea", "idea from my business", "idea from my expertise", "plaid validate", "validate my idea", "pressure-test", "is this idea good", "find fatal flaws", "validate the problem", "plan a product", "define my vision", "generate a PRD", "product strategy", "plaid design", "design from image", "translate image to design", "create design.md", "extract design tokens", "plaid launch", "go-to-market", "launch plan", "GTM strategy", "launch playbook", "plaid build", "build the app", "start building", or "execute the roadmap".
nextjs-framer-motion-animations
IncludedAdds production-safe Motion for React or Framer Motion animations to Next.js apps, including reveal, hover and tap micro-interactions, whileInView, stagger, AnimatePresence, layout and layoutId transitions, reorder, scroll-linked UI, and lightweight route-content transitions. Use when the user asks to add, refactor, or debug Motion or Framer Motion in App Router or Pages Router codebases, especially around server/client boundaries, reduced motion, LazyMotion, bundle size, hydration, or route transitions. Avoid for GSAP-style timelines, WebGL or 3D scenes, heavy scroll storytelling, or CSS-only effects unless Motion is explicitly requested.