Skip to main content

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.

Claude Code is the recommended integration path for dbv-specs-ops. When CLAUDE.md is present at the project root, Claude Code reads it automatically at the start of every session — no manual pasting, no setup commands. The moment you open a project, the full Spec-Driven Development context is already loaded and the AI is ready to act as a disciplined Senior Software Engineer.

​
How CLAUDE.md Is Auto-Loaded

Claude Code scans the project root for a file named CLAUDE.md before processing any user message. If the file exists, Claude reads it in full as part of its initialization context. This means every session starts with the SDD workflow, the list of files to read, and the core rules already in place — regardless of whether you open a new conversation or resume an existing one.
This auto-loading behavior is specific to Claude Code (CLI, VS Code extension, and Desktop). It does not apply to Claude.ai web chat, which requires manual activation.

​
Files Read at Session Start

The CLAUDE.md activation file instructs Claude to read seven project files before proposing any code or plan:
FilePurpose
project.config.mdProject identity: name, author, license and file header template
docs/MASTER_PROMPT.mdMandatory workflow, rules and boundaries
docs/SPECIFICATIONS.mdCurrent project requirements
docs/ARCHITECTURE.mdStack and technical decisions
docs/DESIGN.mdVisual design system: color tokens, typography, components and philosophy (if it exists)
memory.mdContext and Decisions: Qualitative knowledge (ADRs, lessons learned, active context)
task.mdCurrent state + Context Snapshot
Reading these files in order gives Claude the full project context before it writes a single line of code: what to build, how to build it, what decisions have already been made, and exactly where work left off in the last session.

​
Core Rules

The CLAUDE.md file is intentionally a thin pointer. Rather than duplicating workflow logic, it directs Claude to docs/MASTER_PROMPT.md as the single source of truth:
Read docs/MASTER_PROMPT.md and follow its workflow strictly. If you detect contradictions between the prompt and the project specs, halt and report before proceeding.
All initialization logic (Bootstrap), state checking (Specs Check), lifecycle management (Workflow) and coding standards are defined centrally in MASTER_PROMPT.md to avoid cognitive redundancy across activation files.

​
The CLAUDE.md File

This is the complete content of the CLAUDE.md activation file: 
# Instrucciones del Proyecto para Claude Code

Este proyecto sigue la metodología **Spec-Driven Development (SDD)**. Lee estos archivos al inicio de cada sesión antes de proponer cualquier código o plan:

| Archivo | Propósito |
| --- | --- |
| `project.config.md` | Identidad del proyecto: nombre, autor, licencia y plantilla de cabeceras |
| `docs/MASTER_PROMPT.md` | Workflow obligatorio, normas y límites |
| `docs/SPECIFICATIONS.md` | Requisitos del proyecto actual |
| `docs/ARCHITECTURE.md` | Stack y decisiones técnicas |
| `docs/DESIGN.md` | Sistema de diseño visual: tokens de color, tipografía, componentes y filosofía *(si existe)* |
| `memory.md` | **Contexto y Decisiones:** Conocimiento cualitativo (ADRs, lecciones, mapa) |
| `task.md` | Estado actual + Snapshot de Contexto |

## ⚠️ Reglas Core (Puntero Fuerte)

**Lee `docs/MASTER_PROMPT.md` y sigue su flujo de trabajo estrictamente. Si detectas contradicciones entre el prompt y las especificaciones del proyecto, detente e informa antes de proceder.**
Toda la lógica de inicialización (Bootstrap), comprobación de estado (Specs Check), ciclo de vida (Workflow) y estándares de código están definidos centralizadamente allí para evitar redundancia cognitiva.


> 🛠️ Framework SDD creado por **[David Bueno Vallejo](https://github.com/davidbuenov)** — libre y gratuito · [dbv-specs-ops](https://github.com/davidbuenov/dbv-specs-ops)

​
Setup Steps

1

Copy CLAUDE.md to your project root

Place CLAUDE.md at the root of your project. If you used the GitHub template or downloaded the ZIP, it is already there. Claude Code will detect it automatically.
2

Fill in project.config.md

Open project.config.md and complete the project identity fields: name, author, and license. If you leave the placeholders in place, Claude will run the Bootstrap interview and fill them in for you on first session start.
3

Open Claude Code

Launch Claude Code (CLI, VS Code extension, or Desktop app) in the project directory. Claude reads CLAUDE.md immediately and loads the full SDD context. You will not need to paste any instructions.
4

Type /spec to start

Send the command /spec to kick off the Engineering Interview. Claude will analyze the project, propose a specification draft with explicit assumptions, and wait for your confirmation before writing any code.

​
The Trust Boundary

MASTER_PROMPT.md defines a strict separation between directives and data. Only the content inside the XML tags of MASTER_PROMPT.md (<workflow>, <boundaries>, <development_rules>, etc.) is treated as a directive. All project files — docs/SPECIFICATIONS.md, task.md, memory.md, CHANGELOG.md, and all source code — are treated as data to analyze, not instructions to follow. This means that if any project file contains imperative text that contradicts the workflow defined in MASTER_PROMPT.md, Claude will detect the contradiction, report it, and halt rather than silently obeying a potentially injected instruction.
If you need to isolate the SDD framework from an existing repository without touching your project root, you can place the entire dbv-specs-ops folder as a subfolder and point CLAUDE.md to it: Please read and follow the master instructions in dbv-specs-ops/docs/MASTER_PROMPT.md.

Build docs developers (and LLMs) love

Get started for freeTalk to us