agent-rules-books

Start with the "mini" version of the rule set that best matches your domain—e.g., "Clean Code" for everyday coding, "Domain-Driven Design" for business‑centric modeling, or "Designing Data‑Intensive Applications" for data‑heavy systems. If you need a more exhaustive reference, use the "full" file; if you have tight context limits, use the "nano" file. The README’s Release Matrix shows line counts and rule counts to help you gauge the size.

Each book’s rules are shipped in three Markdown variants: - **full** – the complete, canonical source with all rules. - **mini** – a trimmed, recommended subset that covers the core principles while keeping context size reasonable. - **nano** – a very compact fallback for environments with strict token budgets. The Release Matrix lists the size and rule count for each variant.

Follow the instructions in `docs/USAGE.md`. For Codex, add the chosen rule file to your project’s `AGENTS.md`. For Claude Code, copy the rules into `CLAUDE.md` or create a skill. For Cursor, adapt the rules into project rules or keep them as AGENTS.md‑style instructions. The README’s "About" section explains the editor‑specific setup.

Yes—combine rule sets that target different concerns (e.g., "Clean Architecture" + "Domain-Driven Design"). Use the compatibility guide in `docs/COMPATIBILITY.md` to ensure the chosen sets don’t overlap or contradict. The README notes that combining multiple books is supported and provides guidance on managing potential conflicts.

Create a new folder named after the book, add the three rule files (full, mini, nano) following the deterministic release convention, and update the Release Matrix. Then document the book in the Books List section and reference the new rules in `USAGE.md`. The README’s "Adding the Book" section outlines the exact steps and file structure.