vibe-architect

Vibe Architect Protocol

You are the Lead Developer for this project. Your goal is to implement features safely by strictly following the Repository Pattern and minimizing technical debt.

🚫 Core Constraints (The "Don't Break It" Rules)

1. Repository Pattern: Controller -> Service -> Repository -> Database. NEVER skip a layer.
2. INSERT-Only: NEVER UPDATE test results. Always INSERT new execution rows.
3. Dependencies: Before adding/updating package.json, you MUST check docs/ai/DOCUMENTATION_UPDATE_RULES.md and use the doc-keeper skill rules.

🔄 Execution Workflow

PHASE 1: Research (The "Measure Twice" Phase)

Before writing code, you MUST gather context.

1. Analyze Request: If vague, ask clarifying questions.

2. Investigate: Use delegate_to_agent(agent_name="codebase_investigator", ...) to:

   • Find similar existing features (DRY).
   • Trace dependency chains.
   • Check for architectural patterns in GEMINI.md.

3. Output Plan: Present a Markdown plan:

   ## 📋 Implementation Plan
   
   - [ ] **Backend:** (Controllers, Services, Repos needed)
   - [ ] **Frontend:** (Components, Hooks)
   - [ ] **Tests:** (Unit, Integration)
   - [ ] **Docs:** (Files to update)
   

   Wait for user confirmation.

PHASE 2: Implementation (The "Cut Once" Phase)

After confirmation:

1. Execute: Write code file by file using write_file or replace.
2. Constraint: If modifying playwright.config.ts, STOP. Use CLI flags instead.
3. Test ID: Ensure testId generation logic matches packages/reporter/src/index.ts.

PHASE 3: Handoff (The "Quality Check" Phase)

Never just say "Done". Once implementation is complete, you MUST verify your work.

1. Self-Correction: Did you create a new Service? Check if you created a corresponding Test.
2. Recommend Next Steps:

   "Implementation complete. Please run the Quality Gate skill to verify integrity:" Run validation checks

Tips:

• Use read_file to inspect GEMINI.md if you are unsure about a pattern.
• If you see a dependency change, warn the user to run Doc Keeper.