owl-listener/state-machine
interaction-design/skills/state-machine/SKILL.md
Model complex UI behavior as finite state machines with states, events, and transitions.
$ install --global
skillsauthnpx skillsauth add owl-listener/designer-skills state-machineInstall this skill globally with one command. Works with Claude Code, Cursor, and Windsurf.
Security Scan Results
3 of 9 scanners reported clean
Some scanners were skipped, did not run, or reported a non-clean status. Review each row below.
3
Scanners Passed
9
Scanners in report
Clean
TrivyContainer and dependency vulnerability scanner
95%
Clean
SemgrepStatic code analysis for vulnerabilities
95%
Clean
mcp-scan (Snyk)Model Context Protocol security validation
95%
Skipped
Snyk (dep)Open source security scanning
50%
Skipped
Socket.devSupply chain security analysis
50%
Skipped
VirusTotalMulti-engine malware detection
50%
Skipped
CrowdStrikeAdvanced threat intelligence
50%
Skipped
OSV-ScannerOpen Source Vulnerability database check
50%
Skipped
OWASP Dep-Check
50%
Last scanned: May 15, 2026, 5:31 AM103.5s1 file scanned
SKILL.md
- name:
- state-machine
- description:
- Model complex UI behavior as finite state machines with states, events, and transitions.
State Machine
You are an expert in modeling complex UI behavior as finite state machines.
What You Do
You model UI components and flows as state machines to eliminate impossible states and make behavior predictable.
State Machine Components
- States: Distinct modes the UI can be in (idle, loading, success, error)
- Events: Things that cause transitions (click, submit, timeout, response)
- Transitions: Rules for moving between states (on event X in state A, go to state B)
- Actions: Side effects during transitions (fetch data, show toast, log event)
- Guards: Conditions that must be true for a transition (isValid, hasPermission)
Common UI State Machines
Form
idle -> editing -> validating -> submitting -> success/error -> idle
Data Fetching
idle -> loading -> success/error, error -> retrying -> success/error
Authentication
logged-out -> authenticating -> logged-in -> logging-out -> logged-out
Multi-Step Wizard
step1 -> step2 -> step3 -> review -> submitting -> complete
Modeling Approach
- List all possible states
- List all events/triggers
- Define valid transitions
- Identify impossible states to prevent
- Add guards for conditional transitions
- Define entry/exit actions per state
Benefits
- Eliminates impossible states (no loading + error simultaneously)
- Makes edge cases visible
- Shared language between design and engineering
- Testable behavior specification
Best Practices
- Start with the happy path, then add error states
- Every state should have a way out (no dead ends)
- Keep state machines focused (one per concern)
- Document with visual diagrams
- Map each state to a UI representation
Related Skills
owl-listener/critique-visual-hierarchy
tools
VerifiedTrustedCommunity
Critique a screen's visual hierarchy — entry point, eye flow, weight distribution, and emphasis.
1,265SKILL.mdUpdated May 15, 2026
owl-listener/critique-typography
tools
VerifiedTrustedCommunity
Critique a screen's typography — scale usage, readability, consistency, and token compliance.
1,265SKILL.mdUpdated May 15, 2026
owl-listener/critique-composition
testing
VerifiedTrustedCommunity
Critique a screen's composition — balance, whitespace, rhythm, and gestalt principles.
1,265SKILL.mdUpdated May 15, 2026
owl-listener/critique-brand-consistency
data-ai
VerifiedTrustedCommunity
Critique a screen's brand consistency against mood.md, voice.md, and tokens.md.
1,265SKILL.mdUpdated May 15, 2026