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.