reatom-scaffold

Scaffold Reatom v1000+ projects with validation-gated routing and feature work.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

It prevents broken or out-of-order Reatom project bootstraps by enforcing an explicit scaffold-to-validation workflow before any routing, runtime wiring, or feature implementation.

Core Features & Use Cases

  • Ordered greenfield scaffolding with phase gates: parks the user’s original feature request into GOAL.md and blocks feature work until the scaffold baseline proves validation is green.
  • Validation pipeline wiring and proof: installs and configures linting, formatting, typecheck, code intelligence, and a browser smoke test, then requires npm run validate to pass.
  • Routing-skeleton handoff after first green validate: transitions to a routing-only pass with strict setup/dev-time logger wiring and outlet() composition, validated before continuing features.
  • Recovery from out-of-order changes: detects and corrects gate violations (e.g., feature code or Reatom runtime changes added before npm run validate), repairing the ledger and resuming at the earliest incomplete gate.

Quick Start

Tell your agent: “Scaffold a new Reatom v1000+ app in this folder and follow the scaffold flow with GOAL.md, run npm run validate until it’s green, then proceed only to the routing-only skeleton phase.”

Frequently Asked Questions about reatom-scaffold

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

FAQPage Schema
How do I scaffold a new Reatom project without breaking the bootstrap order?

Scaffold a Reatom project by gating routing and feature work behind a verified validation pipeline. This ensures bootstrapping includes scaffold artifacts, GOAL.md phase tracking, and a browser-level smoke proof before proceeding.

What is the validation pipeline required for bootstrapping Reatom v1000+ apps?

The validation pipeline requires wiring lint, format, typecheck, code intelligence, and a browser smoke test. You must run npm run validate until it passes green before touching the Reatom runtime or adding feature code.

How do I set up routing in a Reatom app after initial scaffolding?

After your first green validate, proceed to a routing-skeleton pass. This involves strict setup and dev-time logger wiring alongside outlet() composition, which must be validated before continuing with feature implementation.

Can I add Reatom runtime changes before npm run validate passes?

No, Reatom runtime changes and feature-reference reads are blocked until validation is green. This gate prevents broken or out-of-order project bootstraps by enforcing an explicit scaffold-to-validation workflow.

How do I recover from out-of-order changes during Reatom project bootstrapping?

Recover from out-of-order changes by detecting and correcting gate violations, such as feature code added before validation. The workflow repairs the ledger and resumes at the earliest incomplete gate to restore bootstrap order.

Does the Reatom scaffolding workflow support monorepo additions and demos?

Yes, the scaffolding workflow applies to greenfield apps, demos, and monorepo additions. It requires creating GOAL.md immediately after scaffold success to park original feature requests and track phases.