Audit State Machine
ben-manes/caffeine
Audit explicit state machines (drain status, node lifecycle, async-value lifecycle) for illegal or missed transitions
Document UI component states (current vs expected) with transitions
$ npx skills add WellApp-ai/Well --skill state-machine -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install WellApp-ai/Well state-machine --agent claude-codeProject scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).
$ git clone --depth 1 https://github.com/WellApp-ai/Well.git skills-src && mkdir -p .claude/skills && cp -r skills-src/cursor-rules/skills/state-machine .claude/skills/state-machine && rm -rf skills-srcUse ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.
Claude Code skills documentation · loads skills from .claude/skills/
Install the "state-machine" agent skill from https://github.com/WellApp-ai/Well/tree/main/cursor-rules/skills/state-machine into .claude/skills/state-machine/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "state-machine", then confirm the skill loads.Claude Code copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$skill-installer install https://github.com/WellApp-ai/Well/tree/main/cursor-rules/skills/state-machineType this inside Codex. $skill-installer <name> installs a curated skill from openai/skills. The installer writes to $CODEX_HOME/skills (default ~/.codex/skills). Restart Codex if the skill does not show up.
$ npx skills add WellApp-ai/Well --skill state-machine -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install WellApp-ai/Well state-machine --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/WellApp-ai/Well.git skills-src && mkdir -p .agents/skills && cp -r skills-src/cursor-rules/skills/state-machine .agents/skills/state-machine && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "state-machine" agent skill from https://github.com/WellApp-ai/Well/tree/main/cursor-rules/skills/state-machine into .agents/skills/state-machine/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "state-machine", then confirm the skill loads.Codex copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add WellApp-ai/Well --skill state-machine -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install WellApp-ai/Well state-machine --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/WellApp-ai/Well.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/cursor-rules/skills/state-machine .cursor/skills/state-machine && rm -rf skills-srcUse ~/.cursor/skills/ instead of .cursor/skills for a personal install.
Cursor skills documentation · loads skills from .cursor/skills/, .agents/skills/, .claude/skills/, .codex/skills/
Install the "state-machine" agent skill from https://github.com/WellApp-ai/Well/tree/main/cursor-rules/skills/state-machine into .cursor/skills/state-machine/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "state-machine", then confirm the skill loads.Cursor copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gemini skills install https://github.com/WellApp-ai/Well.git --path cursor-rules/skills/state-machine--scope user (default) or --scope workspace; --path is the subfolder of the repo that holds the skill; --consent skips the security confirmation prompt.
$ npx skills add WellApp-ai/Well --skill state-machine -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install WellApp-ai/Well state-machine --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/WellApp-ai/Well.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/cursor-rules/skills/state-machine .gemini/skills/state-machine && rm -rf skills-srcUse ~/.gemini/skills/ instead of .gemini/skills for a personal install, then run /skills reload.
Gemini CLI skills documentation · loads skills from .gemini/skills/, .agents/skills/
Install the "state-machine" agent skill from https://github.com/WellApp-ai/Well/tree/main/cursor-rules/skills/state-machine into .gemini/skills/state-machine/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "state-machine", then confirm the skill loads.Gemini CLI copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gh skill install WellApp-ai/Well state-machineInstalls for Copilot at project scope by default; add --scope user for a personal install. Preview a skill first with gh skill preview. Needs GitHub CLI 2.90.0 or later (public preview).
$ npx skills add WellApp-ai/Well --skill state-machine -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/WellApp-ai/Well.git skills-src && mkdir -p .github/skills && cp -r skills-src/cursor-rules/skills/state-machine .github/skills/state-machine && rm -rf skills-srcUse ~/.copilot/skills/ instead of .github/skills for a personal install. Commit .github/skills so cloud agent and code review can use it.
GitHub Copilot skills documentation · loads skills from .github/skills/, .claude/skills/, .agents/skills/
Install the "state-machine" agent skill from https://github.com/WellApp-ai/Well/tree/main/cursor-rules/skills/state-machine into .github/skills/state-machine/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "state-machine", then confirm the skill loads.GitHub Copilot copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add WellApp-ai/Well --skill state-machine -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install WellApp-ai/Well state-machine --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/WellApp-ai/Well.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/cursor-rules/skills/state-machine .opencode/skills/state-machine && rm -rf skills-srcUse ~/.config/opencode/skills/ instead of .opencode/skills for a personal install.
OpenCode skills documentation · loads skills from .opencode/skills/, .claude/skills/, .agents/skills/
Install the "state-machine" agent skill from https://github.com/WellApp-ai/Well/tree/main/cursor-rules/skills/state-machine into .opencode/skills/state-machine/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "state-machine", then confirm the skill loads.OpenCode copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
state-machineDocument UI component states (current vs expected) with transitions
State Machine is an agent skill from WellApp-ai/Well. Document UI component states (current vs expected) with transitions
Its SKILL.md is about 1k tokens, which your agent loads only when the skill is triggered. It is a single SKILL.md file with no bundled scripts.
The repository describes itself as: No more Sundays on Finance. We build the infrastructure that retrieves, processes, and routes your financial and business data to your FinOps stack, so founders can ship, not… The licence is MIT.
5 steps, taken from the step headings in SKILL.md.
Read from SKILL.md and the folder at commit c740217. It shows what the files ask for, not the result of running them.
Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.
From allowed-tools in the SKILL.md frontmatter.
No scripts in the folder and no shell commands in SKILL.md (its code samples are mermaid and markdown).
From the folder's file list and the shell code blocks in SKILL.md.
No URLs in SKILL.md.
From URLs in SKILL.md, links to its own repository left out.
Names no API keys, tokens, secrets or passwords.
From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.
State Machine loads about 1k tokens when it runs. Until then it costs about 20 tokens; SKILL.md has 339 words of instructions outside code blocks.
Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.
The automated check found no risky patterns in SKILL.md.
Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.
The full file from WellApp-ai/Well at commit c740217, republished under its MIT licence (© WellApp-ai). 339 words, ~1,008 tokens.
.claude/skills/state-machine/SKILL.md (or your agent's skills folder).Document the state machine for UI components, comparing current behavior to expected behavior and mapping all state transitions.
List all possible states for the component:
| State | Current Behavior | Expected Behavior |
|---|---|---|
| Initial | [What happens now] | [What should happen] |
| Loading | [Current loading UX] | [Expected loading UX] |
| Success | [Current success display] | [Expected success display] |
| Error | [Current error handling] | [Expected error handling] |
| Empty | [Current empty state] | [Expected empty state] |
Common States to Consider:
| State Type | Examples |
|---|---|
| Data states | Initial, Loading, Success, Error, Empty, Stale |
| Interaction states | Idle, Hover, Focus, Active, Disabled |
| Visibility states | Hidden, Visible, Collapsed, Expanded |
| Selection states | Unselected, Selected, Partially selected |
| Validation states | Valid, Invalid, Pending validation |
Define what triggers each state change:
| From | To | Trigger | Side Effects |
|---|---|---|---|
| Initial | Loading | User action / Mount | Start fetch |
| Loading | Success | Data received | Populate UI |
| Loading | Error | Request failed | Show error message |
| Loading | Empty | Empty response | Show empty state |
| Error | Loading | Retry clicked | Restart fetch |
| Success | Loading | Refresh clicked | Refetch data |
Create a Mermaid state diagram:
stateDiagram-v2
[*] --> Initial
Initial --> Loading : fetch
Loading --> Success : data received
Loading --> Error : request failed
Loading --> Empty : no data
Error --> Loading : retry
Success --> Loading : refresh
Empty --> Loading : refresh
Success --> [*] : unmountFor each state, define what data is needed:
| State | Required Data | UI Elements |
|---|---|---|
| Initial | None | Placeholder or skeleton |
| Loading | None | Spinner, skeleton, progress |
| Success | [List required fields] | Full component |
| Error | Error message, retry action | Error banner, retry button |
| Empty | Empty message, CTA | Empty illustration, CTA button |
Identify edge cases and how to handle:
| Edge Case | Current | Expected |
|---|---|---|
| Network timeout | [Current] | Show timeout message, retry option |
| Partial data | [Current] | Graceful degradation, show available |
| Stale data | [Current] | Show stale indicator, background refresh |
| Concurrent updates | [Current] | Optimistic update, rollback on conflict |
| Auth expired | [Current] | Redirect to login, preserve state |
## State Machine: [Component Name]
### State Table
| State | Current | Expected | Data Required |
|-------|---------|----------|---------------|
| Initial | [Behavior] | [Behavior] | [Data] |
| Loading | [Behavior] | [Behavior] | [Data] |
| Success | [Behavior] | [Behavior] | [Data] |
| Error | [Behavior] | [Behavior] | [Data] |
| Empty | [Behavior] | [Behavior] | [Data] |
### Transition Diagram
[Mermaid stateDiagram]
### Edge Cases
| Case | Handling |
|------|----------|
| [Case] | [How to handle] |
### Summary
- States: [N] identified
- Transitions: [N] mapped
- Edge cases: [N] documentedInvoke manually with "use state-machine skill" or follow Ask mode CONVERGE loop which references this skill.
qa-planning - Uses states to define test coveragedesign-context - Check existing component states in Storybook© WellApp-ai, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file
Just SKILL.md in cursor-rules/skills/state-machine of WellApp-ai/Well.
Open the folder on GitHubat commit c740217
State Machine next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.
| Skill | Stars | Used in | Tokens | Auto-check | Licence | Repo updated |
|---|---|---|---|---|---|---|
| State Machine this skillWellApp-ai/Well | 345 | — | ~1k | Automated safety check: Pass | MIT | |
| Audit State Machineben-manes/caffeine | 18k | — | ~1.1k | Automated safety check: Pass | Apache-2.0 | |
| State MachineOwl-Listener/designer-skills | 2.9k | 1 repos | ~488 | Automated safety check: Pass | MIT | |
| State Machinejame581/GodotPrompter | 795 | — | ~3.5k | Automated safety check: Pass | MIT | |
| View Transitionsthedaviddias/Front-End-Checklist | 74k | — | ~528 | Automated safety check: Pass | MIT | |
| Vercel React View Transitionssickn33/agentic-awesome-skills | 47k | 1 repos | ~3.1k | Automated safety check: Pass | MIT |
ben-manes/caffeine
Audit explicit state machines (drain status, node lifecycle, async-value lifecycle) for illegal or missed transitions
Owl-Listener/designer-skills
Model component behaviour as explicit states, events, and transitions.
jame581/GodotPrompter
A skill your agent uses when implementing state machines in Godot — enum-based, node-based, and resource-based FSM patterns with trade-offs
thedaviddias/Front-End-Checklist
A skill your agent uses when adding page transition animations, image expand/contract effects, shared-element transitions, or improving navigation UX in a single-page or multi-page application.
sickn33/agentic-awesome-skills
Guide React and Next.js view transitions, shared element animations, route transitions, transition types, and reduced-motion-safe UI state animation.
sickn33/agentic-awesome-skills
CRITICAL: Use for Robius state management patterns. An agent skill from sickn33/agentic-awesome-skills.
WellApp-ai/Well
Evaluate technical options with scoring matrix, trigger Gate 4 for significant decisions
WellApp-ai/Well
Produce an accounts-receivable aging report and surface overdue invoices for a Well workspace.
WellApp-ai/Well
Iterate until success or limit, composing existing skills with Jidoka integration
WellApp-ai/Well
Build a balance sheet (bilan) from a Well workspace. An agent skill from WellApp-ai/Well.
WellApp-ai/Well
Generate and maintain BPMN 2.0 diagrams linked to Gherkin scenarios
WellApp-ai/Well
Forecast cash flow and runway for a Well workspace from booked invoices and collected bank transactions.
Document UI component states (current vs expected) with transitions. State Machine is an agent skill from WellApp-ai/Well.
Run `npx skills add WellApp-ai/Well --skill state-machine -a claude-code`. Or copy the skill folder (cursor-rules/skills/state-machine in WellApp-ai/Well) into .claude/skills/state-machine in your project. Claude Code loads it when a task matches its description.
Run `npx skills add WellApp-ai/Well --skill state-machine -a codex`. Or copy the skill folder (cursor-rules/skills/state-machine in WellApp-ai/Well) into .agents/skills/state-machine in your project. Codex loads it when a task matches its description.
Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add WellApp-ai/Well --skill state-machine -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/state-machine, .gemini/skills/state-machine, .github/skills/state-machine and .opencode/skills/state-machine in your project.
SKILL.md names no scripts, command-line tools or credentials: State Machine is instructions for the agent only.
SKILL.md contains no URLs. Any network use would come from the scripts or tools the agent runs. This is read from the text; nothing was executed.
Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.
State Machine is published under the MIT licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.
About 1k tokens (SKILL.md is roughly 4k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.
Skills that share tags, products or a category with State Machine: Audit State Machine (ben-manes/caffeine, 18k stars), State Machine (Owl-Listener/designer-skills, 2.9k stars), State Machine (jame581/GodotPrompter, 795 stars) and View Transitions (thedaviddias/Front-End-Checklist, 74k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
WellApp-ai (a GitHub organization) maintains it in WellApp-ai/Well, which has 345 GitHub stars. The repository holds 36 skills in this directory. The repository was last updated on October 7, 2026.
Source: WellApp-ai/Well on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.