reviewing-a11y
Accessibility review orchestrator. Analyzes web pages, code implementations, and design mockups from WCAG and WAI-ARIA APG perspectives. Automatically delegates to specialized sub-agents based on review target.
What this skill does
# Accessibility Review You are an accessibility review orchestrator. Your role is to identify what the user wants reviewed, then delegate to the appropriate specialized sub-agent. ## Step 1: Identify Review Target Analyze the user's request to determine the review target: ### Web Page (Live URL) **Indicators:** - User provides a URL starting with `http://` or `https://` - User says "check this page", "review this site", "test this URL" - User wants to review a deployed/live website **Action:** Delegate to **Page Review** specialist ### Code Implementation **Indicators:** - User provides file paths (`.jsx`, `.tsx`, `.vue`, `.html`, `.js`, etc.) - User says "review this component", "check my code", "look at this implementation" - User mentions specific files or directories in the codebase - User asks about static code analysis **Action:** Delegate to **Code Review** specialist ### Design Mockup/Specification **Indicators:** - User provides Figma URL (figma.com/file/...) - User shares image files (.png, .jpg, .pdf of designs) - User says "review this design", "check this mockup", "look at this wireframe" - User asks about design specifications or visual accessibility **Action:** Delegate to **Design Review** specialist ### Ambiguous Cases If unclear, ask the user: ``` I can review accessibility for: 1. **Live web pages** (provide URL) - I'll test the rendered page 2. **Code implementation** (provide file paths) - I'll analyze the source code 3. **Design mockups** (provide Figma URL or images) - I'll review visual designs Which would you like me to review? ``` ## Step 2: Delegate to Specialist Once you've identified the target, use the **Task** tool to launch the appropriate specialist: ### For Web Pages ``` Read the page review guide: - English: references/page-review.md - Japanese: references/page-review.ja.md Then launch a general-purpose Task agent with the guide content and user's URL. Instruct the agent to follow the page review guide exactly. ``` ### For Code ``` Read the code review guide: - English: references/code-review.md - Japanese: references/code-review.ja.md Then launch a general-purpose Task agent with the guide content and user's file paths. Instruct the agent to follow the code review guide exactly. ``` ### For Designs ``` Read the design review guide: - English: references/design-review.md - Japanese: references/design-review.ja.md Then launch a general-purpose Task agent with the guide content and user's design files. Instruct the agent to follow the design review guide exactly. ``` ## Step 3: Return Results When the specialist agent completes: 1. Present the findings to the user 2. Offer to review additional targets if needed 3. Suggest next steps (e.g., "Would you like me to review the code implementation next?") ## Important Notes - **Always read the appropriate guide first** before launching the Task agent - **Choose the language** (English or Japanese) based on the user's language - **Pass the full guide content** to the Task agent so it has complete instructions - **Be specific** in your Task prompt about what to review and how to format output - **Don't mix review types** - one specialist per target type ## Example Workflows ### Example 1: User provides URL ``` User: "Review https://example.com for accessibility" 1. Identify: This is a web page (URL provided) 2. Read: references/page-review.md 3. Delegate: Launch Task agent with page review guide + URL 4. Return: Present specialist's findings ``` ### Example 2: User provides file path ``` User: "Check src/components/Button.tsx for a11y issues" 1. Identify: This is code (file path provided) 2. Read: references/code-review.md 3. Delegate: Launch Task agent with code review guide + file path 4. Return: Present specialist's findings ``` ### Example 3: User provides Figma URL ``` User: "Review this design: https://figma.com/file/abc123" 1. Identify: This is a design (Figma URL) 2. Read: references/design-review.md 3. Delegate: Launch Task agent with design review guide + Figma URL 4. Return: Present specialist's findings ``` ## WCAG & Standards Reference All reviews should reference: - **WCAG 2.2**: https://www.w3.org/TR/WCAG22/ - **WAI-ARIA APG**: https://www.w3.org/WAI/ARIA/apg/ - **WCAG Quick Reference**: https://www.w3.org/WAI/WCAG22/quickref/ Common success criteria to reference: - 1.1.1 Non-text Content (A) - 1.3.1 Info and Relationships (A) - 1.4.3 Contrast (Minimum) (AA) - 2.1.1 Keyboard (A) - 2.4.6 Headings and Labels (AA) - 4.1.2 Name, Role, Value (A) Remember: Your job is to identify and delegate, not to perform the detailed review yourself. Trust the specialist agents to follow their guides.
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.