angular-ngrx-patterns

Align new NgRx actions, reducers, effects, selectors, and facades with existing project patterns.

Updated Feb 7, 2026

Search Tags:#angular #patterns #state-management #ngrx #code-consistency #architectural-guidance

Ready to run

npx skills add https://github.com/lorrandavid/.dotfiles --skill angular-ngrx-patterns

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: angular-ngrx-patterns
Source: https://github.com/lorrandavid/.dotfiles/tree/main/.config/.copilot/skills/angular-ngrx-patterns
Command: npx skills add https://github.com/lorrandavid/.dotfiles --skill angular-ngrx-patterns

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

The Copilot agent enforces NgRx best practices while adapting to the project's existing NgRx implementation, prioritizing consistency over introducing new paradigms.

Core Features & Use Cases

Inspect and align actions, reducers, effects, selectors, and facades with the prevailing NgRx style to avoid architectural drift.
Preserve consistency across NgRx-related code by modeling around existing patterns (e.g., createReducer, switch(action.type), centralized selectors, and entity adapters).
Provide guidance that helps engineers extend or modify NgRx implementations without introducing fragmentation or incompatible paradigms.

Quick Start

Analyze the project's NgRx codebase and implement changes that mirror the established NgRx style.

Frequently Asked Questions about angular-ngrx-patterns

High-intent search queries and answers about installing and using this skill.

FAQPage Schema

How do I enforce NgRx best practices and consistency across my Angular codebase?▼

To enforce NgRx consistency, align new code with the project's established NgRx implementation patterns. This approach inspects existing actions, reducers, effects, selectors, and facades to prevent architectural drift while extending functionality.

What is architectural drift in NgRx and how do I avoid it when adding new state management features?▼

Architectural drift in NgRx occurs when developers introduce incompatible paradigms or fragmented styles. You avoid it by inspecting existing NgRx patterns, such as createReducer or centralized selectors, and mirroring that prevailing style for new features.

How do I modify NgRx actions, reducers, and effects without disrupting the existing code structure?▼

To modify NgRx actions, reducers, and effects without disruption, model changes around the project's existing implementation. This ensures new code mirrors the established style, like switch(action.type) or entity adapters, maintaining consistency and reducing fragmentation.

Does this approach work with both modern createReducer syntax and traditional switch statements for NgRx state management?▼

Yes, this approach works with both modern createReducer syntax and traditional switch statements. It inspects your specific NgRx codebase to identify the prevailing style and provides non-disruptive guidance to mirror that exact pattern for consistency.

When should I not introduce new NgRx paradigms to my Angular application?▼

You should not introduce new NgRx paradigms when your project already has an established state management style. Prioritizing consistency over new patterns prevents fragmentation, ensuring actions, reducers, effects, selectors, and facades remain unified.