NgRx Signal Store

Modern, lightweight, signal-based state management for Angular. This skill produces idiomatic, type-safe, well-architected @ngrx/signals code.

When to use this skill

Trigger on any of these signals:

• The user names the API: signalStore, signalStoreFeature, withState, withMethods, withComputed, withHooks, withProps, withEntities, rxMethod, signalMethod, patchState, getState, signalState.
• The user wants to refactor a service that uses BehaviorSubject/Subject or a class with mutable fields into a Signal Store.
• The user asks for feature/page state in Angular and either mentions Angular Signals or asks for a "modern" approach.
• The user wants a custom store feature (withRequestStatus, withSelectedEntity, withLogger, etc.) or asks how to compose features.
• The user asks about optimistic updates, request status, entity collections, or CRUD against an HTTP API in an Angular feature.

Do NOT use for classic @ngrx/store (actions, reducers, effects, separate-file selectors), Redux DevTools wiring without Signal Store, or pure RxJS pipeline questions.

Mental model

A Signal Store is a tree of composed features. Each feature contributes some combination of state, computed signals, methods, props, and lifecycle hooks. Composition happens at definition time: