blueprint
Plans blueprint.md, the design-blind layout payload a design consumes: a region tree plus screen flow that arranges surfaces before any visual identity is styled — structure only, composable under any design. Use when planning information architecture, page composition, screen inventory, or screen flow; arranging surfaces, blocks, or navigation; wireframing or validating a wireframe; drafting a layout plan from a brief or conversation. Not for visual identity or design tokens, copy or content, or rendering HTML.
What this skill does
# Blueprint Owns `blueprint.md` — the design-blind layout payload a design consumes: a YAML frontmatter holds the renderable region tree, and a markdown body narrates it with a screen map and per-surface rationale. Arrangement is orthogonal to visual identity: the same `blueprint.md` must hold under any design, so this skill plans structure only — information architecture, region layout, and screen flow — never colors, fonts, or tokens. ## Quick start Produces `blueprint.md`, the layout plan a design consumes. Operations: - **create** — author a fresh layout plan from conversation (surfaces, blocks, shapes, flow). → [create.md](references/create.md) - **validate** — check a wireframe or existing plan for IA, flow, and intent coherence. → [validate.md](references/validate.md) ## Discovery `discovery.md` runs before every operation — never skipped, never invoked directly. It checks existing context (an existing `blueprint.md`, the conversation, any brief the user provides) and routes by intent — author a plan, or check one. See [discovery.md](references/discovery.md). ## Operations | Operation | File | | --------- | ---- | | Author a fresh layout plan into blueprint.md | [create.md](references/create.md) | | Check a wireframe or plan for coherence | [validate.md](references/validate.md) | ## Artifact Produces and owns `docs/design/blueprint.md`. A **YAML frontmatter** carries the normative region tree (surfaces → blocks with shape hints) plus optional screen flow — what a downstream renderer parses to draw the low-fi wireframe. A **markdown body** narrates it: a screen map and the per-surface rationale a tree alone cannot hold. Block labels come from the conversation; shape hints come from a fixed set. Patch the frontmatter first, then the prose that describes it, so the two stay in sync. Before saving, self-check: the tree is well-formed and carries structure only — no colors, fonts, spacing, or tokens, no copy strings, and no requirement IDs (`fr-1`, `m1`, `j1`, `us-3`). It plans arrangement, nothing else. ## Inputs Plan from the conversation. Beyond that, the only inputs are what the user provides — a brief, a PRD, a description, or existing material they point to; nothing is auto-loaded. If the user hands over existing content or a prior plan, arrange against it; otherwise plan from intent. ## Guidelines - Plan structure only — never embed colors, fonts, spacing, or tokens. - Derive surfaces and topics from the conversation; no fixed project types. - Use free block labels; pick shape hints from the fixed set so the plan stays renderable. - Patch the frontmatter region tree first, then the body that narrates it, so the two stay in sync. - Ask one decision at a time when walking surfaces, blocks, and flow. - Keep content out — plan structure; never author or import copy, and never carry requirement IDs (`fr-1`, `m1`, `j1`).
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.