Documents patterns and best practices for ccstate state management in the vm0 platform.
npx skills add https://github.com/vm0-ai/vm0 --skill ccstate
Please help me install this Agent Skill. Skill: ccstate Source: https://github.com/vm0-ai/vm0/tree/main/.claude/skills/ccstate Command: npx skills add https://github.com/vm0-ai/vm0 --skill ccstate
Developers working with ccstate in the vm0 platform repeatedly hit subtle bugs: floating promises in DOM handlers, functions silently executed instead of stored in state atoms, orphaned AbortSignals leaking polling loops, and manual HTTP error handling that duplicates framework behavior. This Skill codifies the correct patterns so these mistakes are avoided.
detach() with Reason.DomCallback in React views to handle fire-and-forget promises without lint errors or test cleanup leaks.computed(async ...) plus a reload counter, eliminating manual loading/error state.accept: Enforce a single, type-narrowed way to handle API status codes with automatic toast and ApiError semantics.pageSignal$, accept, and detach correctly on the first attempt.Ask the assistant to review your ccstate signals code and apply the documented patterns for detach, accept, and AbortSignal ownership.
High-intent search queries and answers about installing and using this skill.
Use detach() with Reason.DomCallback to mark the promise as intentionally fire-and-forget. This satisfies the no-floating-promises lint rule while tracking the promise for test cleanup via clearAllDetached().
Prefer a reactive computed(async ...) that reads a reload counter state, rather than an imperative fetch command with manual loading flags. Invalidate by bumping the counter, and consume with useLoadable or useLastResolved in views.
ccstate treats any function passed to set() as an updater and executes it immediately, storing the return value instead. Wrap the function in an updater that returns it: set(atom$, () => theFn).
Wrap every apiClient call in accept() with an explicit list of accepted status codes. Unlisted statuses automatically trigger a toast error and throw an ApiError, so manual try-catch and status checks are forbidden.
The AbortSignal likely has no parent owner, so nothing aborts it on navigation. Pass the page or route signal into resetSignal() so the loop is cancelled when the page unmounts or the route changes.
Use a factory when one page must host multiple independent instances of the same feature, such as several chat threads. Each factory call returns fresh state, computed, and command instances so instances never share state.
digirati-co-ukUpdate ApiClient wiring and gateway task definitions in Madoc TS.
zenbuappsValidate Zod schemas, API clients, and MSW handlers against api.yml contracts.
muratmirgunRename Go identifiers to follow idiomatic naming conventions.
algusaemGuide React state management across local, global, and server state.