Project-Level Context
This is a member-only chapter. Log in with your Signal Over Noise membership email to continue.
Log in to readModule 3 · Section 4 of 5
Project-Level Context
Reference files work at the project level too. A .claude/CLAUDE.md file in a specific repo can give Claude context about that codebase without touching your global config:
## This Project
- Astro static site deployed to VPS via rsync
- CSS uses custom properties defined in global.css
- No TypeScript — plain JS only
- Deploy with: ./deploy.sh
- Assets served from CDN, not local public/ folderThis is where you put the things that only apply here: the tech stack, the deployment process, the gotchas, the conventions. Project-level context is what stops Claude from suggesting TypeScript types in a JS-only codebase, or running a deploy process that doesn’t exist.
Start here: Create at least one reference file. ~/.claude/TOOLS.md is the easiest starting point — list the tools you use daily, then point to it from your CLAUDE.md.