Skip to content
SkillModel-led124 tokens in use

Patterns of Enterprise Application Architecture

Martin Fowler-inspired rules for choosing layers, service layers, domain models, mappers, units of work and DTOs.

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

Install command as written in the repository's README

Skill label

measured from its files

What installing Patterns of Enterprise Application Architecture costs

37tokens idle
124tokens in use
4,475tokens, 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
  • Size15/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 Martin Fowler’s Patterns of Enterprise Application Architecture. It tells a coding agent to make responsibilities explicit before it names patterns, so the framework, ORM or schema does not pick the design.

It covers business logic patterns, persistence patterns, transactions, concurrency, remote boundaries, integration and session state.

What You Get

  • A mini rule set with decision rules, trigger rules and a closing checklist for enterprise architecture work
  • A nano version for tight context budgets and a full version for reference
  • A skill description that makes the agent load the rules for layering, persistence and transaction tasks

Common Use Cases

  • Choosing between transaction script and domain model for a feature
  • Placing transaction ownership in a service layer and keeping remote calls outside transactions
  • Introducing a repository, mapper or gateway to centralise SQL and saves
  • Replacing chatty remote APIs with coarse use-case contracts and DTOs

What Makes It Unique

It is a pattern-selection guide, with the force that justifies each pattern and the situation where it becomes a review blocker, such as a pass-through layer or an ORM model doubling as DTO. It covers concurrency, offline locks and session state, which the repository’s other architecture rule sets leave out.

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