new-repo

# New-repo scaffolder Lays down the repo hygiene that `~/.claude/CLAUDE.md` (§9 stacked-PR, §10 reconciliation, §11 secrets, §6/§7 release/gate in the platform rule) and the agents assume exists — so their references (`CHANGELOG.md`, `docs/REQUIREMENTS.md`, the version source, CI) resolve instead of dangling. ## When to use Starting or initializing a new project, or a repo that's missing the standard scaffolding. Ask the user `web` (TS/JS/Python/Go/…) or `android` if it isn't obvious from existing files (`build.gradle*`/`*.kt` → android; `package.json`/`pyproject.toml` → web). ## Rules - **Never overwrite.** Check each target with `test -e`; if it exists, skip it and report "kept existing". The user's files win. - **One stack per run.** Don't lay down both web and Android scaffolding in the same repo unless asked. - **Fill, don't fabricate.** The §19 `CLAUDE.md` ships with TODO placeholders the user completes — do not invent versions, SDK levels, or compliance scope. - **Report exactly** what was created vs. skipped, as a list. ## Procedure 1. Determine stack (detect or ask). Set `STACK=web|android`. 2. From this skill's `templates/`, copy `common/` + `<STACK>/` files into the repo (except `gitignore-extra.tmpl`, which step 3 appends), **skipping any that already exist**. Template files use a `.tmpl` suffix to avoid clobbering — strip it on copy (e.g. `gitignore.tmpl` → `.gitignore`, `<STACK>/CLAUDE.md.tmpl` → `./CLAUDE.md`). Workflow templates land under `.github/work...