Skip to content
SkillModel-led90 tokens in use

Clean Architecture

Robert C. Martin-inspired rules that keep business policy independent of frameworks, databases and delivery details.

3,324 stars on the repository MIT Licenseciembor/agent-rules-books · clean-architecture
npx skills add ciembor/agent-rules-books --skill clean-architecture
View source

Install command as written in the repository's README

Skill label

measured from its files

What installing Clean Architecture costs

27tokens idle
90tokens in use
4,577tokens, up to

Idle is what sits in context while the skill is installed. In use is its instructions, loaded when it runs. Up to adds the files its instructions link. Counts are approximate, made offline with cl100k_base.

Model dependence Model-led

Script-ledMixedModel-led

Mostly instructions, so how well it works depends on the model that follows them.

This describes the skill's structure, how much of it is scripts. It does not say how well it works.

Touches

Nothing detected: no shell, network, file writes, git or credentials in its files.

Declared tags come from the skill's frontmatter; detected ones from its scripts, its code blocks and the commands it names in inline code. This is detected, not audited.

How it scores

Quality

How well the skill is written, counted from its own files: its frontmatter, its steps, examples, stated output and constraints, its size and whether every file it ships is one it names.How we score it →
Needs attention
  • Frontmatter11/15
  • Structure0/25
  • Examples0/15
  • Output2/15
  • Size13/15
  • Resources10/15

Security

Starts at 100 and loses points for each thing in the skill's files that a reader should look at first.How we score it →
Excellent

No findings.

Repository health

Pre-computed score based on development activity, maintenance, community, maturity, and trend momentum.How we score it →
Fair
  • Development activity44
  • Maintenance72
  • Community52
  • Maturity28
  • Momentum40

This skill loads a compact rule set inspired by Robert C. Martin’s Clean Architecture. It tells a coding agent to point source dependencies inward, keep entities and use cases free of framework types, and treat databases, web delivery and vendors as replaceable details.

It applies to code whose business rules should survive changes in frameworks, storage, delivery mechanisms and deployment shape.

What You Get

  • A mini rule set with decision rules, trigger rules and a closing checklist for architecture work
  • A full version of the rules for deeper architectural tradeoffs
  • A skill description that makes the agent load the rules for boundary, dependency and framework-isolation tasks

Common Use Cases

  • Moving business branching out of controllers, jobs and handlers into use cases
  • Introducing a policy-owned port in front of a database or service client
  • Replacing a shared common package with structure organised by use case
  • Reviewing a feature for framework types leaking into core logic

What Makes It Unique

The rules are written as trigger conditions, such as a use case that instantiates infrastructure or an adapter that bypasses a use case, each paired with the repair to make. They also ask for boundaries to be enforced by packages, build rules or tests, and for the lightest workable boundary when a full split costs too much. It sits beside the repository’s other architecture rule sets and focuses on dependency direction.

Under The Hood

The skill is a SKILL.md with a name and description, plus Markdown files holding the mini, nano and full versions of the rules. The SKILL.md tells the agent to read the mini file before design or code decisions and the full file only for harder tradeoffs. It contains no scripts. It does not fetch web pages, call APIs, run commands or write files; the agent only reads the rule text.

Join founders building with open source

Opinionated takes, migration guides, cost-saving tips, and insights from the open source ecosystem.

Subscribe on SubstackJoin 750+ subscribers