prototype
Rapid UI prototyping — generates 3 visually distinct HTML/CSS components from a text prompt, each driven by a unique physical/material metaphor. Use when user runs /prototype, asks to "prototype a UI", "mock up a component", "generate HTML mockups", "create UI variations", "design exploration", "quick UI concept", or wants to see multiple visual approaches to a component. Also trigger when user says "show me different ways to build...", "explore different designs for...", or wants rapid visual exploration of a UI idea — even without saying "prototype" explicitly.
What this skill does
# Prototype
Generate 3 visually distinct, high-fidelity HTML/CSS UI components from a single text prompt. Each component adopts a unique design persona based on physical/material metaphors — producing genuinely different visual approaches, not just color swaps.
## Quick Start
Parse `$ARGUMENTS` for the component description, optional `--vary N` flag, and optional `--dir <path>`.
If `--vary N` is present, skip to the [Variation Workflow](#variation-workflow) section.
If the description is vague (e.g., "button", "form"), just generate — don't ask clarifying questions. The value of this skill is speed. Interpret vague prompts generously and produce something interesting.
Follow these 3 phases in order for new generation. Do not pause between phases or ask for confirmation — generate everything in one pass.
### Phase 1: Style Direction
Think of 3 distinct design direction names for the user's prompt. Each name uses a physical/material metaphor — never artist names, brands, or copyrighted references.
**Name pattern**: `[Adjective] + [Material/Process] + [Form/Action]`
**Tone guide** (invent your own, do not copy these):
- "Asymmetrical Rectilinear Blockwork" (Grid-heavy, primary pigments, thick structural strokes)
- "Grainy Risograph Layering" (Tactile paper texture, overprinted translucent inks, dithered gradients)
- "Kinetic Wireframe Suspension" (Floating silhouettes, thin balancing lines, organic primary shapes)
- "Spectral Prismatic Diffusion" (Glassmorphism, caustic refraction, soft-focus morphing gradients)
Each metaphor should imply fundamentally different CSS techniques — not just different colors. See the materiality-to-CSS mapping in [WORKFLOW.md](WORKFLOW.md).
### Phase 2: Artifact Generation
For each of the 3 style directions, generate a complete, self-contained HTML page.
**Scope**: Each artifact is a focused, single-screen component — typically 100-300 lines of HTML. Enough structure to demonstrate the design direction clearly, but limited to one viewport. Not a full multi-section website.
**Visual execution rules:**
1. **Materiality**: The style metaphor drives every CSS choice (e.g., Risograph → `feTurbulence` for grain, `mix-blend-mode: multiply` for ink layering)
2. **Typography**: Use Google Fonts via `<link>`. Pair a bold sans-serif with a refined monospace for data
3. **Motion**: Include subtle CSS animations — hover transitions, entry reveals, micro-interactions
4. **IP Safeguard**: No artist names, brand names, or trademarks anywhere in the output
5. **Layout**: Be bold with negative space and visual hierarchy. Avoid generic card grids
6. **Content**: Use realistic placeholder content (names, dates, numbers) — not lorem ipsum
**Output format**: Each artifact is a complete `<!DOCTYPE html>` page with:
- Inline `<style>` block (no external CSS files except Google Fonts)
- Complete HTML structure with realistic placeholder content
- Optional `<script>` for interactions
- No markdown fences — raw HTML only
### Phase 3: Output
1. Create output directory (default: `.prototype/`, or `--dir` value)
2. Write each artifact with position prefix: `01-{slug}-{style-slug}.html`, `02-...`, `03-...`
3. Write `manifest.json` mapping positions to filenames and style names
4. Generate `index.html` with all 3 artifacts displayed in iframes side-by-side
5. Print file paths and suggest: `open .prototype/index.html`
See [WORKFLOW.md](WORKFLOW.md) for the index page template, manifest format, and file naming details.
## Variation Workflow
When `--vary N` is passed (where N is 1, 2, or 3):
1. Read `manifest.json` from the output directory to find the Nth artifact
2. Read the existing artifact HTML file to understand the current design
3. Generate 3 radical conceptual variations using different physical metaphors
4. Each variation gets a unique persona name and complete HTML/CSS rewrite
5. Write variation files as `{original-slug}-var-1.html`, `-var-2.html`, `-var-3.html`
6. Update `index.html` to show variations
See [WORKFLOW.md](WORKFLOW.md) for the full variation workflow.
## References
- [WORKFLOW.md](WORKFLOW.md) — Detailed guidance, index page template, materiality-to-CSS mapping
- [EXAMPLES.md](EXAMPLES.md) — Usage examples and sample outputs
- [TROUBLESHOOTING.md](TROUBLESHOOTING.md) — Common issues and fixes
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.