What problem does it solve?
Standardizes the creation and refactoring of Angular v20+ standalone components so teams can avoid inconsistent patterns, inline templates, and fragile class-based inputs while ensuring maintainability, signal-driven state, and accessibility compliance.
Core Features & Use Cases
- Signal-based Inputs & Outputs: Encourage input.required, input defaults, computed values, and output/outputFromObservable for predictable component APIs.
- Separation of Concerns: Enforce external HTML templates for all components and keep TypeScript files focused on logic and signals.
- Host Bindings & Events: Use the host object for attributes, class/style bindings, aria attributes, and keyboard/event listeners.
- Accessibility & Performance: Require WCAG AA support, AXE checks, keyboard navigation, visible focus indicators, OnPush change detection, and NgOptimizedImage for images.
- Use Case: Build interactive UI primitives like accessible buttons, toggles, cards, and user-cards or refactor legacy class-based inputs to signal-based APIs.
Quick Start
Generate a new Angular standalone component named user-card with signal inputs for name and email, a separate HTML template, OnPush change detection, host bindings for accessibility, and WCAG AA compliance.