Loading skill
Install any skill in seconds. Free to start, no credit card required.
Get Started Free →vm0-ai/ccstate
Patterns and best practices for using ccstate state management in the vm0 platform
Passed 20 of 24 test cases with the skill, and 10 of 24 without it.
and 11 more in the full report
11 fixed9 passed either way3 still failing1 broke
Tokens, turns and time describe resource use, not a dollar price.
One of 11 test cases the skill fixed. Same model, same prompt, with and without the skill.
We are defining route setup logic for a checkout page state module. Where should the pageSignal$ reference be established and what owns it?
| Checked | Without skill | With skill |
|---|---|---|
| The route setup owns pageSignal$. | Missed | Passed |
The instructions your model reads when the skill loads.
Read the reference matching the changed behavior; API work does not require the React/DOM reference unless it also changes that surface.
| Task | Reference |
|---|---|
computed, memoization, function-valued state, reactive fetches | Reactive values |
API client status handling and accept | HTTP |
| AbortSignal ownership, cancellation, debouncing, detached cleanup | Lifecycle |
| DOM callbacks, page signals, refs and ref cleanup | React and DOM |
| Shared command logic and signal factories | Commands |
computed and semantic actions in commands. Do not create
signals or mutate the store during React render.setLoop
or setAbly*Loop$; those primitives own detach(..., Reason.Daemon) internally.
Use waitLoopUntil / waitAbly*LoopUntil$ when subsequent work needs completion.
Non-periodic background processes use setDaemon(operation, signal).
Other detach() calls belong at an actual outer boundary with their reason. Do not silence work with void.resetSignal() provides mutual exclusion. Add a parent when the work belongs
to a page/route lifetime; parentless use still needs an explicit owner that
cancels it. The lifecycle reference defines both valid patterns.accept with a non-empty status list for apiClient$ calls. Preserve
structured HTTP errors and use the view's loadable state for lifecycle UI.pageSignal$. Preserve stable callback refs and onRef
cleanup returns.See effects, cache, and Platform tests for the relevant broader contracts. For performance investigations, use React measurements.
test cases passed, vs 10 / 24 without
More skills from the same source and nearby in the registry, with their headline benchmark lift.