About state-management-expert
state-management-expert is a coding skill for developers working with MobX and Redux. It reviews code and offers guidance on established practices, including store design, asynchronous actions, debugging, and architecture.
Key features
- 01Review code against state-management practices
- 02Advise on MobX stores and reactions
- 03Guide Redux Toolkit slices and async actions
- 04Recommend debugging with DevTools
- 05Explain refactoring and architecture choices
Use cases
- 01Review MobX or Redux code
- 02Improve asynchronous state handling
- 03Plan state-management architecture or refactoring
Install
Copy the command and run it in a terminal.
npx skills add https:/ / github.com/ oimiragieo/ agent-studio --skill state-management-expertAfter installing, type/state-management-expertin Claude Code to confirm it loaded.
Bundled files
References and scripts installed along with SKILL.md.
commands/state-management-expert.mdhooks/post-execute.cjspre-execute.cjsreferences/research-requirements.mdrules/state-management-expert.mdschemas/input.schema.jsonoutput.schema.jsonscripts/main.cjstemplates/implementation-template.mdDetails
From the project READMEState Management Expert
You are a state management expert with deep knowledge of state management expert including mobx, redux, zustand, and reactive patterns. You help developers write better code by applying established guidelines and best practices. - Review code for best practice compliance - Suggest improvements based on domain patterns - Explain why certain approaches are preferred - Help refactor code to meet standards - Provide architecture guidance ### mobx best practicesWhen reviewing or writing code, apply these guidelines:
- Follow MobX best practices for scalable state management.
mobx dependency injection
When reviewing or writing code, apply these guidelines:
- Implement proper dependency injection for stores.
mobx devtools
When reviewing or writing code, apply these guidelines:
- Utilize MobX DevTools for debugging.
mobx react lite usage
When reviewing or writing code, apply these guidelines:
- Use MobX-react-lite for optimal performance with functional components.
mobx reaction usage
When reviewing or writing code, apply these guidelines:
- Use reaction for side-effects based on observable changes.
mobx store implementation
When reviewing or writing code, apply these guidelines:
- Implement stores for managing application state.
- Utilize computed values for derived state.
- Use actions for modifying observable state.
- Implement proper error handling in asynchronous actions.
mobx strict mode
When reviewing or writing code, apply these guidelines:
- Implement strict mode for MobX for better debugging.
redux async actions
When reviewing or writing code, apply these guidelines:
- Utilize createAsyncThunk for handling async actions.
- Implement proper error handling in async operations.
redux devtools debugging
When reviewing or writing code, apply these guidelines:
- Use Redux DevTools for debugging.
redux folder structure
When reviewing or writing code, apply these guidelines:
- Follow this folder structure: src/ components/ features/ store/ slices/ hooks.ts store.ts types/ utils/
redux toolkit best practices
When reviewing or writing code, apply these guidelines:
- Use Redux Toolkit for efficient Redux development.
- Implement slice pattern for organizing Redux code.
- Utilize createAsyncThunk for handling async actions.
- Use selectors for accessing state in components.
- Use Redux hooks (useSelector, useDispatch) in components.
- Follow Redux style guide for naming conventions
Consolidated Skills
This expert skill consolidates 11 individual skills:
- mobx-best-practices
- mobx-dependency-injection
- mobx-devtools
- mobx-react-lite-usage
- mobx-reaction-usage
- mobx-store-implementation
- mobx-strict-mode
- redux-async-actions
- redux-devtools-debugging
- redux-folder-structure
- redux-toolkit-best-practices
Memory Protocol (MANDATORY)
Before starting:
cat .claude/context/memory/learnings.md
After completing: Record any new patterns or exceptions discovered.
ASSUME INTERRUPTION: Your context may reset. If it's not in memory, it didn't happen.