Install any skill in seconds. Free to start, no credit card required.
Get Started Free →velcrafting/state-modeling
Define client state shape and transitions for non-trivial UI flows (multi-step, branching, async, derived state).
Passed 18 of 21 test cases with the skill, and 15 of 21 without it.
3 fixed16 passed either way3 still failing0 broke
Tokens, turns and time describe resource use, not a dollar price.
One of 3 test cases the skill fixed. Same model, same prompt, with and without the skill.
We have a user profile editing form state machine with states `idle`, `editing`, and `saving`. A user clicks 'Cancel' while in the `saving` state or 'Submit' while in the `idle` state. How should these event-to-state mappings be defined?
| Checked | Without skill | With skill |
|---|---|---|
| Every event explicitly maps to a deterministic next state or explicit no-op for every defined state. | Missed | Passed |
| Cancellation and reset pathways are explicitly defined for active states. | Passed | Passed |
The instructions your model reads when the skill loads.
Make non-trivial UI state explicit and testable by defining:
Use when UI behavior is more than “render props and call an API”.
<repo>/REPO_PROFILE.jsontest cases passed, vs 15 / 21 without
More skills from the same source and nearby in the registry, with their headline benchmark lift.