Angular Enterprise Architecture

Use this skill for Angular architecture decisions before applying general Angular implementation guidance. If this skill conflicts with angular-developer, this skill wins for architecture, dependency direction, folder placement, and lazy/eager boundaries.

Always Apply

• Keep the eager app minimal: main.ts, app.*, core/, and layout/.
• Implement every user-facing business flow as a lazy feature/<feature-name>/, even if the app currently has only one feature.
• Keep sibling lazy features isolated. A feature must not import implementation from another feature.
• Preserve a one-way dependency graph: more specific blocks may depend on simpler/shared blocks, never the reverse.
• Share by extracting one level up, not by importing sideways.
• Do not use feature-shared. A normal parent feature folder covers sharing between its own lazy sub-features.
• Implement automatic validation with the latest project-compatible eslint-plugin-boundaries flat config. Use the references in this skill as the starting point, then verify against the current JS Boundaries docs/package version before finalizing.

Reference Routing