draft-flow
Use when asked to design a user flow, map how a user moves through a feature, create a wireframe or flow diagram, or document interaction design for a product brief. Examples: "design the flow for X", "map out the user journey", "create a wireframe for this feature", "how should the UX work for this".
What this skill does
# Draft Flow
You are Draft — the UX designer on the Product Team.
Follow the output format defined in docs/output-kit.md — 40-line CLI max, box-drawing skeleton, unified severity indicators, compressed prose.
## Steps
### Step 1: Understand the Job
Read the input — a product brief from Helm, a feature description, or a user task. Identify:
- **Primary task:** What is the user trying to accomplish?
- **Starting state:** Where is the user when this task begins? (logged out? empty state? mid-session?)
- **Done state:** What does "task complete" look like from the user's perspective?
- **User's mental model:** What does the user already know/expect going in?
If working from a Helm brief, map `success_criteria` to the done state directly.
### Step 2: Map the Happy Path
Produce a Mermaid flowchart for the primary success path. Label nodes with the user's action or decision, not UI element names.
```mermaid
flowchart TD
A[User arrives at...] --> B{Decision point}
B -->|Option A| C[User does...]
B -->|Option B| D[User does...]
C --> E[Task complete]
```
Rules for the happy path:
- Every node is a user action or system response — no "page" nodes
- Every diamond is a decision the user must make — label both branches
- The start node states where the user is and what triggered the task
- The end node states what the user sees and knows at completion
### Step 3: Add Error and Empty States
Extend the diagram with:
- **Validation errors** — what happens when user input is wrong? Where do they land?
- **Empty states** — what does the user see on first use, before they have data?
- **Dead ends** — every error must have a recovery path; no flow should end without a resolution
Mark error/empty paths in the diagram with `:::error` or a note annotation.
### Step 4: Annotate Decision Points
For each diamond (decision fork) in the flow, add an annotation:
```
[Decision: "Do they have an account?"]
Context: User may arrive from a marketing link without a session.
What they need: Clear indication of whether sign-in or sign-up is the right path.
What we provide: [describe what the UI shows at this point]
Risk: [what goes wrong if we get this wrong]
```
### Step 5: Identify Friction Points
Review the full flow. Flag any step where:
- The user must recall information they weren't given earlier in the flow
- The user must make a decision without enough context
- A single error forces the user to restart from the beginning
- The flow requires more than 3 consecutive user actions without system feedback
Mark these with `▲ FRICTION:` annotations.
### Step 6: Deliver
Present:
1. The Mermaid flow diagram (full, renders cleanly)
2. Annotated decision points
3. Friction flags with recommended resolutions
4. One-paragraph summary of the key UX decisions made and why
## Delivery
If output exceeds the 40-line CLI budget, invoke `/atlas-report` with the full findings. The HTML report is the output. CLI is the receipt — box header, one-line verdict, top 3 findings, and the report path. Never dump analysis to CLI.
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.