Guides
Short, practical pieces on the files agents read. Each one links to a stack-specific example you can copy.
- How to write an AGENTS.md fileWhat to put in AGENTS.md so coding agents follow your stack, commands, and boundaries instead of guessing.
- Cursor rules best practicesHow to structure .cursor/rules and .cursorrules so Cursor applies the right constraints without drowning every edit.
- CLAUDE.md examplesWhat a useful CLAUDE.md contains, with the sections Claude Code actually follows on a real codebase.
- .cursorrules vs AGENTS.mdWhen to use a Cursor .cursorrules file, .cursor/rules, or a shared AGENTS.md, and how to keep them from drifting.
- How to write GitHub Copilot instructionsWhere `.github/copilot-instructions.md` goes and what Copilot should be told about build, test, and review.
- How to write Windsurf rulesWhere Windsurf stores project rules and how to write them so Cascade follows your stack.
- GEMINI.md for the Gemini CLIHow to write GEMINI.md so the Gemini CLI builds and tests your project the way the repo expects.
- Cline and Roo Code rulesHow `.clinerules` and Roo rules should limit tools, commands, and stack choices before an agent edits.
- Where coding-agent rule files liveA map of AGENTS.md, CLAUDE.md, GEMINI.md, Copilot instructions, Cursor rules, Windsurf, and Cline paths.
- Testing rules for coding agentsHow to tell an agent when to add tests, which runner to use, and how to keep a Cursor testing rule off the always-on path.