by ciembor
AGENTS.md rules / skills for AI coding agents: Codex, Cursor & Claude Code. Inspired by Clean Code, Refactoring, DDD, Clean Architecture and DDIA programming books.
# Add to your Claude Code skills
git clone https://github.com/ciembor/agent-rules-booksGuides for using ai agents skills like agent-rules-books.
Last scanned: 5/6/2026
{
"issues": [],
"status": "PASSED",
"scannedAt": "2026-05-06T06:29:37.441Z",
"semgrepRan": false,
"npmAuditRan": true,
"pipAuditRan": true
}agent-rules-books is an open-source ai agents skill for AI coding assistants such as Claude Code, Codex CLI, and ChatGPT, built by ciembor. AGENTS.md rules / skills for AI coding agents: Codex, Cursor & Claude Code. Inspired by Clean Code, Refactoring, DDD, Clean Architecture and DDIA programming books. It has 1,906 GitHub stars.
Yes. agent-rules-books passed SkillsLLM's automated security scan — a dependency vulnerability audit plus prompt-injection heuristics — with no high-severity issues. You can read the full report in the Security Report section on this page.
Clone the repository with "git clone https://github.com/ciembor/agent-rules-books" and add it to your Claude Code skills directory (see the Installation section above).
Yes. SkillsLLM lists many other AI Agents skills you can browse and compare side by side. Open the AI Agents category from the badge at the top of this page, or use the Related Skills and comparison links further down to weigh agent-rules-books against similar tools.
No comments yet. Be the first to share your thoughts!
MIT licensed universal project rules for coding agents.
This repository contains ready-to-use rule sets inspired by well-known books on software design, architecture, refactoring, legacy code, reliability, and data-intensive systems.
For editor-specific setup in Codex, Claude Code, and Cursor, see USAGE.md. It covers always-on vs on-demand usage, skills, scoped rules, MCP or RAG patterns, and the preferred setup for each editor.
Each rule set is released in three tool-agnostic Markdown versions:
mini: the recommended version for most real task usenano: the compact fallback for very tight context budgetsfull: the canonical complete source and reference versionFor constructive criticism from Reddit, see CRITICISM.md.
For release history, see CHANGELOG.md.
Metrics:
lines: physical line count from wc -lrules: Markdown list items counted with the deterministic release conventionsize: raw bytes from wc -c| Rule Set | Full file | Full lines | Full rules | Full size | Mini file | Mini lines | Mini rules | Mini size | Nano file | Nano lines | Nano rules | Nano size |
|---|---|---|---|---|---|---|---|---|---|---|---|---|
| A Philosophy of Software Design | full | 370 | 177 | 13561 B | mini | 46 | 28 | 5774 B | nano | 35 | 17 | 2258 B |
| Clean Architecture | full | 515 | 289 | 17782 B | mini | 49 | 31 | 5486 B | nano | 36 | 18 | 2254 B |
| Clean Code | full | 297 | 220 | 13851 B | mini | 47 | 29 | 3804 B | nano | 32 | 14 | 1235 B |
| Code Complete | full | 354 | 180 | 12407 B | mini | 56 | 38 | 6717 B | nano | 41 | 23 | 2544 B |
| Designing Data-Intensive Applications | full | 393 | 205 | 16084 B | mini | 55 | 37 | 6949 B | nano | 34 | 16 | 2575 B |
| Domain-Driven Design | full | 979 | 523 | 42424 B | mini | 48 | 30 | 5683 B | nano | 39 | 21 | 2266 B |
| Domain-Driven Design Distilled | full | 317 | 158 | 11351 B | mini | 56 | 38 | 6438 B | nano | 41 | 23 | 2535 B |
| Implementing Domain-Driven Design | full | 337 | 177 | 12848 B | mini | 57 | 39 | 7333 B | nano | 37 | 19 | 2723 B |
| Patterns of Enterprise Application Architecture | full | 404 | 196 | 15501 B | mini | 54 | 36 | 8099 B | nano | 35 | 17 | 2823 B |
| Refactoring | full | 433 | 242 | 17866 B | mini | 49 | 31 | 5167 B | nano | 37 | 19 | 1986 B |
| Release It! | full | 382 | 204 | 13542 B | mini | 48 | 30 | 6372 B | nano | 38 | 20 | 2205 B |
| The Pragmatic Programmer | full | 359 | 179 | 13398 B | mini | 65 | 47 | 7165 B | nano | 44 | 26 | 2263 B |
| Working Effectively with Legacy Code | full | 371 | 193 | 13817 B | mini | 50 | 32 | 5707 B | nano | 35 | 17 | 1792 B |
| Refactoring.Guru | full | 765 | 478 | 62561 B | mini | 64 | 46 | 6287 B | nano | 41 | 23 | 2593 B |
Author: John Ousterhout
The book focuses on fighting complexity through deep modules, simple interfaces, information hiding, and design choices that reduce cognitive load. This rule set is especially useful for API design, module design, and refactoring shallow abstractions.
Author: Robert C. Martin
The book describes designing systems around stable boundaries, the dependency rule, and the separation of business policies from details such as frameworks, databases, and UI. This rule set helps keep code resistant to technology churn.
Author: Robert C. Martin
The book focuses on readability, naming, small functions, responsibilities, tests, and simplicity. This rule set is a strong default for everyday coding and code review.
Author: Steve McConnell
The book covers a broad range of software construction practices: routine design, variables, classes, control flow, defensive programming, coding standards, and testing. This rule set helps agents make disciplined implementation decisions.
Author: Martin Kleppmann
The book covers reliability, scalability, consistency, replication, partitioning, transactions, data streams, and schema evolution. This rule set is intended for systems where data ownership, event flows, and consistency semantics matter.
Author: Eric Evans
The book introduces domain modeling, ubiquitous language, bounded contexts, tactical patterns, and strategic design. This rule set helps agents think in terms of the business model rather than tables, controllers, or DTOs.
Author: Vaughn Vernon
The book is a short, practical introduction to DDD. It focuses on subdomains, bounded contexts, context mapping, and basic tactical patterns. This rule set is a good fit when you want the benefits of DDD without excessive ceremony.
Author: Vaughn Vernon
The book shows how to apply DDD in real systems: aggregates, domain events, contexts, integrations, and application architecture. This rule set is more implementation-focused than domain-driven-design-distilled.
Author: Martin Fowler
The book catalogues enterprise appl