architecture-paradigm-layered

Use a Layered (N-Tier) architecture to separate presentation, domain logic, anddata access responsibilities within a system.Triggers: layered architecture, n-tier, separation of concerns, presentation layer,data access layer, service layer, traditional architecture, monolith structure,layer enforcement, dependency directionUse when: building traditional applications with clear boundaries, working withmoderate-sized teams, needing familiar and well-understood patterns, compliancerequirements demand clear separationDO NOT use when: selecting from multiple paradigms - use architecture-paradigms first.DO NOT use when: high scalability needs independent component scaling.DO NOT use when: teams need independent deployment cycles - use microservices.Consult this skill when implementing layered patterns or enforcing layer boundaries.