scope-rule-architect-angular

What problem does it solve?

Provides a structured approach to building Angular 20+ applications by enforcing Scope Rule, Screaming Architecture, and the use of standalone components, ensuring consistent organization, naming, and maintainability.

Core Features & Use Cases

• Standalone Components First: ALL components SHOULD be standalone; modern Angular favors standalone components and inject() usage, coupled with signal-based state management.
• Modern Template Syntax: Use @if, @for, @switch, @defer, typed reactive forms, and avoid legacy NgModules for structure.
• The Scope Rule — Unbreakable Law: Code used by 2+ features MUST live in global/shared areas; code for a single feature stays local.
• Screaming Architecture: Directory structure should tell the business story; feature components must align with feature names.
• Decision Framework: Count feature usage, apply the rule, validate against best practices, and document decisions with rationale.
• Project Structure: Presents a complete layout for feature, shared, core, and routing with standalone patterns.
• Standalone Component Pattern: Demo patterns for using imports, signals, and inject() in standalone components.
• Service with Signals: Pattern for local and injectable services using signals for state management.
• Quality Checklist & Edge Cases: Migration strategies, lazy loading via standalone routes, and guardrails.

Quick Start

Follow the guide to implement a scalable Angular project using Scope Rule and standalone components.