Skip to main content
skill CX Codex

MVP Builder — Claude Code skill: what it does, how to install

MVP Builder cuts a product idea down to the smallest version worth shipping and keeps the agent from over-building. Feature matrix, five MVP patterns, a two-week plan.

MIT 165 installs ★ 39 updated 2025-12-25

Install into Claude Code · Skills CLI (Vercel) All methods and platforms ↓
npx skills add daffy0208/ai-dev-standards --skill mvp-builder -a claude-code
Open on GitHub

What MVP Builder does

The skill gives the agent one rule to work from: build the smallest thing that confirms or kills your riskiest assumption. Every feature idea lands in a P0/P1/P2/out-of-scope table, so the agent argues about scope instead of generating code. Five patterns follow, among them concierge, wizard of oz and landing page, each with what it validates and roughly how long it takes.

There is a stack decision tree for web, mobile, API, browser extension and CLI, a recommended MVP setup (React or Next.js, Supabase, Tailwind, Stripe Checkout), and anti-patterns to avoid: custom auth, admin panel first, scaling for a million users. The build plan walks day by day through two weeks and ends with a launch checklist and pass/fail numbers.

Know one thing before you follow it. The quality standards put tests and error monitoring in the skip-until-validation bucket. That fits a throwaway prototype. On a codebase that already takes real payments it points the agent the wrong way.

What it helps with

  • Sort a feature backlog into P0/P1/P2 before the first sprint
  • Pick an MVP shape that fits the idea: waitlist page, manual service, single feature
  • Choose a prototype stack without dragging in infrastructure you don't need
  • Lay out a two-week build and validation schedule
  • Push back on features someone wants built just in case

Example prompts for the agent

  • Sort these features into P0/P1/P2 and tell me what ships this week.
  • Should I test this idea with a landing page or with one working feature?
  • Write the two-week plan with a launch checklist and the numbers I need to hit.

How to install MVP Builder

1Skills CLI (Vercel)

npx skills add daffy0208/ai-dev-standards --skill mvp-builder -a claude-code

2Manually: put the files in place

~/.claude/skills/mvp-builder/SKILL.md

Copy the whole skill folder; for one project use .claude/skills/mvp-builder/

Step by step, with commands for each platform: How to install skills in Claude Code: five ways

Questions about MVP Builder

How do I install MVP Builder in Claude Code?

Run npx skills add daffy0208/ai-dev-standards --skill mvp-builder -a claude-code. The skill file lands at ~/.claude/skills/mvp-builder/SKILL.md.

What does MVP Builder do?

It steers the agent from a feature list to a shipped minimal product: prioritization matrix, five MVP patterns, stack picks, a two-week plan and validation metrics.

Does it work outside Claude?

Yes. Install commands exist for Codex, Cursor, GitHub Copilot, Gemini CLI and OpenCode, each placing the skill in that tool's own skills folder.

Source text

SKILL.md · MIT
---
name: MVP Builder
description: Rapid MVP development and feature prioritization for fast product validation. Use when building minimum viable products, prioritizing features, validating ideas quickly, or when users need to ship products fast while avoiding over-engineering.
version: 1.0.0
---

# MVP Builder

Ship MVPs in 1-2 weeks, not months.

## Core Principle

**Start with the smallest thing that proves/disproves your riskiest assumption.**

MVP = Minimum **Viable** Product, not Minimum **Pretty** Product.

## MVP Feature Matrix

Categorize every feature idea using this matrix:

| Category         | Definition                           | Action                |
| ---------------- | ------------------------------------ | --------------------- |
| **P0**           | Must have for core value proposition | Build now             |
| **P1**           | Important but can wait for v1.1      | Ship after validation |
| **P2**           | Nice to have, delight features       | Ship v2+              |
| **Out of Scope** | Not needed for validation            | Defer indefinitely    |

### Example: Task Management MVP

**P0 (Week 1):**

- Create task with title/description
- Mark task complete
- View task list
- Basic authentication

**P1 (Post-validation):**

- Due dates, priorities, reminders

**P2 (Future):**

- Team collaboration, file attachments, mobile app

**Out of Scope:**

- Gantt charts, time tracking, integrations

## 5 MVP Patterns

