What problem does it solve?
It solves the confusion and inconsistency that teams face when building Angular components, especially when adopting modern patterns like standalone components, signals, inject-based dependency access, and zoneless change detection.
Core Features & Use Cases
- Standalone-first Angular architecture: Encourages component patterns suitable for modern Angular apps, including OnPush and clean separation of concerns.
- Signal-based state management: Recommends signals, computed, and effect for reactive UI state instead of lifecycle-driven patterns.
- Zoneless Angular setup: Guides adding zoneless change detection via provideZonelessChangeDetection and removing Zone.js assumptions.
- Preferred template and API boundaries: Enforces external templates and function-based input/output APIs to keep component code maintainable.
Use Case: You are creating a production Angular feature component and want reliable reactive behavior using signals, clean templates, and a zoneless runtime configuration without legacy lifecycle complexity.
Quick Start
Use the angular-core skill to generate an Angular component that uses standalone patterns, signals-based state, inject() for services, and zoneless change detection.