Onboard

Design-Philosophy.md

• "Do you have a preferred visual style? (minimal, Material, custom design system, etc.)"
• "Dark mode, light mode, or both?"
• "Any icon/typography preferences?"

Decision-Making.md

• "How do you approach technical decisions? (pragmatic, thorough, move fast, etc.)"
• "Build vs buy — do you prefer libraries or custom code?"
• "How important is backwards compatibility vs. clean breaks?"

Workflow.md

• "Where do your projects live on disk?"
• "How autonomous should I be? (ask often / only for blockers / full autonomy)"
• "Any shell or tooling preferences? (zsh, bash, package managers, etc.)"

Resumable

Onboarding is resumable. The agent checks which files still have placeholders:

• If the user ran /onboard before but only finished 2 of 5 files, it picks up where they left off
• Already-customized files (no "This is an example file" marker) are skipped automatically
• The user can run /onboard tech-stack to onboard a single file

Rules

• Ask one file at a time — don't overwhelm with all questions at once
• Accept short answers — you fill in the structure
• If the user says "skip", move to the next file
• If the user gives partial info, fill in what you can and note what's still missing
• After each file, confirm what was written and ask "Continue to the next, or stop here?"