mobile-scaffold

The default failure of a new RN app is not a bad decision. It's a deferred one. Nobody decides to have two lockfiles, a half-adopted component library, sheets nested in ScrollViews, and no test runner; those are the defaults you get by starting to build features on day 1. Every one of them is a five-minute choice at scaffold time and a multi-day excavation at day 45, because by then thirty screens sit on top of it. This skill bans deferral: it forces the twelve decisions before the first feature ships.

This is the opening of the Mobile Kit lifecycle: mobile-scaffold (foundations) → mobile-architecture (nav/state/structure spec) → mobile-design (tokens and screens) → mobile-motion (interaction) → mobile-audit (the hold) → mobile-ship (the release gate). This skill owns project foundations only. It does not design the nav graph (mobile-architecture), does not pick token values (mobile-design), and does not run release verification (mobile-ship). It verifies those siblings have a place to stand.

Modes

Mode	When	What happens
SCAFFOLD	Creating a new project	Walk S1–S12 as a build checklist; nothing else gets built until every gate passes.
RETROFIT	Existing project, foundations unverified	Walk S1–S12 as an audit; emit the report with fixes ordered by blast radius.

The S-gates (binary, evidence required)

Read references/day-one-decisions.md for the reasoning and the exact commands behind each gate.