frontend-design-ui-ux
Produce implementation-ready UX and UI specifications: user flows, states, component briefs, design tokens, accessibility constraints, and handoff guidance for frontend engineering agents. Use for new features, redesigns, or design-system work where implementation should follow a clear product and interaction spec.
What this skill does
<EXTREMELY-IMPORTANT> This is a design-spec skill, not an implementation skill. Non-negotiable rules: 1. Understand users, context, and states before proposing screens. 2. Specify flows, states, accessibility, and responsiveness, not just visuals. 3. Reuse the templates in `references/` instead of inventing new handoff formats. 4. Keep implementation handoff concrete enough that an engineering agent can build from it. 5. Do not start coding the UI from this skill. </EXTREMELY-IMPORTANT> # frontend-design-ui-ux ## Inputs - `$request`: Feature, page, component, or UX problem to design ## Goal Produce a design handoff that covers: - user goals - flow and state model - component structure - design tokens - accessibility and responsive behavior - target engineering handoff ## Step 0: Discovery Resolve: - target users - product goal - device and usage context - existing design-system or product constraints - accessibility expectations If the problem statement is underspecified, ask before designing. **Success criteria**: The design problem is framed in user and product terms, not just screens. ## Step 1: Model flows and states Document: - primary user journey - edge cases - loading, empty, partial, success, and error states - key decisions or branching points Use `references/user-flow-template.md` when writing flow documentation. **Success criteria**: The design covers behavior across states, not just the happy path. ## Step 2: Specify components and interaction rules For the needed components, define: - purpose - variants - props or data needs - states - interaction feedback - responsive behavior - accessibility requirements Use `references/component-spec-template.md` for structured component briefs. **Success criteria**: The engineering handoff is concrete enough to implement without guessing. ## Step 3: Define tokens and system-level decisions Specify only the tokens and conventions the feature actually needs: - color roles - typography hierarchy - spacing and layout rhythm - motion and feedback rules - semantic states such as success, warning, danger, disabled Use `references/design-tokens-template.md` when a token artifact is required. **Success criteria**: The spec encodes reusable system decisions, not just one-off styling notes. ## Step 4: Handoff to the right engineering surface ### Agent Selection | Criteria | Target Agent | |----------|-------------| | Server-side rendering needed | `nextjs-senior-engineer` | | SEO critical | `nextjs-senior-engineer` | | App Router / Server Components | `nextjs-senior-engineer` | | API routes / Server Actions | `nextjs-senior-engineer` | | Pure SPA / client-only | `react-vite-tailwind-engineer` | | CLI with web UI | `react-vite-tailwind-engineer` | | Electron/Tauri app | `react-vite-tailwind-engineer` | | Static site with no SSR | Either (ask user) | | Unclear | Ask user | State: - which implementation target and why it fits - the acceptance criteria for engineering handoff **Success criteria**: Another agent can pick up the design package and implement it directly. ## Guardrails - Do not implement production UI code from this skill. - Do not skip accessibility, state coverage, or responsive behavior. - Do not produce vague design prose when a concrete artifact is needed. - Do not ignore existing product patterns unless the user asked for a redesign. ## When To Load References - `references/user-flow-template.md` Use for user journeys and acceptance flow documentation. - `references/component-spec-template.md` Use for component briefs and interface contracts. - `references/design-tokens-template.md` Use when the task requires tokenized styling decisions or system handoff. ## Output Contract Report or write: 1. user and context summary 2. flows and states 3. component specs 4. design tokens or styling rules if needed 5. handoff target and implementation acceptance criteria
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.