Vibe build

--- name: vibe-build description: Build your MVP following the AGENTS.md plan. Use this when the user wants to start building, implement features, or says "build my MVP," "start coding," or "implement the project." --- # 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 at AGENTS.md to build the MVP incrementally, testing after each feature. ## Session Continuity 1. Continue in the active project session whenever possible. 2. If the context is too long, summarize or condense it before resetting. 3. If a session reset is unavoidable, re-anchor with the AGENTS state, recent completed work, and the next task. ## Naming Policy Use model family names in recommendations unless the user explicitly requests version pinning. ## 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. Planning Phase Before any coding: 1. Read AGENTS.md to understand the 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 an authentication provider (Supabase/Firebase) > 2. Create login/signup components > 3. Add a protected route wrapper > 4. Test the login flow > > Should I proceed? ### 2. Execution Phase After approval: 1. Implement ONE feature at a time 2. Follow the patterns in agent_docs/code_patterns.md 3. Use the tech stack from agent_docs/tech_stack.md 4. Keep changes focused and minimal 5. Commit after each working feature ### 3. Verification Phase After each feature: 1. Run tests: npm test (or equivalent) 2. Run linter: npm run lint 3. Perform a manual smoke test if needed 4. Fix any issues before moving on 5. Update AGENTS.md to reflect the 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 the project with the chosen stack 2. Set up the development environment 3. Configure the database connection 4. Set up authentication 5. Create the basic project structure ### Phase 2: Core Features Build each feature from the PRD: 1. Identify the simplest implementation 2. Create a database schema if needed 3. Build the "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 the launch checklist 4. Run a dedicated security check (authentication, 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 passed. Ready for the next feature? Avoid: > I’ve finished implementing the login form component that handles user authentication via email and password... ## Progress Updates After completing each feature, update AGENTS.md: ``markdown ## 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: `markdown ### 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 a backup plan - Do NOT add features outside the current phase - Do NOT skip verification steps - Do NOT use deprecated patterns - Do NOT over-engineer simple f