What is the recommended way to name states and events?

The skill recommends naming states by what the machine is currently doing (e.g., 'submitting') rather than what happened, and using dot-notation for events (e.g., 'form.submit') to allow for wildcard transitions.

Does this skill support XState v4?

This skill is specifically optimized for XState v5 patterns, focusing on the latest standards such as the setup() API, promise actors, and updated transition syntax.

When should I use a state instead of context according to this skill?

Use states for mutually exclusive modes that change which events are possible or change the machine's behavior. Use context for quantitative data like strings, numbers, or lists that don't gate transitions.

How does this help with error handling in state machines?

It implements a 'Missing Error States' check, ensuring that every long-running task or actor has an explicit onError transition to prevent the machine from getting stuck in a loading state.

XState Machine Modeling

Name: XState Machine Modeling
Author: IlyaGulya

byIlyaGulya

0•

Developer Tools

Designs and models robust XState v5 state machines using a systematic architectural process for predictable application logic.

This skill provides a structured methodology for building XState v5 machines, helping developers navigate complex state management by clearly distinguishing between states and context, and actions and actors. It guides users through a comprehensive five-step modeling process—from event listing to iterative state construction—ensuring that applications avoid common anti-patterns like boolean 'flag-based' logic and unhandled error states. Whether you are building a multi-step form or a complex data-fetching service, this skill ensures your logic is predictable, testable, and scalable.

Key Features

01Architectural guidance on State vs. Context selection

020 GitHub stars

03Standardized event namespacing and state naming conventions

04Systematic 5-step modeling process for XState v5

05Identification and prevention of common state machine anti-patterns

06Decision framework for choosing Actions vs. Actors

Use Cases

01Refactoring legacy 'boolean soup' logic into clean finite state machines

02Designing complex multi-step forms with validation and submission logic

03Modeling robust data fetching flows with retry logic and error handling

What are Skills?·How to Install

Install with 🐟 Skill.Fish

npx skillfish add ilyagulya/claude-marketplace xstate-machine-modeling

For use in Claude.ai and ChatGPT

Download Skill