agentleFS
theintelligentmind00-droidtheintelligentmind00-droid/Solar-Ai/.claude/skills/vibe-build/SKILL.md

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

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
  1. Distinctive:

    If context is too long, summarize/compact before resetting.

    line 17
  2. Distinctive:

    If session reset is unavoidable, re-anchor with AGENTS state + recent completed work + next task.

    line 18
  3. Distinctive:

    Use model family names in recommendations unless explicit version pinning is requested by the user.

    line 22
  4. Distinctive:

    Check for required files:

    line 26
  5. Very specific:

    If missing, suggest running /vibe-agents first.

    line 33
  6. Distinctive:

    Read AGENTS.md to understand current phase and tasks

    line 41
  7. Distinctive:

    Wait for user approval before proceeding

    line 44
  8. Very specific:

    Follow patterns in agent_docs/code_patterns.md

    line 60
  9. Very specific:

    Use tech stack from agent_docs/tech_stack.md

    line 61
  10. Distinctive:

    Keep changes focused and minimal

    line 62
  11. Distinctive:

    Commit after each working feature

    line 63
  12. Very specific:

    Run tests: npm test (or equivalent)

    line 69
  13. Distinctive:

    Update AGENTS.md current state

    line 73
  14. Distinctive:

    Follow the phases in AGENTS.md:

    line 79
  15. Distinctive:

    Create basic project structure

    line 86
  16. Distinctive:

    Create database schema if needed

    line 91
  17. Distinctive:

    Run through launch checklist

    line 106
  18. Distinctive:

    Run dedicated security pass (auth, input validation, secrets/dependency checks)

    line 107
  19. Distinctive:

    Document any manual steps

    line 108
  20. Distinctive:

    After completing each feature, update AGENTS.md:

    line 123
  21. Distinctive:

    Don't apologize - just fix it

    line 144
  22. Distinctive:

    Do NOT delete files without confirmation

    line 156
  23. Distinctive:

    Do NOT change database schemas without backup plan

    line 157
  24. Distinctive:

    Do NOT add features outside current phase

    line 158
  25. Distinctive:

    Do NOT skip verification steps

    line 159
  26. Distinctive:

    Do NOT use deprecated patterns

    line 160
  27. Distinctive:

    Do NOT over-engineer simple features

    line 161
  28. Distinctive:

    If blocked or uncertain:

    line 165
  29. Distinctive:

    Ask ONE specific question

    line 169
  30. Distinctive:

    When the MVP is fully built:

    line 177

“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.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

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

  1. Continue in the active project session whenever possible.
  2. If context is too long, summarize/compact before resetting.
  3. 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:

  1. AGENTS.md - REQUIRED (master plan)
  2. agent_docs/ directory - REQUIRED (detailed specs)
  3. docs/PRD-*.md - Reference for requirements
  4. docs/TechDesign-*.md - Reference for implementation

If missing, suggest running /vibe-agents first.

Workflow: Plan -> Execute -> Verify

1. Plan Phase

Before any coding:

  1. Read AGENTS.md to understand current phase and tasks
  2. Load relevant agent_docs/ files for the current task
  3. Propose a brief implementation plan
  4. Wait for user approval before proceeding

Example:

Plan for: User Authentication

  1. Set up auth provider (Supabase/Firebase)
  2. Create login/signup components
  3. Add protected route wrapper
  4. Test login flow

Shall I proceed?

2. Execute Phase

After approval:

  1. Implement ONE feature at a time
  2. Follow patterns in agent_docs/code_patterns.md
  3. Use tech stack from agent_docs/tech_stack.md
  4. Keep changes focused and minimal
  5. Commit after each working feature

3. Verify Phase

After each feature:

  1. Run tests: npm test (or equivalent)
  2. Run linter: npm run lint
  3. Manual smoke test if needed
  4. Fix any issues before moving on
  5. Update AGENTS.md current 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

  1. Initialize project with chosen stack
  2. Set up development environment
  3. Configure database connection
  4. Set up authentication
  5. Create basic project structure

Phase 2: Core Features

Build each feature from the PRD:

  1. Identify the simplest implementation
  2. Create database schema if needed
  3. Build backend logic
  4. Create frontend components
  5. Connect and test end-to-end

Phase 3: Polish

  1. Add error handling
  2. Improve mobile responsiveness
  3. Add loading states
  4. Optimize performance
  5. Add analytics

Phase 4: Launch

  1. Deploy to production
  2. Set up monitoring
  3. Run through launch checklist
  4. Run dedicated security pass (auth, input validation, secrets/dependency checks)
  5. Document any manual steps

Communication Style

Be concise and action-oriented:

Good:

Created LoginForm.tsx with 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:** None

Mark completed items in the roadmap:

### Phase 2: Core Features
- [x] User authentication
- [ ] [Next feature]

Error Handling

If something breaks:

  1. Don't apologize - just fix it
  2. Explain briefly what went wrong
  3. Show the fix
  4. Verify it works
  5. 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:

  1. State what you're trying to do
  2. Explain what's unclear
  3. Ask ONE specific question
  4. 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:

  1. Share with 5-10 beta testers
  2. Collect feedback
  3. Prioritize v2 features

Congratulations on shipping your MVP!

Download now (ZIP)

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
What did you use it for? e.g. Reviewing pull requests in a Rails app

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.