### 1. Concierge MVP

**Definition:** Manually deliver the service before building automation

**When to use:** Core value is service delivery, not technology

**Examples:**

- Food delivery → Take orders via WhatsApp, deliver yourself
- AI copywriter → Manually write copy for customers
- Scheduling tool → Coordinate meetings via email

**Time:** 1-3 days | **Validates:** People want the service

---

### 2. Wizard of Oz MVP

**Definition:** Interface looks automated, but humans operate it behind the scenes

**When to use:** Automation is expensive/complex to build

**Examples:**

- Zapier early days → Manually created integrations
- AI chatbot → Human answers, customer thinks it's AI

**Time:** 1 week | **Validates:** Users engage with interface

---

### 3. Landing Page MVP

**Definition:** Explain the product + collect emails (no product yet)

**When to use:** Testing demand before building anything

**Examples:**

- Dropbox → Video showing concept
- Buffer → Landing page before code existed

**Time:** 1-2 days | **Validates:** People sign up for waitlist

---

### 4. Single-Feature MVP

**Definition:** One feature that solves one problem

**When to use:** One feature delivers 80% of value

**Examples:**

- Twitter → Just post 140-character updates
- Instagram → Just share photos with filters
- Stripe → Just accept credit card payments

**Time:** 1-2 weeks | **Validates:** People use the core feature

---

### 5. Piecemeal MVP

**Definition:** Combine existing tools instead of building custom

**When to use:** You can cobble together a solution with existing tools

**Examples:**

- Typeform + Airtable + Zapier + Stripe
- No-code tools: Webflow, Bubble, Retool

**Time:** 2-5 days | **Validates:** Workflow works end-to-end

## Tech Stack Decision Tree

```
Is this a web app?
├─ YES
│  ├─ Need real-time?
│  │  ├─ YES → Next.js + Supabase + WebSockets
│  │  └─ NO → Remix + PostgreSQL
│  └─ Simple CRUD? → Supabase + React
└─ NO
   ├─ Mobile app? → React Native + Expo
   ├─ API only? → Express + PostgreSQL
   ├─ Chrome extension? → Vanilla JS + Chrome APIs
   └─ CLI tool? → Node.js or Python
```

**Recommended MVP Stack:**

- **Frontend:** React + Vite or Next.js
- **Backend:** Supabase (Postgres + Auth + Storage) or Express.js
- **Styling:** Tailwind CSS + shadcn/ui
- **Hosting:** Vercel/Netlify (frontend) + Railway/Fly.io (backend)
- **Auth:** Clerk or Supabase Auth
- **Payments:** Stripe Checkout

**Speed-Focused Tools:**

- Supabase (backend in 10 min)
- Vercel v0 (UI generation)
- Clerk (auth in 5 min)
- Stripe Checkout (payments in 20 min)

## Anti-Patterns to Avoid

❌ **Building features "just in case"** → Build when 3+ users request
❌ **Perfect design before launch** → Ship functional, ugly is fine
❌ **Over-engineering architecture** → Monolith is fine for MVP
❌ **Custom authentication** → Use Clerk, Auth0, or Supabase Auth
❌ **Building admin panel first** → Use database GUI (Retool/Supabase)
❌ **Mobile app before web** → Web first, always
❌ **Scaling for 1M users** → Build for 10 users, scale when needed

## MVP Quality Standards

### Must Have ✅

