xstate-system

Manage XState v5 actor systems for cross-actor communication and global addressing.

Updated Feb 12, 2026
One-click install
npx skills add https://github.com/IlyaGulya/claude-marketplace --skill xstate-system
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: xstate-system
Source: https://github.com/IlyaGulya/claude-marketplace/tree/main/plugins/xstate/skills/xstate-system
Command: npx skills add https://github.com/IlyaGulya/claude-marketplace --skill xstate-system

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill addresses the complexity of managing communication between different actors in XState v5, especially when direct parent-child relationships are insufficient or undesirable.

Core Features & Use Cases

  • Cross-Actor Communication: Enables actors to communicate regardless of their hierarchical position within the system.
  • Global Actor Addressing: Allows actors to be registered with unique systemIds and retrieved globally using system.get().
  • Use Case: In a complex application, a notification actor might need to send messages to various UI components (actors) that are not direct children. This Skill facilitates such communication patterns.

Quick Start

Use the xstate-system skill to send a 'notify' event with message 'Form submitted!' to the actor with systemId 'notifier'.

Frequently Asked Questions about xstate-system

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

FAQPage Schema
How do I manage communication between XState actors that are not in a parent-child hierarchy?

To enable cross-actor communication in XState v5, register actors with unique systemIds for global addressing. This allows any actor to retrieve and communicate with another using system.get(), bypassing strict parent-child hierarchies.

What is global actor addressing in XState and when do I need it?

Global actor addressing in XState assigns unique systemIds to actors for system-wide access. You need it when components like a notification actor must send messages to UI actors that are not direct children in the hierarchy.

How do I send a message to a specific actor using XState system.get()?

You send a message to a specific actor by retrieving it with system.get() using its registered systemId. Once retrieved, you can directly send events, such as a notify event with a message payload, to that actor.

Does XState v5 support communication between actors outside their parent-child hierarchy?

Yes, XState v5 supports communication beyond parent-child hierarchies by utilizing actor systems. Actors can be registered with unique systemIds and accessed globally to facilitate complex cross-actor communication patterns.

What are the limitations of using systemIds for XState actor communication?

Using systemIds for XState actor communication requires actors to be registered before they can be retrieved with system.get(). This approach manages global addressing but depends on the system hierarchy being properly established.