new-projectlisted

# Create / configure a project — run through the RUNBOOK ## The two documents, and which one governs what They do not replace each other — they answer two different questions. **Confusing them means either improvising the procedure, or violating the conventions.** | Document | Answers | When to read it | |---|---|---| | 🎯 **`docs/RUNBOOK.md`** | **WHAT to do, in what ORDER, and WHO does it.** URLs, exact permissions, complete commands, pitfalls. | **IN FULL, before starting.** It's the thread to follow. | | 📖 **`docs/claude-code-project-standard.md`** | **WHY**, and the **conventions to hold while developing**: layout, secrets, branches, README, lifecycle docs. | **Already imposed on every session** by `~/.claude/CLAUDE.md`. **If it hasn't been done in this session: read it NOW** — the runbook keeps referring to it ("standard §3"…), and **an unread reference is a dead reference**. | ### 🔴 Step 0 — resolve the TEMPLATE ROOT before reading anything Every `docs/…` path on this page is relative to the **template root**: the directory holding `init-project.sh`. That root is **two levels above this skill's own directory**, whose absolute path the runtime states when loading this skill. **Build that absolute path first, and prefix every `docs/…` read with it.** ```bash # <skill-dir> = the absolute path the runtime just stated for this skill cd "<skill-dir>/../.." && pwd # → the template root ls "$(cd "<skill-dir>/../.." && pwd)/init-project.sh" # must resolve ``` ⚠️