trip-scaffoldlisted

# trip-scaffold Compile a family-trip PWA. The output is a static artifact the user owns, not a chat answer: cream-and-terracotta visual identity, a day-by-day schedule, a contingency chip on every anchor (每個備案都有資料), a collapsible prep-refs card (今晚先看), full keyboard a11y, an offline service worker, and static output ready to publish to GitHub Pages. This skill has three subcommands. Read the matching reference file in `references/` before executing — keep this entry short; the detail lives there. ## When to use which subcommand - **`init`** — create a new trip PWA from scratch. Sets up the static shell (index.html, day.html, css/, js/), the data corpus (trip.json, days.json, refs.json), PWA icons (192/512 PNG + maskable, rendered from a city-initial SVG via `@resvg/resvg-js`), and the service worker. Read `references/init.md`. - **`draft-days`** — seed `data/days.json` with execution-level schedule blocks, one researched contingency alternative per real anchor, retaining inline research detail in the target language. Destination-local names use `local_name` (`jp_reading` is a legacy Japan-only fallback). Read `references/draft-days.md`. - **`launch-check`** — pre-publish audit: complete browser behavior (Playwright), static duplicate-ref check, and the `--quality family` content-depth floor. Missing bundle Playwright fails closed; `--no-browser-tests` is an explicit partial check. Exit non-zero with an actionable message on failure. Read `referenc