mvp
Guides the founder through designing and optionally building the simplest MVP or prototype that validates their current hypotheses. Use when the founder wants to build something to test assumptions, discusses what to build next, wants to interpret results from a live MVP, or is deciding whether the current approach is still right. Also use when a founder proposes something to build — the skill will check whether the proposed form is the simplest thing that generates honest signal.
What this skill does
# MVP / Prototype Help the founder figure out the simplest thing worth building to validate their remaining assumptions — and optionally scaffold and deploy it. The central job of this skill is to be a principled counterweight to over-engineering. Most founders want to build more than they need to test what they don't yet know. This skill reads what's been validated, identifies the riskiest untested assumptions, and argues for the form of MVP that generates honest signal with the least build effort. Two modes: 1. **Design conversation** — structured dialogue that produces `startup/mvp-plan.md`: what to build, why this form, which hypotheses it tests, and what success looks like 2. **Scaffold and deploy** — optional Layer 2 reference that writes code to the project root and deploys using Vercel MCP, Supabase MCP, and the v0 Platform API --- ## Before you start Read `startup/core.md` and scan `startup/hypotheses/` to understand what's been established and what's still untested. Check `startup/interviews/` and `startup/surveys/` for evidence gathered so far. No directory scaffolding is needed — `startup/` is created during project initialization. --- ## When no `startup/mvp-plan.md` exists Load the reference file that runs the design conversation: ``` .claude/skills/mvp/references/initial-mvp-design.md ``` The reference file's instructions take over from this point. --- ## When `startup/mvp-plan.md` exists Read it for context. Infer intent from the conversation — don't ask "what do you want to do?" **If the founder is discussing results or what they're seeing:** Handle inline. Read the plan to understand what was built, what hypotheses were being tested, and what the success criteria were. Also check `startup/interviews/` and `startup/surveys/` for any evidence collected since the MVP launched — this context informs the assessment. Ask what they're seeing — numbers, anecdotes, surprises. Compare against the success criteria and give a frank read: - **Confirmed** — signal clearly supports the hypothesis; route updates through the `hypotheses` skill - **Contradicted** — signal clearly runs against it; route updates through the `hypotheses` skill - **Inconclusive** — make the distinction explicit: "the hypothesis is probably wrong" is different from "the experiment didn't reach the right audience or ran too short." The first warrants invalidating the hypothesis; the second warrants redesigning the experiment, not changing hypothesis state. Update the `## Experiments Log` in `mvp-plan.md` with what was learned (dated entry). If the plan needs to evolve, propose changes and get confirmation before writing back. **If the founder wants to iterate or pivot the experiment:** Discuss what's changed. Propose what the next experiment should look like. Before overwriting the plan, move the current success criteria and outcome into the `## Experiments Log` as a completed entry. Then update `## What We're Building`, `## Why This Form`, `## Hypotheses Being Tested`, `## Success Criteria`, and `## Distribution Plan` with the new experiment. Propose the full updated content before writing. Get confirmation. **If the founder wants to scaffold and deploy:** - `status: ready` and a deployable form (landing page, demo, simple app) → load: ``` .claude/skills/mvp/references/scaffold-and-deploy.md ``` - `status: designing` → suggest finishing the design conversation first; offer to continue it - `status: live` → ask whether they want to redeploy or add something new; if yes, load the scaffold reference **If a founder proposes building something without a prior design conversation:** Read the existing hypotheses. Brief honest check (2–3 sentences): is the proposed form the simplest thing that would test the riskiest untested assumptions? Share the assessment before proceeding — not a gate, just an informed nudge. **If the founder wants to archive:** Archiving marks this MVP track as closed — the plan remains for reference but is no longer the active experiment. Read the file. Set `status: archived`, `last_updated: today`. Add a final log entry summarising the experiment outcome. Propose changes, get confirmation, write back. --- ## After saving `startup/mvp-plan.md` Briefly confirm: "Saved to `startup/mvp-plan.md`." Mention natural next steps without pushing: - `status: ready` and deployable form → "Ready to scaffold and deploy — just say the word" - `status: live` → "When you have results, come back and we'll assess them against the success criteria" - Running interviews or surveys in parallel often produces richer validation than the MVP alone
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.