setup-initlisted

# Init project Orchestrates the onboarding chain. Detects project type, resolves per-domain arguments, previews the chain, then runs `aitk init` with flags. The CLI holds the install logic. This skill only resolves and previews. ## Scope - This skill and `aitk init` run once on a fresh scaffold, never on an existing project. They do not guard against clobbering existing configs. When tempted to add guards, mode switches, or an existing-project branch, stop. Extend the per-domain `aitk <domain> install` or `aitk sync` paths instead. ## Read catalogs Run in parallel. Never hardcode stack, rule, snippet, or standards names. Run from the target project's current directory. Do not cd into the toolkit source tree. The `aitk` CLI is global. ```bash aitk gov list --json 2>/dev/null aitk snippets list --json 2>/dev/null aitk standards list --json 2>/dev/null aitk tooling list --json 2>/dev/null ``` ## Detect Read these from the project root in parallel, skipping any that do not exist: - `package.json`: `dependencies` and `devDependencies` - Root configs: `astro.config.*`, `next.config.*`, `vite.config.*`, `tailwind.config.*`, `tsconfig.json`, `pyproject.toml`, `go.mod`, `Cargo.toml` - `.claude/REQUIREMENTS.md` and `.claude/ARCHITECTURE.md` if present - Directory structure via `ls -1` of the project root and `src/` if present ## Resolve arguments - **Stack:** pick the closest governance stack by matching detected runtime or framework against stack names in the catalog. If no