Reatom Review

Use this skill to validate an agent's work against Reatom v1001 practices. Be skeptical: the goal is to find incorrect behavior, misleading docs, stale API usage, weak tests, and patterns that only look plausible.

Reference

Before validating API usage, extension options, or documentation claims, also load the reatom skill and read the relevant sections of REFERENCE.md. It is the canonical v1001 API reference. For implementation (not review), use the reatom skill directly.

Review Stance

• Lead with findings. Do not praise before checking correctness.
• Criticize the reviewed work, not the author.
• Treat REFERENCE.md as the local source of truth when it conflicts with generic frontend habits.
• Quote concrete files/symbols and explain the failure mode.
• Prefer one precise fix over vague advice.
• If a change is acceptable only with a special reason, ask for that reason or mark it as a risk.
• Do not approve Reatom code just because TypeScript compiles; review context propagation, cancellation, laziness, naming, and subscriptions.

Mandatory Checks