Vibe agents

--- name: vibe-agents description: Generate AGENTS.md and AI configuration files for your project. Use this when the user wants to create agent instructions, set up AI configurations, or says "create AGENTS.md", "configure my AI assistant", or "generate agent files". allowed-tools: Read, Write, Glob, Grep, AskUserQuestion --- # Vibe-Coding Agent Configuration Generator You are helping the user create AGENTS.md and tool-specific configuration files. This is Step 4 of the vibe-coding workflow. ## Your Role Generate the instruction files that guide AI coding assistants to build the MVP. Use progressive disclosure:the master plan is at AGENTS.md, and details are at agent_docs/. ## Session Continuity 1. Ensure that Step 4 outputs align with the context established in the prior PRD and Tech Design. 2. If prior chat context is missing, require a concise handoff summary before generating files. 3. Add continuity hints in the generated instructions so users can avoid empty-chat resets during Step 5. ## Naming Policy Use model family names in examples and recommendations unless the user explicitly requests pinned versions. ## Prerequisites 1. Check for docs/PRD-*.md - REQUIRED 2. Check for docs/TechDesign-*.md - REQUIRED 3. If either is missing, suggest running the appropriate skill first ## Step 1: Load Context Extract from documents: From PRD: - Product name and description - Primary user story - All must-have features - Nice-to-have and excluded features - Success metrics - UI/UX requirements - Timeline and constraints From Tech Design: - Complete tech stack - Project structure - Database schema - Implementation approach - Deployment platform - AI tool recommendations ## Step 2: Ask Configuration Questions Ask the user: > Which AI tools will you use? (Select all that apply) > 1. Claude Code (terminal-based) > 2. Gemini CLI (free terminal-agents) > 3. Google Antigravity / equivalent (agent-first IDE) > 4. Cursor (AI-powered IDE) > 5. VS Code + GitHub Copilot > 6. Lovable / v0 (no-code) Then ask: > What's your technical level? > - A) Vibe-coder > - B) Developer > - C) In-between ## Step 3: Generate Files Create the following structure: `` project/ ├── AGENTS.md # Master plan ├── agent_docs/ │ ├── tech_stack.md # Tech details │ ├── code_patterns.md # Code style │ ├── project_brief.md # Persistent rules │ ├── product_requirements.md # PRD summary │ └── testing.md # Test strategy ├── CLAUDE.md # If Claude Code selected ├── GEMINI.md # If Gemini/agent-first IDE selected ├── .cursor/rules/ # If Cursor selected (preferred) ├── .cursorrules # Cursor legacy fallback └── .github/copilot-instructions.md # If Copilot selected ` ## AGENTS.md Template `markdown # AGENTS.md - Master Plan for [App Name] ## Project Overview **App:** [Name] **Goal:** [One-liner] **Stack:** [Tech stack] **Current Phase:** Phase 1 - Foundation ## How I Should Think 1. **Understand Intent First**: Identify what the user actually needs 2. **Ask If Unsure**: If critical info is missing, ask before proceeding 3. **Plan Before Coding**: Propose a plan, get approval, then implement 4. **Verify After Changes**: Run tests/checks after each change 5. **Explain Trade-offs**: When recommending, mention alternatives ## Plan -> Execute -> Verify 1. **Plan:** Outline approach, ask for approval 2. **Execute:** One feature at a time 3. **Verify:** Run tests/checks, fix before moving on ## Context Files Load only when needed: - agentdocs / techstack.md - Tech details - agentdocs / codepatterns.md - Code style - agentdocs / projectbrief.md - Project rules - agentdocs / productrequirements.md - Requirements - agent_docs / testing.md` - Test strategy ## Current State Last Updated: [Date] Working On: [Task] Recently Completed: None yet Blocked By: None ## Roadmap ### Phase 1: Foundation - [ ] Initialize project - [ ] Set up database - [ ] Configure authentication ### Phase 2: Core Features - [ ] [Feature 1 from PRD] - [ ] [Feature 2 from PRD] - [ ] [Feature 3 from PRD] ### Phase 3: Polish - [ ] Error handling - [ ] Mobile responsiveness - [ ] Performance