← LeaderboardThe Skill Leaderboard

patterns-of-enterprise-application-architecture

Apply Martin Fowler-inspired enterprise architecture rules when choosing layers, service layers, transaction scripts, domain models, repositories, mappers, or DTOs.

Published by ciembor ↗ciembor/agent-rules-books

Try your first task

patterns-of-enterprise-application-architecture

Start a fresh conversation. Replace the highlighted placeholders.

Use patterns-of-enterprise-application-architecture to design the enterprise architecture for [feature or system], producing a concise recommendation for layers, business-logic and persistence patterns, DTO/boundary design, and explicit transaction ownership based on its complexity and integration needs.

Required inputs

  • [feature or system]

User-approved starter prompt based on a pinned source version; check current skill requirements before running. Task evidence ↗

SKILL.md

name: patterns-of-enterprise-application-architecturedescription: Apply Martin Fowler-inspired enterprise architecture rules when choosing layers, service layers, transaction scripts, domain models, repositories, mappers, or DTOs.license: MIT

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.