Angular State Management

Angular State Management

Comprehensive guide to modern Angular state management patterns, from Signal-based local state to global stores and server state synchronization.

When to Use

• The request matches the skill description: Master modern Angular state management with Signals, NgRx, and RxJS. Use when setting up global state, managing component stores, choosing between state solutions, or migrating from legacy patterns.
• The task needs the implementation patterns, examples, validation checks, or edge cases listed in the topic map.
• The work would benefit from the complete guidance preserved in references/full-guidance.md.

Core Workflow

1. Confirm the request matches this skill's trigger, scope, and risk profile.
2. Use the topic map to identify the relevant pattern, checklist, or example before writing detailed guidance or code.
3. Load references/full-guidance.md when implementation details, examples, anti-patterns, validation checks, or edge cases are needed.
4. Apply only the relevant guidance instead of loading or repeating the entire reference by default.
5. Verify the result against any validation checks, limitations, security notes, or platform constraints in the reference.

Topic Map

• When to Use This Skill
• Do Not Use This Skill When
• Core Concepts
• State Categories
• Selection Criteria
• Quick Start: Signal-Based State
• Pattern 1: Simple Signal Service
• Pattern 2: Feature Signal Store
• Pattern 3: SignalStore (NgRx Signals)
• NgRx Store (Global State)
• Setup
• Feature Slice Pattern
• Component Usage
• RxJS-Based Patterns
• Component Store (Local Feature State)
• Server State with Signals
• HTTP + Signals Pattern
• Best Practices

Reference Map

• references/full-guidance.md preserves the complete original guidance, including examples and detailed edge cases.

Limitations

• Use this skill only when the task clearly matches the scope described above.
• Do not treat the output as a substitute for environment-specific validation, testing, or expert review.
• Stop and ask for clarification if required inputs, permissions, safety boundaries, or success criteria are missing.

Progressive Loading

Keep this SKILL.md as the compact routing and workflow entrypoint. Load the reference file only when the user task requires the deeper implementation material.