Onboard a developer to RaiSE interactively. Use for first-time setup.
Get a developer fully set up in a RaiSE project through a guided flow that detects their situation and only asks what's needed.
When to use: First time a developer works in a RaiSE project. Subsequent runs verify setup.
When to skip: Developer is already set up (profile exists, graph exists).
Inputs: A project with .raise/ directory (from rai init).
ls ~/.rai/developer.yaml 2>/dev/null && echo "PROFILE_EXISTS" || echo "NO_PROFILE"
ls .raise/ 2>/dev/null && echo "RAISE_EXISTS" || echo "NO_RAISE"
| Profile? | .raise/? | Action |
|---|---|---|
| No | Yes | Full setup (Steps 2-5) |
| Yes | Yes | Verify only (Step 4) |
| Any | No | Stop: "Run rai init first, then /rai-welcome again." |
Ask developer's name (only mandatory question). Derive pattern prefix (first letter, uppercased), confirm.
rai session start --name "{name}" --project .
Edit ~/.rai/developer.yaml to add confirmed pattern_prefix.
Frame as skippable: "Want to customize? Or skip — defaults work well."
If customize, ask up to 3 questions:
communication.languagecommunication.stylecommunication.redirect_when_dispersingDefaults: shu, balanced, en, detailed_explanations: true, redirect_when_dispersing: false.
Build graph if missing (rai graph build). Run context bundle:
rai session start --project . --context
Check: developer name appears, session count shown, no errors.
Welcome to RaiSE, {name}!
Setup: Profile ({prefix}), Graph ({N} concepts)
Next: /rai-session-start
| Item | Destination |
|---|---|
| Developer profile | ~/.rai/developer.yaml |
| Knowledge graph | .raise/rai/memory/index.json |
| Session context | Derived from git (ADR-038) |
| Next | /rai-session-start |
src/raise_cli/onboarding/profile.py/rai-session-start