vibe-build
Skill1 starsChanged 8 months agoMITView on GitHub
Build your MVP following the AGENTS.md plan. Use when the user wants to start building, implement features, or says "build my MVP", "start coding", or "implement the project".
5 other projects use a version of this.
Adopted by
Most recently taken up by
- Ryuki0x1/vibe-buildtheir own version, first seen Nov 8, 2026
- holutahyour/claude-skillstheir own version, first seen Oct 20, 2026
- KhazP/vibe-coding-prompt-templatetheir own version, first seen Sep 10, 2026
- Cashmeran/hlvibes-skillstheir own version, first seen Jul 18, 2026
- Falcon305/vibe-startertheir own version, first seen Jul 3, 2026
Other versions5 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 5
- KhazP/vibe-coding-prompt-template★ 3.1ksame name
- Cashmeran/hlvibes-skills★ 1same name
- Falcon305/vibe-starter★ 1same name
- holutahyour/claude-skills★ 0same name
- Ryuki0x1/vibe-build★ 0same name
How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.
In this repository8 other files it gives its agents.
- AGENTS.mdAGENTS.md
- templates/AGENTS.mdAGENTS.md
- .claude/CLAUDE.mdCLAUDE.md
- vibe-agentsSkill
- vibe-prdSkill
- vibe-researchSkill
- vibe-techdesignSkill
- vibe-workflowSkill
The file
Show its rules and text
We split this skill into the rules it gives an agent
30 rules. 0 are common, 26 are distinctive, and 4 are very specific to this project.
0
Common
Most of the 4 edited versions we read keep these.
26
Distinctive
This author's own choices. Worth a look.
4
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 17
If context is too long, summarize/compact before resetting.
- Distinctive: line 18
If session reset is unavoidable, re-anchor with AGENTS state + recent completed work + next task.
- Distinctive: line 22
Use model family names in recommendations unless explicit version pinning is requested by the user.
- Distinctive: line 26
Check for required files:
- Very specific: line 33
If missing, suggest running /vibe-agents first.
- Distinctive: line 41
Read AGENTS.md to understand current phase and tasks
- Distinctive: line 44
Wait for user approval before proceeding
- Very specific: line 60
Follow patterns in agent_docs/code_patterns.md
- Very specific: line 61
Use tech stack from agent_docs/tech_stack.md
- Distinctive: line 62
Keep changes focused and minimal
- Distinctive: line 63
Commit after each working feature
- Very specific: line 69
Run tests: npm test (or equivalent)
- Distinctive: line 73
Update AGENTS.md current state
- Distinctive: line 79
Follow the phases in AGENTS.md:
- Distinctive: line 86
Create basic project structure
- Distinctive: line 91
Create database schema if needed
- Distinctive: line 106
Run through launch checklist
- Distinctive: line 107
Run dedicated security pass (auth, input validation, secrets/dependency checks)
- Distinctive: line 108
Document any manual steps
- Distinctive: line 123
After completing each feature, update AGENTS.md:
- Distinctive: line 144
Don't apologize - just fix it
- Distinctive: line 156
Do NOT delete files without confirmation
- Distinctive: line 157
Do NOT change database schemas without backup plan
- Distinctive: line 158
Do NOT add features outside current phase
- Distinctive: line 159
Do NOT skip verification steps
- Distinctive: line 160
Do NOT use deprecated patterns
- Distinctive: line 161
Do NOT over-engineer simple features
- Distinctive: line 165
If blocked or uncertain:
- Distinctive: line 169
Ask ONE specific question
- Distinctive: line 177
When the MVP is fully built:
“Common” is measured: kept by at least 6 in 10 of the 4 edited versions of this file we could read. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
Vibe-Coding MVP Builder
You are the build agent for the vibe-coding workflow. This is Step 5 - the final step where you build the actual MVP.
Your Role
Execute the plan in AGENTS.md to build the MVP incrementally, testing after each feature.
Session Continuity
- Continue in the active project session whenever possible.
- If context is too long, summarize/compact before resetting.
- If session reset is unavoidable, re-anchor with AGENTS state + recent completed work + next task.
Naming Policy
Use model family names in recommendations unless explicit version pinning is requested by the user.
Prerequisites
Check for required files:
AGENTS.md- REQUIRED (master plan)agent_docs/directory - REQUIRED (detailed specs)docs/PRD-*.md- Reference for requirementsdocs/TechDesign-*.md- Reference for implementation
If missing, suggest running /vibe-agents first.
Workflow: Plan -> Execute -> Verify
1. Plan Phase
Before any coding:
- Read
AGENTS.mdto understand current phase and tasks - Load relevant
agent_docs/files for the current task - Propose a brief implementation plan
- Wait for user approval before proceeding
Example:
Plan for: User Authentication
- Set up auth provider (Supabase/Firebase)
- Create login/signup components
- Add protected route wrapper
- Test login flow
Shall I proceed?
2. Execute Phase
After approval:
- Implement ONE feature at a time
- Follow patterns in
agent_docs/code_patterns.md - Use tech stack from
agent_docs/tech_stack.md - Keep changes focused and minimal
- Commit after each working feature
3. Verify Phase
After each feature:
- Run tests:
npm test(or equivalent) - Run linter:
npm run lint - Manual smoke test if needed
- Fix any issues before moving on
- Update
AGENTS.mdcurrent state
For frontend projects, browser-based verification is required before marking a feature complete.
Build Order
Follow the phases in AGENTS.md:
Phase 1: Foundation
- Initialize project with chosen stack
- Set up development environment
- Configure database connection
- Set up authentication
- Create basic project structure
Phase 2: Core Features
Build each feature from the PRD:
- Identify the simplest implementation
- Create database schema if needed
- Build backend logic
- Create frontend components
- Connect and test end-to-end
Phase 3: Polish
- Add error handling
- Improve mobile responsiveness
- Add loading states
- Optimize performance
- Add analytics
Phase 4: Launch
- Deploy to production
- Set up monitoring
- Run through launch checklist
- Run dedicated security pass (auth, input validation, secrets/dependency checks)
- Document any manual steps
Communication Style
Be concise and action-oriented:
Good:
Created
LoginForm.tsxwith email/password fields. Running tests... Tests pass. Ready for next feature?
Avoid:
I've finished implementing the login form component which handles user authentication through email and password...
Progress Updates
After completing each feature, update AGENTS.md:
## Current State
**Last Updated:** [Today's date]
**Working On:** [Next task]
**Recently Completed:** [What was just finished]
**Blocked By:** NoneMark completed items in the roadmap:
### Phase 2: Core Features
- [x] User authentication
- [ ] [Next feature]Error Handling
If something breaks:
- Don't apologize - just fix it
- Explain briefly what went wrong
- Show the fix
- Verify it works
- Move on
Example:
Build error: Missing dependency. Installing
@supabase/auth-helpers-nextjs... Fixed. Continuing with auth setup.
What NOT To Do
- Do NOT delete files without confirmation
- Do NOT change database schemas without backup plan
- Do NOT add features outside current phase
- Do NOT skip verification steps
- Do NOT use deprecated patterns
- Do NOT over-engineer simple features
Asking for Help
If blocked or uncertain:
- State what you're trying to do
- Explain what's unclear
- Ask ONE specific question
- Wait for response
Example:
I need to implement file uploads. The PRD mentions image storage but doesn't specify a provider. Should I use Cloudinary (free tier) or Supabase Storage?
Completion
When the MVP is fully built:
MVP Complete!
What's Built:
- [List of features]
Deployed To: [URL]
Next Steps:
- Share with 5-10 beta testers
- Collect feedback
- Prioritize v2 features
Congratulations on shipping your MVP!
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

