project-initlisted

# Project Init ## Purpose Bootstrap a new project's `.claude/` configuration and surrounding scaffolding. This is the higher-level companion to `yakos init` — the CLI command sets up the framework wiring; this skill walks the operator through the project-specific decisions: which agents to write, which rules apply, what `path-allowlist.json` should look like for this codebase. ## Scope Operates on a project that has been initialized via `yakos init`. Assumes `<project>/.claude/` already exists with the framework's templates (settings.json, path-allowlist.json) in place. NOT in scope: replacing `yakos init`. If the project hasn't been through `yakos init`, run that first. ## Automated pass 1. Read the project's structure (`README.md`, `package.json`, `go.mod`, `pubspec.yaml`, etc.) to identify languages, frameworks, and structural conventions. 2. Detect domain boundaries from the directory structure (`api/`, `web/`, `mobile/`, `db/`, `mcp/`, etc.). 3. Read `.claude/path-allowlist.json` (the template) and propose a per-domain refinement based on the detected boundaries. 4. Read existing rules in `<project>/.claude/rules/` and surface gaps: if `api/` exists but no rule covers it, surface "missing `go-backend.md`" or equivalent. 5. List the framework agents that apply (from `~/.claude/agents/`). Note which ones the project might want to override or extend. ## Manual pass The operator reviews the proposed: - Allowlist refinement — does each agent's a