Layered Architecture Boundaries

Purpose

Use this skill to analyze, design, or refactor Angular applications using explicit boundaries between UI, feature or application logic, state, services, data access, and core or platform concerns.

The goal is not to force one folder structure. The goal is to prevent responsibility leaks, circular dependencies, smart shared components, duplicated business logic, and architecture that only looks clean in diagrams.

When to Use

Use this skill when: