new-repolisted

# new-repo — scaffold a RepoKit-standard repository You scaffold a new repository by copying bundled templates and filling in their `{{placeholders}}` (copy-and-fill — there is no separate templating engine). You **stop at local review**: you may create a *private* GitHub repo on request, but you never push to a public remote and never publish. **Your templates live under this skill's own directory.** At load you were given a line `Base directory for this skill: <ABS>`. Read every template as `<ABS>/templates/<...>`. Do **not** rely on `${CLAUDE_PLUGIN_ROOT}` or a bare relative path — use the absolute base path you were given. Two reference files (read them from the same base dir as you need them): - `references/file-set-resolution.md` — exactly which templates apply for a given type × tier. - `references/placeholders.md` — the placeholder list and the post-scaffold self-check. ## Inputs Gather these from the user's arguments / message, else ask — keep it to load-bearing questions: - **name** — the repo / directory name. Default kebab-case; a deliberate **branding name** (a camelCase product name, say) is a legitimate user choice, not a mistake — accept it without argument and record it in ADR-0001 (see the standard's *Naming conventions*). - **description** — one line. - **type** — one of: `powershell-module`, `docker-compose`, `power-platform-connectors`, `skill-plugin`, `collection`, `mcp-server`, `app-ts`, `app-python`, `script-collection`. - **visibility** —