state-machines
Find the implicit state machines in a codebase (lifecycles spread across booleans, status strings, nullable fields, effects and handlers), show which states conflict with exact lines, then make them explicit as a checked spec and a pure transition function with IO at the edge. Use for "find all the implicit state machines in my app", "which states can conflict", "make this state explicit", "model this as a state machine", "review this state machine", or before an agent builds anything with a lifecycle (loading/error, forms, modals, auth, checkout, uploads, jobs, sync, agent loops).
- Version
- 0.1.0
- License
- MIT
Pinned to revision a713fa19e489, so it is the text this page describes rather than whatever the author pushed since.
Files
- skills/state-machines/SKILL.md
- skills/state-machines/references/refactor.md
- skills/state-machines/references/signals.md
- skills/state-machines/references/spec-format.md
- skills/state-machines/scripts/check-machine.py
- skills/state-machines/scripts/find-candidates.sh
- skills/state-machines/scripts/signal-patterns.tsv
Every link opens the file at its source, pinned to the revision this page describes.