redux-state-generator

Generate Redux slices, thunks, selectors, and hooks from domain use cases.

1|Updated Apr 27, 2026
One-click install
npx skills add https://github.com/Saurav-snapwork/NewAppTemplate --skill redux-state-generator
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: redux-state-generator
Source: https://github.com/Saurav-snapwork/NewAppTemplate/tree/main/.github/skills/redux-state-generator
Command: npx skills add https://github.com/Saurav-snapwork/NewAppTemplate --skill redux-state-generator

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill automates the generation of a complete Redux state layer for a feature by deriving a consistent slice shape, thunks, selectors, and presentation hooks from domain use cases, ensuring clean architecture boundaries.

Core Features & Use Cases

  • Auto-generates a per-feature state slice using Redux Toolkit with typed data, status, and error fields for each async use case.
  • Co-locates all thunks inside the slice file and enforces delegation to use cases, never performing I/O directly.
  • Produces selectors for every field and derived async-state helpers for UI integration.

Quick Start

Run the Redux State Generator after Domain Extraction to scaffold the feature's state layer.

Frequently Asked Questions about redux-state-generator

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

FAQPage Schema
How do I generate a Redux Toolkit slice with typed thunks and selectors from use cases?

You scaffold a Redux Toolkit slice by deriving typed data, status, and error fields from domain use cases, co-locating thunks inside the slice file to enforce delegation and clean architecture boundaries.

What is the best way to enforce clean architecture boundaries in Redux state management?

Enforcing clean architecture in Redux state management requires thunks to delegate to use cases without performing direct I/O, ensuring state remains serializable and data-source access stays outside the slice.

Do I need domain-use-case types before scaffolding Redux state layers?

Yes, domain-use-case types are required to scaffold Redux state layers, because this Skill derives a complete slice, thunks, selectors, and presentation hooks for each async operation from them.

How does Redux Toolkit state generation handle selectors and presentation hooks?

Redux Toolkit state generation produces selectors for every state field alongside derived async-state helpers, creating presentation hooks that integrate seamlessly with UI components in React projects.

Can I use this Redux state generation approach for projects without clean architecture?

This Redux state generation approach targets React/Redux projects following clean architecture, so using it without these boundaries may result in mismatched thunk delegation and improper data-source separation.