Conventions worth writing down
My own house rules, written down so Claude Code applies them without being asked: how I format, test, gate permissions, handle secrets and ship my Django projects, and what should never reach a commit in any of them. Have a look around, take whatever works for you, and adjust the rest to suit how you like to work.
Two skills, and counting
More will follow as I keep building with agents. Each is a principle plus a pointer to where a project keeps its own values, so none of them describes a single codebase.
django
Formatters, imports, docstrings, coverage as a merge gate, permission gating, secrets at rest, email as one Markdown template, and a portable boot contract.
gitignore
What never belongs in version control, what people wrongly ignore, and why a committed secret gets rotated rather than merely deleted.
Derived, not duplicated
Every page here is generated from the same Markdown Claude loads, so there is no second copy to drift out of date.
Written for an agent, readable by a person
If something is written for an agent, or works because an agent reads it, a person has to be able to read the same thing and do it themselves. So every rule here is prose with its reasons attached rather than machine instructions, and this site publishes the exact files Claude loads. No agent-only version, no human-only version, and nothing that only makes sense once someone explains it to you.