Skip to content

CLAUDE.md

Latest commit

 

History

History
68 lines (55 loc) · 2.69 KB

CLAUDE.md

File metadata and controls

68 lines (55 loc) · 2.69 KB

CLAUDE.md — F3Go30

Tier: Standard Standards: /docs/framework/doc-standard.md (read-only — do not edit)

Reading Order

  1. Current state — bd prime (auto-loaded when bd in use)
  2. docs/CONTEXT.md — purpose, capabilities, use cases
  3. docs/DESIGN.md — architecture, modules
  4. docs/OPERATIONS.md — how to run it
  5. /adr/ — why key decisions were made
  6. /docs/references/ — external document summaries

Document Map

Content Location
Purpose, capabilities, use cases, glossary docs/CONTEXT.md
Architecture, modules, data model, runtime risks docs/DESIGN.md
Deployment, configuration, failure modes docs/OPERATIONS.md
Current state bd ready
Identified work bd issues
Technical decisions /adr/
Strategic themes docs/VISION.md (when created)
Roadmap, funnel docs/ROADMAP.md
Go30 Q tutorial narration script /docs/references/go30-q-tutorial-script.md

Placement Rules

  • New capabilities → docs/CONTEXT.md §Capabilities + use case if actor-driven
  • Architecture changes → docs/DESIGN.md + affected diagrams
  • Operational changes → docs/OPERATIONS.md
  • Resolved decisions → /adr/
  • New terms → docs/CONTEXT.md §Glossary
  • New risk identified → bd remember
  • New initiative → docs/ROADMAP.md §Funnel

Maintenance Protocol

Claude does not monitor documents between sessions, detect drift, or update documents without explicit instruction.

  • At session start or phase transition: run /session-start-check
  • After any code or architecture change: run /doc-trigger-check
  • To trigger a state review: "review project state before we start"

Memory System

System Scope Use for
bd remember / bd memories Project-scoped Project rationale, design decisions, process insights — travels with the repo
MEMORY.md (auto-memory) User-scoped User preferences, cross-project style conventions

Do not use MEMORY.md for project rationale. Do not use bd remember for user preferences.

Working

bd ready              # available work (unblocked, prioritized)
bd list               # all open issues
bd show <id>          # full issue detail with deps
bd update <id> --claim  # claim and start work (atomic: sets assignee + in_progress)
bd close <id>         # mark complete
/bd-report            # generate bdreport.md (snapshot with graph + narrative)

Reference Summaries

File Source Document Covers
/docs/references/go30-q-tutorial-script.md Script.md (original) Go30 Q onboarding narration — steps to create a new monthly tracker