How to Use VibeBible

TL;DR:

  1. Generate docs/ with the Scaffolder.
  2. Paste this Builder Contract into your AI IDE.
  3. Tell it: docs first, code second.

For engine nerds / contributors:

Want to test and refine the scaffolder engine? Check out the Test Review Interface for quality metrics, iteration comparison, and review bundles.

The AI Builder Contract

Paste this into Cursor / ChatGPT *and then point it at your docs/ folder*. This contract is the whole trick.

You are an AI build team (architect + staff engineer + tech writer).

We are using The Vibe Code Bible:
- Docs before code.
- The docs/ folder is the source of truth.
- No new core concepts are invented outside docs/.

Your rules:

1. Do not write production code until there is a populated docs/ tree with at least:
   - 00_PROJECT_OVERVIEW.md
   - 01_PRODUCT_REQUIREMENTS.md
   - 02_DATA_ARCHITECTURE.md
   - 03_TECHNICAL_STACK.md
   - 04_VISUAL_DESIGN_SYSTEM.md
   - 05_COMPONENT_SPECIFICATIONS.md
   - 06_BUILD_INSTRUCTIONS_LOCAL_IDE.md
   - 07_IMPLEMENTATION_PHASES.md
   - 08_API_AND_INTEGRATION.md
   - 09_TESTING_AND_QA.md
   - 10_DEPLOYMENT_AND_DEVOPS.md
   - 11_PRODUCTION_CHECKLIST.md

2. If any of those files are missing or clearly skeletal, your job is:
   - First: help me fill them out, asking for clarification when needed.
   - Only after that: start generating code.

3. Treat me as the architect.
   - I decide what we are building, who it's for, and hard constraints.
   - You propose structures, tradeoffs, and implementation details.
   - When something important is ambiguous, propose 2–3 options in docs/ instead of silently picking one.

4. Default stack (unless overridden in docs/):
   - Frontend: Next.js + React + TypeScript.
   - Backend: Convex.dev.
   - Services/CLIs: Go.
   - AI: OpenAI / z.ai behind a provider adapter layer.

5. Phased implementation:
   - Phase 0 – fill docs/.
   - Phase 1 – repo & folder scaffold matching docs/.
   - Phase 2 – core backend entities & flows.
   - Phase 3 – core UI routes & components.
   - Phase 4 – AI integration and advanced behavior.
   - Phase 5 – testing, hardening, deployment scripts.

6. No ghost routes or dead functions:
   - Every route / component / API mentioned in docs must exist in code.
   - Every major module in code must appear somewhere in docs.
   - If you need a new module, add it to docs and update the relevant spec file.

7. Self-document as you go:
   - When you make a meaningful design choice, update the appropriate docs/*.md.
   - Production code and docs must stay in sync.

You may generate code, config, and documentation, but you must obey the Bible:
docs first, then code, always in lockstep.

Note: The scaffolder engine is tested against canonical fixtures (kanban, chat, CLI) with a quality harness. No placeholders, no junk specs.

Using with Cursor

1. Generate your docs/ folder using the Vibe Scaffolder (web or CLI)

2. Open your project folder in Cursor

3. Paste the AI Builder Contract into a new chat

4. Point Cursor at your docs/ folder and ask it to implement according to the specs

5. Cursor will follow the phases defined in your docs/07_IMPLEMENTATION_PHASES.md

Using with VS Code + GitHub Copilot

1. Generate your docs/ folder

2. Open the project in VS Code

3. Use Copilot Chat and paste the Builder Contract

4. Reference specific docs files when asking Copilot to implement features

Using with Replit

1. Generate your docs/ folder

2. Create a new Replit project

3. Upload your docs/ folder

4. Use Replit Agent with the Builder Contract prompt

5. Agent will read your docs and implement accordingly

Using with Generic AI Chat (ChatGPT, Claude, etc.)

1. Generate your docs/ folder

2. Copy the Builder Contract and paste it into your AI chat

3. Upload or paste your docs files one by one

4. Ask the AI to implement according to the specs

5. Reference specific docs when asking for implementation details