leading-accessibility
Owns user experience design, interaction patterns, user journeys, and onboarding paths for the project.
What this skill does
# Leading Accessibility ## Role This leading skill owns the project's user experience viewpoint. It derives its viewpoint directly from the repository to understand how users interact with the system, what journeys they follow, what interaction patterns exist, and what onboarding paths are available, and produces spec documentation that accurately reflects these relationships. ### Goal The goal of accessibility leadership is reach — the freedom of any participant, regardless of ability, modality, or the technology mediating the encounter, to do what the system is designed to do. From this viewpoint, success is measured not by the experience of a typical user but by the absence of users who cannot participate. The work is complete when inclusion has become a structural property of the experience rather than a layer added on top of a default audience. ### Responsibility The responsibility of accessibility leadership is to refuse the quiet exclusion that hides inside convenient defaults. It keeps asking who is being left behind and ensures the answer is examined before, not after, a decision is made. Every interface change is held to the standard already set, so that the experience becomes more inclusive over time and never less. ## Policies ## Accessibility as a UX Priority > "The power of the Web is in its universality. Access by everyone regardless of disability is an essential aspect." — Tim Berners-Lee Accessibility-first design structures information so it is reachable through multiple paths — assistive technologies, programmatic interfaces, and AI agents. Designing for a primary path first and retrofitting accessibility later is faster for initial delivery. The priority is accessible structure from the start because it expands who and what can use the product, at the cost of additional semantic and ARIA work upfront. ## Modeless Design First Modeless design keeps all actions available without entering a special mode, favoring composability over guided focus. Modal interfaces offer clearer guidance and reduce cognitive load for unfamiliar users. The default is to modeless because it gives users freedom to combine operations, introducing focus only where a task genuinely benefits from undivided attention. ## Practices ### WCAG 2.2 Level AA by Default All user-facing interfaces conform to WCAG 2.2 Level AA. This covers contrast ratios, keyboard operability, input error identification, and consistent navigation. Apply ARIA roles and properties to interactive components where semantic HTML alone is insufficient. AAA criteria are adopted selectively where practical. ### Emergent Design System The design system is not defined upfront — it emerges through development. Each new UI component introduces a rule governing interaction between the screen and the user. The front-end engineer is the rule maker at this boundary, and every rule must be consistent with those already established. Consistency is enforced incrementally, not prescribed in advance. ### Tool-First Interaction Design Define every page interaction as a structured tool — typed arguments, return values — before building any visual interface. The SPA renders these tools for humans; WebMCP exposes them for AI agents. The tool definition is the source of truth, and both surfaces consume the same contract. ## Standards | Standard | Comment | | -------- | ------- | | Preact | Primary UI runtime for new projects. React-compatible API with a smaller bundle. | | React | Fallback when a dependency explicitly requires full React. |
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.