> angular-state-management
Signals-based state management and NgRx Signal Store. Use when managing application state with Angular Signals or NgRx Signal Store. (triggers: **/*.store.ts, **/state/**, angular signals, signal store, computed, effect)
curl "https://skillshub.wtf/HoangNguyen0403/agent-skills-standard/angular-state-management?format=md"State Management
Priority: P1 (HIGH)
Principles
- Signals First: Use Signals for all local and shared state.
- Computed: Derive state declaratively using
computed(). - Services: For simple apps, a service with
signalproperties is sufficient. - Signal Store: For complex features, use
@ngrx/signals(Signal Store) over Redux boilerplate.
Guidelines
- Immutability: Treat signal values as immutable. Update using
.set()or.update(). - Effects: Use
effect()sparingly (e.g., logging, syncing to localStorage). Do not cascade state updates in effects.
Anti-Patterns
- Component State: Avoid heavy state logic in components. Delegate to a Store/Service.
- RxJS
BehaviorSubject: Deprecated for state (use Signals). Use RxJS only for complex event streams.
References
> related_skills --same-repo
> typescript-tooling
Development tools, linting, and build config for TypeScript. Use when configuring ESLint, Prettier, Jest, Vitest, tsconfig, or any TS build tooling. (triggers: tsconfig.json, .eslintrc.*, jest.config.*, package.json, eslint, prettier, jest, vitest, build, compile, lint)
> typescript-security
Secure coding practices for TypeScript. Use when validating input, handling auth tokens, sanitizing data, or managing secrets and sensitive configuration. (triggers: **/*.ts, **/*.tsx, validate, sanitize, xss, injection, auth, password, secret, token)
> typescript-language
Modern TypeScript standards for type safety and maintainability. Use when working with types, interfaces, generics, enums, unions, or tsconfig settings. (triggers: **/*.ts, **/*.tsx, tsconfig.json, type, interface, generic, enum, union, intersection, readonly, const, namespace)
> typescript-best-practices
Idiomatic TypeScript patterns for clean, maintainable code. Use when writing or refactoring TypeScript classes, functions, modules, or async logic. (triggers: **/*.ts, **/*.tsx, class, function, module, import, export, async, promise)