claude/skills/init-project/SKILL.md

name: init-project description: Full project init: interview → design → scaffold → implement (TDD). Two validation gates. argument-hint: disable-model-invocation: true allowed-tools: Read, Write, Edit, Bash, Grep, Glob

ORCHESTRATOR: INIT PROJECT

REQUEST

$ARGUMENTS

---

STEP 0 — PLUGIN CHECK + AUTO-ACTIVATE

Load $HOME/.claude/agents/plugin-advisor.md. Feed request.

• ACTION REQUIRED → show RECOMMENDATIONS block, offer: A) fix plugins B) type "force". STOP.
• PROPOSED CHANGES exist → show list, ask "Apply? (yes / no / customize)". Apply on confirm.
• OK → ✅ Plugin check passed — [active plugins] — complexity: <score>%, continue.

STEP 1 — INTERVIEW

Before loading the interviewer, check for an existing CLAUDE.md:

ls CLAUDE.md .claude/CLAUDE.md 2>/dev/null | head -1

• Found (either CLAUDE.md or .claude/CLAUDE.md) → read it silently. Pre-fill all interview answers already documented (stack, purpose, features, conventions). Load $HOME/.claude/agents/interviewer.md and ask ONLY what is genuinely missing. Print: "📄 Existing CLAUDE.md found — using as context."
• Not found → standard mode: load $HOME/.claude/agents/interviewer.md, ask all unanswered questions.

In both cases: MANDATORY STOP until user answers remaining questions. Produce PROJECT BRIEF.

STEP 2 — ANALYZE

Load $HOME/.claude/agents/analyzer.md. Analyze BRIEF: existing code, stack constraints, infra risks, open decisions. Produce ANALYSIS REPORT.

STEP 3 — DESIGN

Invoke superpowers:brainstorming with BRIEF + ANALYSIS REPORT. Produce DESIGN: stack+versions, full folder tree, module responsibilities, data flow, interfaces (signatures only), config+tooling, test strategy, resolved decisions, prereqs list.

STEP 4 — VALIDATION GATE #1 ★ MANDATORY STOP

Present:

INIT PROJECT — ARCHITECTURE VALIDATION
PROJECT : <3-5 line recap>
STACK   : <versions>
PREREQS : <install list>
TREE    : <folder tree>
V1 FEATURES: <numbered list>
CONVENTIONS: <naming, doc, test>
EXCEPTIONS : <list or none>
Approve? (yes / request changes)

Changes → back to STEP 3. Approved → continue.

STEP 5 — SCAFFOLD

Load $HOME/.claude/agents/scaffolder.md. Pass: BRIEF + DESIGN + ~/.claude/templates/project-CLAUDE.md + ~/.claude/CLAUDE.md. Creates: CLAUDE.md, settings, structure, config, empty entry points, .gitignore, .env.example, .claude/tasks/TODO.md, .claude/memory/{decisions,learnings,blockers,journal,evals}.md, .claude/audits/. NO README, NO features. Verify: git init + build passes.

STEP 5b — CREATE README

Load $HOME/.claude/agents/readme-updater.md. README.md missing → CREATE mode auto. No stop.

STEP 5c — CTX7 PRE-FETCH (if fast-libs detected)

If fast-libs signal was detected in STEP 0 (Next.js, React 18+, Prisma, Supabase, Drizzle, etc.):

1. Create .ctx7-cache/ directory in project root.
2. For each detected fast-lib, fetch core docs:

   mkdir -p .ctx7-cache
   # Example for detected libs — adapt to actual deps:
   ctx7 docs /vercel/next.js "app router middleware routing" > .ctx7-cache/nextjs-core.md 2>/dev/null || true
   ctx7 docs /prisma/prisma "schema client queries" > .ctx7-cache/prisma-core.md 2>/dev/null || true
   

3. Add .ctx7-cache/ to .gitignore (local dev cache, not committed).
4. Print: 📚 ctx7 docs pre-fetched for: <libs>. Cache at .ctx7-cache/ If ctx7 not installed or no fast-libs → skip silently.

STEP 5d — GRAPHIFY SCAFFOLD (light pass)

If graphify CLI is installed AND complexity >= 30%:

1. Run light graphify on the scaffold:

   graphify . --output graphify-out --mode quick 2>/dev/null || true
   

2. Add graphify-out/ to .gitignore if not already present.
3. Print: 🔗 Scaffold graph generated at graphify-out/ If graphify not installed or complexity < 30% → skip silently.

