Reatom scaffold

Use this skill when the task is primarily about creating a new Reatom codebase or establishing a clean bootstrap baseline.

The goal is not just to list packages. The important part is the order: scaffold first, write GOAL.md, finish the validation pipeline on the untouched starter project, and only then let later stages resume from the checklist in GOAL.md.

The common failure mode is that an agent installs a validation stack, but never actually wires it into a working pipeline. Treat that as an incomplete bootstrap, not as a minor omission.

Bootstrap control protocol

This section is intentionally mechanical. It does not depend on the model judging its own ability. A rich feature request can pull any run into routes, forms, UI, fake APIs, or Reatom models too early, so the feature request is parked work until the gates below unlock it.

For full greenfield apps/examples/packages, keep a visible phase ledger:

1. Scaffold phase — create the starter project and GOAL.md only. After the scaffold command succeeds, the next normal tool call in that root is write for GOAL.md; do not run npm install, npm view, read package.json, or load feature references first unless you genuinely need to locate the scaffold root.
2. Validation phase — wire and run the validation pipeline on the mostly untouched starter. No Reatom app code yet.
3. Routing-skeleton phase — after the first green npm run validate, add strict setup/dev-time logger wiring plus placeholder routes/layouts and outlet() composition.
4. Feature phase — only after the routing skeleton validates, resume the parked original request.