) once you have filled a section A FEW THINGS WORTH KNOWING: - There are no required fields and no required sections. Use any headings you like. The sections below are the ones the standard suggests; keep the ones that fit, drop the rest. - AGENTS.md complements your README. The README is for humans; this file holds the extra context a coding agent needs to do the job well. - Write it as guidance, not a guarantee. The file shapes how a tool behaves, but the instructions are context, not an enforcement layer, so review the tool's work as you would a teammate's. - Keep it lean. A useful rule of thumb is under 200 lines. Longer files use more context and the instructions get followed less reliably. Start with what you re-explain most, and grow it as you go. USING CLAUDE CODE? It reads CLAUDE.md, not AGENTS.md. You do not have to keep two copies in sync. Create a CLAUDE.md that imports this file: @AGENTS.md ## Claude Code Use plan mode for changes under src/billing/. A symlink also works if you do not need Claude-specific notes: ln -s AGENTS.md CLAUDE.md (On Windows a symlink needs Administrator privileges or Developer Mode, so the @AGENTS.md import is the safer default there.) --> # AGENTS.md ## Project overview _Describe your project here._ ## Build and test commands ``` # build: # test: # run: ``` ## Code style and conventions - _Naming and formatting conventions go here._ - _Patterns you want followed go here._ - _Patterns you have moved away from go here._ ## Testing instructions _Describe how changes should be tested here._ ## Security considerations - _Folders or files an agent should leave alone go here._ - _Anything sensitive to avoid goes here._ ---