reatom-skill

Local maintenance workflow for this reatom-skill repo. Use when processing feedback sessions, failed model transcripts, correction threads, or bootstrap postmortems into durable skill/reference/eval improvements. Extract misconceptions, identify instruction-shape failures, generalize fixes without project-specific leakage, and maintain repo-local guidance. Git may be used only for read-only exploration; never touch the index, staged changes, or commits.

Review uncommitted changes in this reatom-skill repo when the task is to inspect modified skill docs, references, evals, or README text for skill quality. Use for requests to review local changes, align them with skill best practices, validate Reatom-specific claims against ~/ghq/github.com/reatom/reatom, and rewrite edits so they read naturally in the target document without session-specific leakage or stray project-only details.

Structured debugging workflow for Reatom v1000+ runtime, routing, React, and test failures. Use when behavior feels surprising, errors mention missing async stack, AbortError, root/provider setup, route ownership, duplicate @reatom packages, or when a Reatom app needs a source-backed debug plan that first verifies observability, including dev-time connectLogger setup.

Follow-up correction and skill-improvement workflow for Reatom guidance. Use when the user says earlier Reatom advice was wrong, asks why the work deviated from the expected process, requests a course correction, or when a scaffold/bootstrap run should end with a pitfall summary and reusable skill feedback.

Ordered scaffold and bootstrap workflow for new Reatom v1000+ projects. Use for greenfield apps, examples, demos, standalone packages, or when the user wants to create a new Reatom project or scaffold Reatom inside another repo. Focus on setup order, validation pipeline, strict-context bootstrap, and initial quality gates before feature work.

Expert guide for Reatom v1000+ state management. Use for tasks involving @reatom/* imports or explicit Reatom APIs: atom/computed/action from @reatom/core, reatomComponent/useAtom/useAction, reatomRoute, reatomForm, withAsyncData/withAsync/withAbort/withChangeHook, wrap() async context, adapters (@reatom/react, @reatom/vue, @reatom/solid-js, @reatom/preact, @reatom/lit, @reatom/jsx), testing, v3 migration, or errors mentioning ReatomError, missing async stack, or Reatom runtime exceptions.

Find reusable Reatom extension candidates in an existing codebase. Use when auditing repeated @reatom/core / reatomForm / reatomRoute patterns, deciding between core, reatom/reusables, custom `.extend()` helpers, or local `reatom*` factories, or when evaluating whether a pattern is generic enough to propose upstream to reatom/reusables.