Apply Martin Fowler-inspired enterprise architecture rules when choosing layers, service layers, transaction scripts, domain models, repositories, mappers, or DTOs.
SkillScore100Maintained
Automatic
◆Coding pack
Last verified 10/10/2026
What it changes
Passed 23 of 23 test cases with the skill, and 22 of 23 without it.
Without skill96%
With skill100%
Checks it passed that the model alone missed
Recommends the Data Transfer Object pattern.
1 fixed22 passed either way0 still failing0 broke
Pass-rate lift
+4 pp
Tokens
-17%
Agent turns
0%
Response time
-23%
Model gemini-3.6-flashMeasured 10/10/2026v123 of 23 cases passed with skill
Tokens, turns and time describe resource use, not a dollar price.
See it in action
A test case the skill fixed. Same model, same prompt, with and without the skill.
Prompt
An enterprise dashboard aggregating customer profile, order history, and support tickets needs to gather data from three distinct domain services into a single payload sent across the network. Identify the pattern and explain its role.
What was checked, without and with the skill
Checked
Without skill
With skill
Recommends the Data Transfer Object pattern.
Missed
Passed
Explains aggregating attributes from multiple entities into a single transport object.
Passed
Passed
case-19 · gemini-3.6-flash · 10/10/2026 · answers are capped and redacted
What's inside
The instructions your model reads when the skill loads.
SKILL.md5 linessingle file
Patterns of Enterprise Application Architecture Skill
Use this skill when a task involves enterprise application structure, layering, service layer, transaction script, domain model, data mapper, repository, unit of work, identity map, DTOs, or integration patterns.
Before making design or code decisions, read and apply patterns-of-enterprise-application-architecture.mini.md. Use patterns-of-enterprise-application-architecture.md only as a deeper reference when the mini rules are not enough for the current enterprise-pattern tradeoff.