michi-bootstraplisted

# Michi Bootstrap Onboard a project to the michi documentation structure. This happens before the first `michi-planning` session — for a brand-new project or an existing one being prepared for Michi work. **Principles served:** Shared context as foundation (builds the context layer all other skills read). Progressive detail (sets up the S/M/L/XL document hierarchy). Sustain the system (docs infrastructure makes future iterations productive). See `references/principles.md`. ## When to Use - Setting up a new project for michi work - Onboarding an existing project that has never used Michi - Re-running on a project with partial Michi structure to close remaining gaps ## Inputs Before starting: - Access to the target project codebase - Michi toolkit installed (skills in `.claude/skills/` or accessible via the GitHub repo) - User present and interactive — this is collaborative, not autonomous ## Phase 1: Survey Produce a **project profile** — a structured snapshot that drives the recommendation phase. ### Codebase Heuristics Get a quick size/shape read: 1. Check if `tokei` is installed (`which tokei`). If available, run `tokei` for language and size breakdown. 2. If `tokei` is not available, fall back to heuristics: - Count files by extension: `find . -type f -name '*.js' -o -name '*.ts' -o -name '*.py' | wc -l` (adapt to what's present) - Rough line count: `find . -type f -name '*.js' | xargs wc -l | tail -1` (adapt to primary language) - Directory depth