STEP 5e — ANIMATION LIB (auto-install)

Install motion (ex-framer-motion, rebranded Nov 2024) when the stack supports it. The scaffold has just been validated by the user, so install proceeds silently.

source "$HOME/.claude/lib/animation-lib-check.sh"
if result=$(detect_anim_eligibility); then
  pkg=$(echo "$result" | cut -d'|' -f2)
  if ! is_anim_lib_installed >/dev/null; then
    cmd=$(recommend_anim_install_cmd "$pkg")
    echo "🎬 Installing animation lib: $cmd"
    eval "$cmd"
  else
    installed=$(is_anim_lib_installed)
    echo "🎬 Animation lib already present: $installed — skipping install"
  fi
else
  echo "🎬 Animation lib: stack not eligible — skipping ($(echo "$result" | cut -d'|' -f3))"
fi

Rules:

• motion for React-family / Svelte / vanilla JS stacks.
• motion-v for Vue 3 / Nuxt.
• React Native, Flutter, backend, embedded, static HTML → skipped.
• If another animation lib (gsap, lottie-react, react-spring, …) is already present → skipped.

STEP 6 — PLAN

Invoke superpowers:writing-plans with BRIEF + skeleton. Granular tasks (2-5 min each), exact file paths, TDD: tests before code.

STEP 7 — VALIDATION GATE #2 ★ MANDATORY STOP

INIT PROJECT — IMPLEMENTATION PLAN
SKELETON: ✅ build passes
FEATURES: <N> → <M> tasks
<numbered task list with paths>
Approve and start? (yes / request changes)

Changes → back to STEP 6. Approved → continue.

STEP 8 — IMPLEMENT

Invoke superpowers:subagent-driven-development. Isolated subagents, TDD, 2-stage review per task.

STEP 8b — GRAPHIFY FULL (after implementation)

If graphify CLI is installed AND complexity >= 30%:

1. Run full graphify on the implemented project:

   graphify . --output graphify-out 2>/dev/null || true
   

2. Print: 🔗 Full project graph updated at graphify-out/ If graphify not installed or complexity < 30% → skip silently.

STEP 9 — ANALYZE

Load $HOME/.claude/agents/analyzer.md. Check: no regressions, no deviations, no stale scaffold, conventions respected.

STEP 10 — CODE REVIEW

Invoke superpowers:requesting-code-review. Fix all CRITICAL before proceeding.

STEP 11 — FINISH

Invoke superpowers:finishing-a-development-branch. Tests pass, build clean, no placeholders, initial commit ready.

STEP 12 — SYNC README

Load $HOME/.claude/agents/readme-updater.md with arg sync. Detect drift, update cmds/vars/structure, add recent changes entry.

STEP 13 — GSD v2 INIT (optional)

If multi-session signal was detected in STEP 0 OR the project has >3 planned milestones: Ask: "Initialize GSD v2 for multi-session management? (yes / skip)"

• yes →
  1. First check: command -v gsd — if not found: Print: "⚠️ GSD v2 not installed. Run npm install -g gsd-pi then re-run /onboard add gsd or /ship-feature to initialize later." Do NOT attempt gsd init. Skip to RULES.
  2. If gsd is in PATH: run gsd init in the project directory to create .gsd/ and ROADMAP.md. Populate ROADMAP.md with milestones from BRIEF (v1 features + any beyond-v1 items). Print: "✅ GSD v2 initialized — run gsd in terminal then /gsd auto to work autonomously."
• skip → print: "GSD v2 skipped — use /ship-feature for individual features."

---

RULES

• No skipping steps. No merged agent responsibilities.
• No implement without user approval at STEP 4 and STEP 7.
• Scaffolder = skeleton only, zero logic.
• Features → subagent pipeline only.
• Broken build = unacceptable output.
• Fix all CRITICAL review issues before proceeding.
• Stop if requirements unclear at any step.

---

FINAL OUTPUT

PROJECT INITIALIZED: <n>
LOCATION: <path> | STACK: <stack> | BUILD: ✅/❌ | TESTS: ✅<N>/❌
V1 FEATURES: ✅<f> / ⚠️<f> partial: <reason>
REMAINING ISSUES: <list or none>
QUICK START: <exact cmds>
CLAUDE.md ✅ | README ✅ | SETTINGS ✅