[ HOW TO START · SETUP, END TO END ]

From a blank laptop
to ready to work.

Two tracks — pick yours and follow it in order. Every step ends with a check: when it passes, move on; when it doesn't, the step says exactly who gets you unblocked. Mac and Windows are both covered along the way.

[ TRACK ONE · NON-DEVELOPER ]

AI Translators · PM · Sales.

No terminal, no code — three installs and two checks, and the setup is done. Claude does the one fiddly part for you.

    [ TRACK TWO · DEVELOPER ]

    Terminal in, baseline on.

    Two commands do the heavy lifting — but each exists only after the step before it, so keep the order.

      [ IF A CHECK FAILS ]

      Two people unblock everything.

      Nothing in this setup is fixed by retrying harder. Each check that can fail points at one of two doors — knock early.

      The Claude admin

      Owns everything inside Claude: team skills missing from your app, a skill that won't run on your machine, accounts and sign-in. If a skill isn't in your list, publishing it is their one-click fix — never something you install yourself.

      Any developer

      Owns everything on the developer track: access to the team's GitHub organization, the agentic-engineering repo, and any step of the technical setup that won't cooperate. The link to the repo is one message away.

      All checks passed? See how the pieces fit — back to the landscape
      ← Landscape