Every desk at Lasting Light now works alongside Claude — an AI teammate that reads our code, drives our Unreal editor, follows our playbooks, and gets smarter every time one of us teaches it something. This site is your field manual: what Claude is, what it can do for your department, and how to make it part of your day one.
NEW HERE? "GET STARTED" WALKS YOU THROUGH INSTALL + SETUP, CLICK BY CLICK — 15 MIN.
Most studios bolt AI onto the edges — a browser tab you paste things into. We built it into the middle. Claude at Lasting Light can open our Unreal project, compile it, run it, look at the scene, and fix what it finds. It also drafts your docs, digests your meetings, and crunches your spreadsheets. One teammate, every desk.
Engineers, designers, artists, QA, production — Claude adapts to the seat it's sitting in. Same teammate, different playbook.
Our shared skill library encodes how Lasting Light builds — exact commands, conventions, and checklists. Browse the full library →
Claude proves its work — builds compile, tests pass, the scene looks right in the editor — before anything is called finished.
When someone says "ask Claude to do it," this is what's actually happening under the hood. You don't need to memorize any of it — but knowing the layers tells you why Claude here is different from ChatGPT in a browser tab.
The intelligence itself. You talk to it in plain English — in Claude Code (terminal or desktop app) when you're working in the project, or the Claude app for everything else. It reads files, writes code, runs commands, browses docs, and works in loops: try, check, fix, repeat. Treat it like a sharp new hire: give it context, tell it what "done" looks like, and check its work at first.
Our team's how-to guides, written for Claude instead of humans. A skill packages the exact way Lasting Light does something — the real build commands, our C++ conventions, our asset naming rules, our review checklists. When you invoke one (or Claude picks it up automatically), Claude stops guessing and follows the studio's way. Each department page on this site walks through the skills that matter for your seat.
A live connection between Claude and the Unreal editor. Through the MCP, Claude can spawn and arrange actors, query the scene, read and edit Blueprints, run console commands, and take a look at what's actually on screen. Skills are the playbooks; the MCP is the hands that execute them. This is how "move all the torches in this room up 20 units and warm the light color" becomes a sentence instead of an afternoon.
What one of us teaches Claude, all of us get. Skills live in a shared, versioned library — not on anyone's laptop. When you hit a weird cook failure and figure out the fix, the move isn't "tell the channel," it's "add it to the skill." See exactly how → Next week, everyone's Claude already knows. This is how the studio compounds: our playbooks get sharper every single week.
Each page below is written for one department: what Claude does for you specifically, the skills you'll lean on, real prompts to try on day one, and how the Unreal MCP shows up in your work.
Six habits. They're the difference between an AI that saves you hours and one that wastes them.
Your Lasting Light Claude account comes from your lead. Then follow the Setup guide → — it has the exact one-line install for Mac and Windows, sign-in, and how to connect the Unreal MCP. About 15 minutes, once. If you work in the Unreal project, pull the repo — the shared skills and MCP config ride along with it.
Claude Code is dramatically more useful when it's opened in the project folder — it can see the code, the config, and our skills. For non-project work (docs, email, research), the Claude app is the right tool.
First prompt: ask it to explain something you actually work with. You'll immediately feel the difference between a search engine and a teammate that has read the codebase.
Go to your department page on this site, pick the first skill listed, and try its example prompt. Watch what Claude does — you'll see it follow our playbook step by step instead of improvising.
Before your first week is out, find one thing Claude got wrong or didn't know — and feed it back into the group knowledge system. That's the whole flywheel. You'll never look at "somebody should write that down" the same way again.
Everything on this site gets you working. These go deeper — and they're all free.
Anthropic's hands-on course on working the way we do here: steering long sessions with plan mode, configuring instructions and permissions, automating repetitive tasks, and verifying unsupervised runs. The single best follow-up to this site — take it your first week.
anthropic.skilljar.com → Course catalogThe full free catalog — prompting fundamentals, building with the API, MCP deep dives. Good for going from "I use Claude" to "I build with Claude," at your own pace.
anthropic.skilljar.com → Reference docsThe official manual: every command, setting, hook, and MCP option. You won't read it cover to cover — you'll search it the moment you wonder "can it do X?" (It can.)
code.claude.com/docs →The site doesn't end at day one. This is where you feed the system back, level up past the basics, and settle the questions everyone quietly has.
Every command, the model habit, the everyone-six skills, quick fixes, and a glossary — on a single printable page. Pin it next to your monitor for week one.
cheatsheet → The flywheel, made easyThe exact template for writing a skill, a before/after example, and a 30-second form to suggest one or flag a problem — no PR required to start.
contribute → Beyond the basicsParallel work for big sweeps, when to reach past Sonnet, reviewing Claude's output well, and writing your first skill.
week two → Straight answersDoes it see code outside this project? What if it's wrong? Can I use my personal account? The questions people don't ask out loud.
faq → 30-second pickerAnswer two questions, get the model, effort, and mode to use for the thing you're about to do.
quiz →