A single activation file —Documentation Index
Fetch the complete documentation index at: https://mintlify.com/davidbuenov/dbv-specs-ops/llms.txt
Use this file to discover all available pages before exploring further.
GEMINI.md — serves both Gemini CLI and Antigravity (VS Code · Google DeepMind). Both tools read GEMINI.md automatically from the workspace root at the start of every session, giving them the full Spec-Driven Development context before any code or plan is proposed. Antigravity extends this base with three native features: Planning Mode with versioned artifacts, Knowledge Items for context recovery, and Context Snapshots for cross-session persistence.
How GEMINI.md Is Auto-Loaded
Both Gemini CLI (gemini terminal command) and Antigravity detect GEMINI.md at the project root and read it as part of their session initialization. No manual pasting is required on either platform. The file is a strong pointer: rather than duplicating workflow logic, it directs the AI to docs/MASTER_PROMPT.md as the single authoritative source for the full SDD lifecycle.
The
ANTIGRAVITY.md file documents the Antigravity-specific extended features. It is read as reference documentation — GEMINI.md remains the primary auto-loaded activation file for both platforms.Files Read at Session Start
GEMINI.md instructs the AI to read these seven files before proposing any code or plan:
| File | Purpose |
|---|---|
project.config.md | Project identity: name, author, license and file header template |
docs/MASTER_PROMPT.md | Mandatory workflow, rules and boundaries |
docs/SPECIFICATIONS.md | Current project requirements |
docs/ARCHITECTURE.md | Stack and technical decisions |
docs/DESIGN.md | Visual design system: color tokens, typography, components and philosophy (if it exists) |
memory.md | Context and Decisions: Qualitative knowledge (ADRs, lessons learned, active context) |
task.md | Current state + Context Snapshot |
Core Rules
The core directive inGEMINI.md is identical to the one in CLAUDE.md, ensuring consistent behavior across platforms:
Read docs/MASTER_PROMPT.md and follow its workflow strictly. If you detect contradictions between the prompt and project specs, halt and report before proceeding.
All initialization (Bootstrap), state checking (Specs Check), lifecycle (Workflow) and coding standards are defined centrally in MASTER_PROMPT.md to avoid cognitive redundancy.
Platform-Specific Behaviors
- Gemini CLI
- Antigravity
Gemini CLI reads
GEMINI.md automatically when you run the gemini command inside a project directory that contains the file. The base SDD workflow defined in docs/MASTER_PROMPT.md applies in full. No additional configuration is needed.Setup steps:Place GEMINI.md at the project root
Copy
GEMINI.md from the dbv-specs-ops template to the root of your project. Gemini CLI will find it automatically on the next session start.Fill in project.config.md
Complete the project identity fields. If left with placeholders, Gemini will run the Bootstrap interview on first session start.
Start a Gemini CLI session
Run
gemini in your terminal from the project root. The full SDD context is loaded automatically.