Reatom extension candidates

Use this skill for existing codebases when the job is to find repeated Reatom patterns and decide whether they should stay inline, become a local helper, become a custom extension, become a local reatom* factory, or be proposed to reatom/reusables.

This skill is about discovery and triage, not blind abstraction. The goal is to reduce duplication without over-generalizing.

If the task is active bug fixing, runtime/test debugging, or bootstrap order, use the sibling reatom-debug or reatom-scaffold workflow instead. If the user is correcting earlier bad guidance, use reatom-feedback-loop after the immediate code issue is understood.

First read

Before analyzing the target codebase, read these sibling references:

1. ../reatom/SKILL.md
2. ../reatom/references/meta/reusables.md
3. ../reatom/references/core/writing-extensions.md
4. references/upstream-checklist.md

Use the general Reatom guidance above as the source of truth for API behavior. This skill layers a search-and-triage workflow on top of it.