reatom

Guide Reatom v1000+ implementation, review, and migration with version-safe rules.

4|Updated May 12, 2026
One-click install
npx skills add https://github.com/Guria/reatom-skill --skill reatom
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: reatom
Source: https://github.com/Guria/reatom-skill/tree/main/skills/reatom
Command: npx skills add https://github.com/Guria/reatom-skill --skill reatom

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

Reatom v1000+ changes often invalidate older v3-style advice, leaving teams unsure which APIs, patterns, and migration steps are actually correct.

Core Features & Use Cases

  • Always-on v1000/v1001 guardrails: keeps answers aligned to the v1000+ API surface and flags v3 memory drift (like explicit ctx usage).
  • Routing, forms, persistence, and adapter correctness: provides decision rules and where to look next for tricky behaviors (loaders, navigation, bindField, storage, React wiring).
  • Debug handoff discipline: guides you to the right focused workflow when the task is active troubleshooting or a correction after wrong guidance.

Quick Start

Tell the AI what you are building in Reatom v1000+ (routing, forms, persistence, React/JSX integration, or migration) and include any error message or the relevant code snippet so it can apply the correct references and guardrails.

Frequently Asked Questions about reatom

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I migrate Reatom v3 code to the v1000+ API surface?

Migrating Reatom v3 to v1000+ requires replacing explicit ctx usage and other stale patterns. This guidance enforces version-safe decision rules and flags v3 memory drift to ensure correct migration across core primitives, async patterns, and framework adapters.

How do I handle ReatomError and missing async stack issues in Reatom v1000+?

Handling ReatomError and missing async stack issues in Reatom v1000+ involves applying correct async patterns and debugging handoffs. This guidance routes you to topic references and focused workflows to resolve common runtime errors during active troubleshooting.

What's the best way to implement routing loaders and navigation in Reatom v1000+?

Implementing routing loaders and navigation in Reatom v1000+ requires specific decision rules for tricky behaviors. This guidance provides correct patterns for routing loaders, navigation, and persistence to ensure framework adapter correctness.

How do I wire the React adapter and bindField forms correctly in Reatom v1000+?

Wiring the React adapter and using bindField for forms in Reatom v1000+ requires specific integration patterns. This guidance provides decision rules for React and JSX wiring, form handling, and storage persistence to maintain adapter correctness.

Why does my Reatom async state pattern from v3 not work in v1000+?

Reatom async state patterns from v3 fail in v1000+ due to API surface changes that invalidate older advice. This guidance provides always-on v1000 guardrails, avoids stale v3 patterns, and enforces version-safe decision rules for async state management.

Can I use Reatom v1000+ with my existing React application without rewriting state logic?

Using Reatom v1000+ with existing React applications is supported through the @reatom/react adapter. This guidance covers React wiring, framework integration rules, and migration steps to adapt your current state logic without full rewrites.