- Core feature works end-to-end
- Basic auth (login/signup)
- Deploys without crashing
- Mobile-responsive (doesn't need to be beautiful)
- Basic error handling

### Can Skip ⏸️

- Perfect UI/UX
- Email notifications
- Advanced features
- Analytics dashboard
- Error monitoring (add after validation)
- Tests (add after product-market fit)

## Build Process

### Week 1: Build Core Feature

**Days 1-2: Design + Setup**

- Sketch 3 screens (paper/Figma)
- Set up repo + database (3-5 tables max)
- Deploy infrastructure

**Days 3-4: Build**

- Authentication (use library, don't build)
- Core feature (1 user flow only)
- Basic UI (use component library)

**Day 5: Polish + Deploy**

- Fix critical bugs
- Deploy to production
- Share with 5 friends for feedback

### Week 2: Validate

**Days 1-2: Iterate**

- Fix issues from Week 1 feedback
- Add 1-2 critical missing features

**Days 3-4: Get Users**

- Share on social media
- Post in relevant communities
- Email 20 people personally

**Day 5: Analyze & Decide**

- Did 10+ people sign up?
- Did 3+ people use it 3+ times?
- Are 1-2 people willing to pay?

**Decision Point:**

- ✅ Yes to above → Build P1 features
- ❌ No → Pivot or kill project

## Launch Checklist

**Pre-Launch (1 hour):**

- [ ] Core user flow works end-to-end
- [ ] Sign up + login works
- [ ] Deployed with HTTPS
- [ ] Privacy policy + ToS (use generator)

**Launch Day:**

- [ ] Post on Twitter/LinkedIn with screenshot
- [ ] Share in 3-5 relevant communities
- [ ] Email 20 people personally

**Week 1 Post-Launch:**

- [ ] Reply to every piece of feedback
- [ ] Fix critical bugs within 24 hours
- [ ] User interview with 3-5 early users

## Success Metrics

**MVP validation criteria:**

- **10+ signups** in first week
- **3+ people** use it 3+ times
- **1-2 people** willing to pay

**If you hit these:** You might have something. Build P1 features.

**If you don't:** Pivot or move on. Don't invest months in something nobody wants.

## Real MVP Examples

**Successful minimal starts:**

- **Airbnb:** Photos of their apartment + PayPal link
- **Stripe:** Just a form to collect card details
- **Dropbox:** Video demo before building product
- **Uber:** iPhone app in San Francisco only
- **Facebook:** Harvard students only, basic profiles

All started much smaller than you think.

## Related Resources

**Related Skills:**

- `product-strategist` - For validating product-market fit
- `frontend-builder` - For building the UI
- `api-designer` - For backend API design
- `deployment-advisor` - For deployment decisions
- `go-to-market-planner` - For launch strategy

**Related Patterns:**

- `META/DECISION-FRAMEWORK.md` - Platform selection decision tree

**Related Playbooks:**

- `PLAYBOOKS/build-mvp.md` - Step-by-step MVP build procedure (when created)

## Quick Reference

**For experienced users:**

- [ ] Identify riskiest assumption
- [ ] Choose MVP pattern (Concierge/Wizard/Landing/Single-Feature/Piecemeal)
- [ ] Categorize features (P0/P1/P2/Out of Scope)
- [ ] Build P0 only (1-2 weeks max)
- [ ] Ship ugly but functional
- [ ] Validate with 10+ users
- [ ] Decide: build P1 or pivot

© daffy0208 · MIT · daffy0208/ai-dev-standards

Similar skills

All skills for Agent setup: memory, context, orchestration →

From the same set63

The whole set →
Security Architect Security Architect evaluates system designs with STRIDE threat modeling, checks code against OWASP flaws, and validates regulatory standards. CX Codex +1 175installs Focus Session Manager Focus Session Manager is a Claude Code skill that tracks focus sessions, escalates break reminders and intervenes when you code for more than 90 minutes without a break. CX Codex +1 167installs codex-review-workflow The codex-review-workflow skill runs Codex CLI reviews, applies fixes, and checks the code again. Use it when a feature needs automated validation or security checks. CX Codex +1 166installs Asset Manager Asset Manager structures project media folders, enforces asset naming standards, and provides scripts to optimize images and generate responsive WebP and AVIF files. CX Codex +1 165installs localization-engineer localization-engineer — a skill for internationalizing Next.js apps with next-intl. Helps set up translations, plural rules, date or currency formatting, and RTL layouts. CX Codex +1 163installs Multi-Agent Architect The Multi-Agent Architect skill helps design systems where specialized agents split work, communicate, and review results. It fits complex workflows with several decision points. CX Codex +1 162installs Product Strategist Product Strategist is a Claude Code skill for testing product ideas before development. It helps assess demand, choose features, and weigh building a solution against buying one. CX Codex +1 160installs PRP Generator PRP Generator turns a rough feature idea into a twelve-section requirements document that a developer and an AI agent can both work from. CX Codex +1 160installs

Project sponsors

Companies that keep this analytics open