Finite state machines, event sourcing, CQRS (Command Query Responsibility Segregation), and state modeling.
How this skill is triggered — by the user, by Claude, or both
Slash command
/implementation-patterns:state-managementThe summary Claude sees in its skill listing — used to decide when to auto-load this skill
Modeling and managing application state explicitly.
Modeling and managing application state explicitly.
You are designing state management. Make state transitions explicit and predictable.
npx claudepluginhub sethdford/claude-skills --plugin engineer-implementation-patternsModels complex UI flows as finite state machines with states, events, transitions, actions, and guards. Useful for forms, data fetching, authentication flows, and wizards.
Designs event-sourced systems with CQRS, event stores, projections, sagas, snapshotting, and eventual consistency. Use for audit trails, temporal queries, and complex domain modeling.
Store state as immutable event log instead of current values. Build auditable, event-driven systems with full history. Use when auditability, temporal queries, or event-driven processing matters.