Vibe Coder’s Guide to MVP
Go from nothing to a shipped MVP in 30 minutes. You can vibe-code something that almost works. What you’re missing isn’t talent, it’s the confidence that it’s actually shippable. This guide hands your agent a stack of skills that turn “sort of works” into a real product, with auth, accessibility, security, design, and deploy.
Pick your agent
Both are excellent. The skills work in either.
Paste this into your agent
Open a fresh session and paste the prompt. The agent takes it from here.
I want to ship an MVP with your help. Two public repos exist to make this fast:
- Agent Skills: https://github.com/titan-alpha/vibe-coders-guide-to-mvp-skills
- Project Template: https://github.com/titan-alpha/vibe-coders-guide-to-mvp-starter (includes the skills at ./vibe-mvp/)
Start by asking me, in one short question, what I want you to do. Likely answers:
A) "Start a new project from scratch" — use the Project Template.
B) "Start a new project with just the skills" — use the Agent Skills only.
C) "Finish or harden a project I already have" — use the Agent Skills only, in my existing project.
Based on my answer:
1. Set up the working directory.
- For (A): ask where on disk to put it and what to call it, then:
`git clone https://github.com/titan-alpha/vibe-coders-guide-to-mvp-starter.git <name>`
cd into it. The skills are already at ./vibe-mvp/ — copy to .claude/skills/vibe-mvp/ so Claude Code auto-loads them.
- For (B): ask where on disk and what to call it, then create the directory and:
`git clone https://github.com/titan-alpha/vibe-coders-guide-to-mvp-skills.git skills-tmp && cp -r skills-tmp/vibe-mvp .claude/skills/vibe-mvp && rm -rf skills-tmp`
- For (C): ask for the path to the project. cd there and read enough of the repo (package.json, README, top-level structure, recent commits) to understand what's already built before suggesting anything. Then:
`git clone https://github.com/titan-alpha/vibe-coders-guide-to-mvp-skills.git skills-tmp && cp -r skills-tmp/vibe-mvp .claude/skills/vibe-mvp && rm -rf skills-tmp`
Do not touch existing code yet.
2. Open the entry-point skill at .claude/skills/vibe-mvp/SKILL.md and follow it from the top. It covers discovery, design, auth, AI, compliance, accessibility, security, performance, deploy, domain, e2e testing, ship, and deliverables.
- For new projects (A or B), work through every skill in order. If the template is in use, many features are already scaffolded — just toggle them on in .env.local when each skill enables them.
- For existing projects (C), treat each skill as a checkpoint: confirm with me what's already done and skip past it; only do the work that's actually missing.
3. Whenever the skills tell you to collect credentials (Vercel token, auth provider keys, etc.), store them in .env.local and read from there on subsequent runs. Never hardcode secrets in source.
4. Pause and ask me before any destructive action, any step that costs money, or any change that touches existing code in ways I might not expect.
Begin now by asking me A/B/C.Now go ship it.
Your agent has the skills, the entry point, and the prompt. It will dialogue with you about your idea and audience, and handle the rest.
The agent asks about audience, tone, and shape. You stay in the driver’s seat.
It writes the code, the tests, the headers, the deploy config. You review.
Code, secrets, and domain are on your machine and your accounts. No lock-in.