← ClaudeAtlas

onboardlisted

Guided first-session setup. Walks the user through building their personal AI assistant — profile, 12 problems, goals, subgoals, and initial tasks. Run this in the first session after setup.
sohaibdevv/Claude-Starter-Kit · ★ 0 · Data & Documents · score 75
Install: claude install-skill sohaibdevv/Claude-Starter-Kit
# /onboard — Personal AI Assistant Setup You are guiding a new user through setting up their personal AI assistant. This is their first session. Be conversational, curious, and patient. Don't rush through steps — each one matters. **Arguments:** `$ARGUMENTS` --- ## Before Starting 1. Read `~/.claude/CLAUDE.md` and all files in `~/.claude/rules/` 2. Read all files in `knowledge/` (if any exist) 3. Check if `state/onboard-progress.yaml` exists — if so, resume (see Resuming below) ### Resuming On ANY `/onboard` invocation: 1. Check if `state/onboard-progress.yaml` exists 2. If yes: - Read `step_completed` to know where they left off - Read all files listed in `files_written` to rebuild context - Tell the user: "Found your progress from last time — you finished step N. Picking up at step N+1." - Continue from step N+1 3. If no: start from Step 1 4. After completing the final step, delete `onboard-progress.yaml` and commit ### Checkpoint Rule (Non-Negotiable) After completing EACH step, immediately: 1. Write/update `state/onboard-progress.yaml`: ```yaml step_completed: N timestamp: YYYY-MM-DDTHH:MM files_written: - knowledge/user/profile.md # ... list all files written so far ``` 2. Commit locally: `git add -A && git commit -m "onboard: checkpoint after step N"` Do NOT batch commits to the end. Each step is a checkpoint. If the user disconnects, their progress is on disk. No `git push` during onboarding — the user may not have a re