State Machine

Renders every state of a component you choose on a throwaway page, with mock data and a switcher, so you can work on each state.

12,359 stars 483 forksFrontend & Design Plugin marketplace

Install

Claude Code plugin
/plugin marketplace add jakubkrehel/skills

The repo is a Claude Code plugin marketplace. Run /plugin afterwards to pick the plugin that includes this skill.

skills CLI (Claude Code, Cursor, Codex and more)
npx skills add jakubkrehel/skills --skill state-machine
Manual install
git clone --depth 1 https://github.com/jakubkrehel/skills.git /tmp/skills
mkdir -p ~/.claude/skills
cp -r /tmp/skills/skills/state-machine ~/.claude/skills/state-machine

Personal skills live in ~/.claude/skills. Use .claude/skills in a project folder to share a skill with your team.

From the SKILL.md

# State machine

This skill takes one component and renders it on a throwaway page in every state it can be in. Mock data feeds each state, a switcher flips between them and the page is deleted in one step when you are done.

It is a workbench, not a review. The page stays up while the user works on the visuals, one state on screen and every other a keypress away. Stacking hostile scenarios on one page for a single look is `break`, exploring alternative designs is `variant` and reviewing finished work is `interface-review`.

## 1. Scope one component

One component per run: the audit log table, the network panel, the billing card. "The settings page" spans several, so list them and ask which one.

Restate it in one sentence: what the component shows, where it renders in production and where its data comes from.

## 2. Find the states in the code

The states are the branches the component already has. Read it and its data hooks for every one:

| Kind | States |
| --- | --- |
| Data | Loading, empty, error, one item, a typical set, a set long enough to scroll or paginate, some requests resolved and others pending, stale data refetching |
| Account | Plan tier, role and permission checks, an owner versus a member |
| Feature | Flags, trials, limits reached, a disabled or locked feature |

A state the code cannot reach is not a state. Do not add a branch to render one. Where the design shows a state the code lacks, list it as missing and leave it out.
Read the full skill on GitHub

Details

Skill name
state-machine
Path
skills/state-machine/SKILL.md
License
MIT
Repo updated
18 November 2026

FAQ

What does the State Machine skill do?

Renders every state of a component you choose on a throwaway page, with mock data and a switcher, so you can work on each state.

How do I install the State Machine skill?

Claude Code plugin: /plugin marketplace add jakubkrehel/skills. Skills go in ~/.claude/skills (personal) or .claude/skills (project), and Claude loads them automatically when a task matches the description.

Is State Machine popular?

It lives in jakubkrehel/skills, which has 12,359 GitHub stars and 483 forks.

Related skills

Browse the most popular Claude skills, all frontend & design skills, or write your own with the skills generator.