What problem does it solve? Angular developers working with version 16+ need consistent guidance on signals, standalone components, and new control flow syntax, while legacy patterns like NgModules, @Input decorators, and RxJS subscriptions still dominate older codebases and documentation. ## Core Features & Use Cases - Signal-Based Component Generation: Create standalone components using signal(), computed(), effect(), and signal-based input()/output() APIs. - Legacy Migration: Convert NgModule-based components, @Input/@Output decorators, structural directives, and RxJS state into modern signal-based equivalents. - State Management & Data Loading: Set up service-level signal state with asReadonly() encapsulation and declarative async loading via the resource() API (Angular 19+). - Use Case: Ask to convert an NgModule-based product list component to standalone with signals, and receive refactored code using input.required(), @for with track expressions, and computed derived values. ## Quick Start Ask the assistant to build an Angular component using signals and modern control flow, or to migrate a legacy component to standalone with signal-based inputs and outputs.