implicit-state-machines
Skill1 starsChanged 2 days agoLicence not identifiedView on GitHub
Finds an app's implicit state machines (state and transitions spread across booleans, status fields, nullables, timers, callbacks, webhooks, jobs and DB columns), verifies each one with a concrete sequence of events that breaks it and proposes the lightest fix that improves UX, DX and AX without breaking anything. Reports in the chat and stops; applies only what the user picks, test first. Use it for "find all of the implicit state machines in my app", "make state machines explicit" or the viral UX/DX/AX prompt, and also for impossible or invalid states, flag soup or boolean soup (isLoading/isError/hasData), a stuck loading spinner, async races, orders or jobs stuck in a status, statuses written from many places without a guard, or an audit of how the app handles its state, even if they never say "state machine". Not for designing a new machine from scratch. Also triggers on Spanish requests such as "busca las máquinas de estado implícitas", "haz explícitas las máquinas de estado" or "sopa de booleanos".
- Reads credentials
1 other project uses a version of this.
Adopted by
Most recently taken up by
- lmammino/agent-skillstheir own version, first seen Nov 15, 2026
Other versions1 project uses a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 1
- lmammino/agent-skills★ 4same name
How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.
In this repository10 other files it gives its agents.
- api-security-reviewSkill
- apply-remediationSkill
- architecture-reviewSkill
- code-structureSkill
- correctness-reviewSkill
- data-consistencySkill
- infra-reviewSkill
- llm-app-reviewSkill
- perf-diagnosisSkill
- repo-audit-swarmSkill
The file
Show its rules and text
We split this skill into the rules it gives an agent
16 rules. About 0 are common, 12 are distinctive, and 4 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈12
Distinctive · estimate
This author's own choices. Worth a look.
4
Very specific
Tied to their project's names, files or tools. Probably skip.
The licence could not be identified — read it at the source. We count its rules but don't quote them. Read them on GitHub.
≈ “Common” is an estimate: at least 1 in 5 of the 350,495 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.