Enterprise Architecture Pattern Stack Selector

When to Use

Use this skill at the start of enterprise application design or major refactoring, when a team needs to select consistent patterns across the domain-logic, data-source, web-presentation, concurrency, and session-state layers of an OO enterprise application backed by a relational database.

This is a router skill: it collects your context, routes each architectural layer to the appropriate pattern family, and produces a consolidated Pattern Stack Decision Record. If you have a specific layer question (e.g., only data-source patterns), use the targeted family selector skill instead.

Prerequisite check before starting:

• Do you know the target language and framework? (Java/Spring, Python/Django, Ruby/Rails, C#/.NET, TypeScript/Node, etc.)
• Can you describe the domain-logic complexity? (simple CRUD, moderate business rules, complex domain with many variations)
• Are there existing architectural commitments you cannot change? (existing ORM, existing schema, existing framework)

Context and Input Gathering

Required Context