init2listed

Generate a world-class project-specific CLAUDE.md by deeply analyzing this repository. The goal is to capture derived knowledge that saves Claude from re-reading the entire project at the start of every session. ## Reading Order (highest signal first) Work through these in order, reading the most information-dense sources first: 1. **README.md, CONTRIBUTING.md** — intent, setup instructions, conventions 2. **docs/adrs/, docs/decisions/** — architectural decisions and their context 3. **docs/\*** — domain knowledge, architecture guides, API docs 4. **Package files** (package.json, Cargo.toml, go.mod, requirements.txt, etc.) — stack, scripts, dependencies 5. **Config files** (tsconfig, eslint/biome, prettier, terraform, docker, etc.) — coding standards already enforced by tooling 6. **CI/CD config** (.github/workflows/, Jenkinsfile, etc.) — what's tested, how it deploys 7. **Directory structure** (tree, 2 levels deep) — module layout, naming 8. **Key entrypoints** (main/index files, route definitions, handler files) — architecture in practice 9. **Test setup** (test config, a few example test files) — testing patterns, framework, structure, conventions ## Output Create a CLAUDE.md at the project root with this structure: ```md # Project: <n> ## Overview <What this project does, its purpose, key domain concepts. 2-3 sentences.> ## Stack <Detected tech stack with versions where relevant. Be specific.> ## Key Commands - **Install:** `<command>` - **Build:** `<comman