MaxtDesign

Onboarding

What /onboard does

/onboard is the setup flow. It runs once after install and asks about your business: who you are, what you build, your brand voice, your stack, your goals, and how you plan to use the pack. It writes all of that to a single profile.md file at your pack root.

Every other skill reads that profile on demand, only when it needs context, never at the start of a session. So instead of re-explaining your stack on every task, you tell the pack once and it remembers.

Running it

  • Claude Code / Cowork-Desktop: type /onboard in a fresh session. It is a guided, 10 to 20 minute Q&A.
  • Cursor, Codex, Claude.ai, chat AI: there are no slash commands, so walk the same Q&A manually using the onboard adapter, then save the result as profile.md (or paste the relevant parts when a skill needs them).

    • What it captures

  • 1.Identity: who is running the pack (solo founder, agency, team).
  • 2.Business: what you sell and to whom.
  • 3.Brand: your voice, optionally extracted from writing samples you provide.
  • 4.Stack: languages, frameworks, deploy targets, payments, email.
  • 5.Goals and constraints: what you are optimizing for, and your limits (budget, hours, team size).

    • Some of these change the actual behavior of skills. For example, your team size shifts the threshold at which a code review convenes a panel, and your budget tier changes the numbers a pricing skill recommends.

    Good to know

  • Only /onboard writes the profile. Other skills read it; they never overwrite it. Update it by running /onboard again (or a single stage of it).
  • It stays on your machine. The profile and any history the operate skills keep are local to your install. Nothing phones home.
  • You can skip it. The skills still work, they just ask you more. Run it when you want the "the pack knows you" behavior.
    • InstallationThe 31 skills