A window with plain text opens. That's the terminal. It's supposed to look boring.

The terminal prints progress text for a minute. When it stops, it should look like this:

Any version number = success, keep going. "command not found" = you skipped the restart — close the terminal fully and try again.

A blue window opens, ending in PS C:\Users\yourname>. The "PS" at the start matters — it means you're in the right place.

"irm is not recognized"? Your window says C:\ without the PS — that's Command Prompt. Close it and redo the previous step.

Why: this quietly gives Claude a better set of tools for running commands. You'll never touch it directly. It takes two minutes.

Any version number = success, keep going. An error = close the window fully, open a fresh one, try again.

On your Mac: find the project folder in Finder, right-click it, and choose New Terminal at Folder (near the bottom of the menu).

On your PC: open the project folder in File Explorer, click once in the address bar at the top, type powershell over what's there, and press Enter.

A terminal opens already "standing in" that folder. That's the whole trick.

Using the Claude Code desktop app instead? Even easier: open the app and choose the project folder when it asks where to work. Then skip ahead — everything else on this walkthrough looks the same in the app.

Your web browser pops open a sign-in page. Sign in with your Lasting Light account — the one your lead gave you, not a personal one.

First time only: Claude also asks you to approve this project's connections (the MCP servers). Say yes — they're ours, committed in the repo.

If Claude answers with a summary of our game — congratulations, Claude Code is fully working on your machine. Two short connections left.

1. Open our project in the Unreal editor (if it asks to enable or rebuild our MCP plugin, say yes).

2. In your Claude session, type /mcp and press Enter. You want to see this:

3. Prove it end to end:

Shows as failed? The editor probably isn't open, or the plugin isn't enabled (in Unreal: Edit → Plugins → find our MCP plugin → check the box → restart). The Setup page has the full checklist.

Using them requires almost nothing from you. Describe the task and Claude picks the right skill automatically. To call one deliberately, type / and its name, or just say it in plain English:

The six everyone uses, whatever your desk:

Your department page (last step) adds the specialist skills for your seat — and the full catalog lives in the Skill Library, filterable by department. Notice something a skill should know? Add it — that's the whole flywheel.

Swapping takes five seconds: in the desktop app, click the model name next to the message box and pick from the menu (or type /model — same thing):

The rhythm: plan in Fable 5 (high) → swap → build in Sonnet 5 (extra). You'll do it without thinking within a week.

In the desktop app, click the mode control next to the message box and pick (in the terminal, Shift + Tab cycles the same modes):

Plan mode is the third stop on that same cycle — Claude researches and writes a full plan, and edits nothing until you approve it. Pair it with Fable 5 for anything big; approve the plan, then flip to auto mode + Sonnet 5 and let it build.

Auto mode isn't a blank check — genuinely risky or destructive actions still ask, and everything Claude does still goes through normal review before it ships.

Where: Claude app → Settings → Connectors → enable what you use. That's the whole setup — no commands.

In Claude Code, type /mcp anytime to see everything connected to your current session — connectors and hand-added MCPs side by side.

Two rules: work accounts only (never personal), and ask in the tools channel before enabling anything unusual. Connectors are the everyday-work superpower — meetings, docs, and email are where most people save their first hours.