Freelance developer, writing software with passion since 1983, Undolog
Treating CLAUDE.md like a budget: what worked for me
hi all 👋 Giovambattista from Rome, writing software since 1983 and these days mostly with Claude Code and Codex side by side
one thing that actually worked for me: every session pays for the instruction files before the first prompt (CLAUDE.md, AGENTS.md, rules, the memory index, a line for each skill), so I started treating them as a budget
- my global CLAUDE.md is a map, not a manual: a short table of where things live
- only what must hold in every session becomes a rule, a few lines each. right now that's 18 rules, 233 lines in total
- the why and the long recipes live in plain reference files the agent opens only for that task
- the memory index is one line per memory, the details sit in their own files
- Codex reads AGENTS.md, not CLAUDE.md, so it gets a condensed copy of the same rules
all in, my main workspace loads about 20k characters on every start across 20 files, and I measure it with a small script instead of guessing
curious how you handle it... one big file per repo, nested files, skills, or something else?






Comments
0 comments