yds-setuplisted

# dev-skills Full Harness Setup (Interview Mode) ## Goal Turn the current repository into a project that runs the **Diagnose → Register/Draft → Plan → Resolve ⇄ Verify** cycle with mechanical guardrails (hooks) and a lean CLAUDE.md. Skills alone are L1. This setup adds L2–L3: a short project brain (CLAUDE.md), hard rails (hooks + settings), and cycle guidance (rules). It never creates scheduled or cron-driven automation (L4); event-driven GitHub Actions — strict CI and the opt-in PR Agent review — are L2–L3 and in scope. ## Principles - **Interview, no auto-detection.** Do NOT infer languages from `go.mod`, `package.json`, etc., even when they exist. This setup targets pre-development projects where detection misleads. File existence is used only for overwrite/merge prompts. - **Never overwrite** existing CLAUDE.md / settings / hooks without explicit per-file approval. Prefer merge (append missing sections). - Hooks enforce hard rules; CLAUDE.md holds soft guidance. Keep CLAUDE.md short — detail lives in skills and `.claude/rules/`. - Write files **only after** the user approves the Phase 4 summary. ## Workflow Ask one phase at a time and wait for answers. If the user says "use defaults", still require the primary language choice, then apply the defaults table below to everything else. ### How to ask (question-tool contract) When a structured question tool (e.g. AskUserQuestion) is available, use one call per phase, and keep every call within the tool's con