skeleton-bootstrapping

Skeleton Bootstrapping

Entry point for every session. Loads context and routes intent.

Announce: "Using skeleton:bootstrapping to load project context."

Checklist

1. Read ./CLAUDE.md (orchestrator root)
2. Detect target repo from user intent:
   • Backend: PHP, Laravel, API, endpoint, module, Action, migration
   • Frontend: React, Next.js, component, page, hook, UI, form
   • Both: full-stack, full feature, API + UI
   • Bug: error, fix, broken, not working
   • Skill: create skill, edit skill, workflow
3. Read {repo}/CLAUDE.md + {repo}/ARCHITECTURE.md for target repo(s) 3b. Frontend task gate:
   • If task involves frontend/UI work:
     • Check if frontend/DESIGN_SYSTEM.md exists
     • If YES → load into context alongside ARCHITECTURE.md
     • If NO → inform user: "DESIGN_SYSTEM.md is needed for frontend work. Run design-system-extractor if /design folder exists."
   • ALWAYS re-read files from disk. NEVER rely on previously loaded content.
4. Check for active plans in docs/plans/:
   • List .md files in docs/plans/
   • For each, count unchecked steps: grep -c '- \[ \]' docs/plans/*.md
   • If plan has unchecked steps → active
   • One active plan → ask: "Found active plan: {filename} with N remaining tasks. Resume?"
     • If YES → route to implementing skill with the plan
     • If NO → proceed with new task routing
   • Multiple active plans → show list, ask which to resume
   • No active plans → proceed to routing as normal
5. Route to skill:

Intent	Plan exists?	Destination
New feature	No	skeleton:designing
New feature	Yes, incomplete	skeleton:laravel-implementing / skeleton:nextjs-implementing
Bug / error	N/A	skeleton:debugging
Create/edit skill	N/A	skeleton:writing-skills

5b. Preview routing: - If user intent involves frontend UI AND uses words like: "preview", "show me first", "mockup", "let me see", "prototype", "how would it look" → route to skeleton:previewing - If user says "implement" or "build" for a UI task and no prototype exists in frontend/.previews/ → suggest: "Want a quick preview before I implement, or should I go straight to code?" 6. Inform user: what context was loaded and where we're routing

Anti-Rationalizations

Temptation	Reality
"I already know this project"	Fresh context window. ARCHITECTURE.md may have changed. Always read it.
"It's a trivial change"	Trivial changes in wrong locations are bugs. Architecture defines file paths.
"The user told me exactly what to do"	Knowing WHAT isn't knowing WHERE. Load context first.

Transitions

Condition	Destination
New feature, no plan	skeleton:designing
Existing incomplete plan	Resume implementation
Bug / error	skeleton:debugging
Create / edit skill	skeleton:writing-skills