# CLAUDE.md
This file provides guidance to Claude Code when working with this codebase.
Generated by [sourcebook](https://github.com/maroondlabs/sourcebook). Review and edit — the best context comes from human + machine together.
## Quick Reference
- **validation:** Use Pydantic BaseModel for data classes
- **testing:** Tests use pytest.
## Commands
- **Build:** `make`
## Critical Constraints
## Stack
Python
## Project Structure
- `tests/` — Tests
- `docs/` — Documentation
## Conventions & Patterns
- **Testing:** Tests live in a separate test/ directory, mirroring src/ structure. New tests go there, not next to source files.
- **Dominant patterns:**
- Use Pydantic BaseModel for data classes. This is the project's standard validation approach.
- Tests use pytest.
## Before Making Changes
- **Follow existing patterns.** This project has established conventions (listed above). Match them instead of introducing new approaches.
- **Respect constraints.** Review the Critical Constraints section before making structural changes.
If the sourcebook MCP server is available (`sourcebook serve`), verify before acting:
- `get_blast_radius` — check what breaks if you edit a hub file
- `query_conventions` — confirm the right pattern before adding new code
- `get_pressing_questions` — get a briefing before editing an unfamiliar file
## What to Add Manually
The most valuable context is what only you know. Add:
- Architectural decisions and why they were made
- Past incidents that shaped current conventions
- Deprecated patterns to avoid in new code
- Domain-specific rules or terminology
- Environment setup beyond what .env.example shows