The Companion Installable · Works offline

Keep it in your pocket.

Onboarding is a website. Day two onward is this. The commands you actually type, prompt starters you can paste straight into a session, connector commands, and the four fixes for the four things that go wrong — installed on your phone or desktop, and working with no signal at all.

Free · no app store · 10 seconds Download the companion app Installs straight from this page onto your phone, tablet, or computer — then works with no signal at all. The exact taps for your device are right below.
00 — HOW TO INSTALL IT

Find your device. Three taps.

There's no app store and no account. Your browser turns this page into an app on your device. Pick the block that matches what you're holding — the pictures show what your screen will look like at each step.

iPhone & iPadIn Safari3 steps
1
Make sure you're in Safari

This only works in Safari on iPhone and iPad — Chrome on iOS can't install apps. If you opened this link from Slack or Mail, tap the compass icon to reopen it in Safari first.

Already in Safari? Skip straight to step 2.

2
Tap Share, then Add to Home Screen

The Share button is the square with an arrow pointing up out of it, in the bar at the bottom of the screen. Tap it, scroll the list down a little, and tap Add to Home Screen.

Claude at Lasting Lightlastinglight.dev
Copy
Add to Favourites
Add to Home Screen
Print

Don't see it? Scroll the grey list further down — on a long list it sits below Add to Favourites.

3
Tap Add

A small preview appears with the name LL Claude. Tap Add in the top-right corner. Close Safari and look at your Home Screen — there's a blue icon with a white X on it. That's the app.

Open it once while you still have signal, so it can save everything for offline use.

AndroidIn Chrome2 steps
1
Look for the install banner — or use the menu

Chrome on Android often shows an Install prompt at the bottom of the screen on its own. If it does, tap it and you're done. If it doesn't, tap the three dots in the top-right corner.

lastinglight.dev/app
New tab
Bookmarks
Install app
Add to Home screen
Desktop site
2
Tap Install, then Install again to confirm

The menu item is called Install app on newer Chrome and Add to Home screen on older versions — either one is correct. Confirm, and the icon lands on your home screen.

Open it once with signal so it can cache everything for offline use.

WindowsChrome or Edge2 steps
1
Click the install icon in the address bar

Look at the right-hand end of the address bar, where the web address is. There's a small icon — a monitor with an arrow, or a plus inside a square. Click it.

🔒 lastinglight.dev/app
Install app? Claude at Lasting Light — lastinglight.dev Install

No icon there? Click the menu at the far right instead, then look for Cast, save and share → Install page as app in Chrome, or Apps → Install this site as an app in Edge.

2
Click Install

It opens in its own window with no browser tabs or address bar, and pins to your taskbar and Start menu like any other program. You'll get the dashboard layout on a computer — sidebar on the left, panels on the right.

MacChrome, Edge, or Safari2 steps
1
Chrome or Edge: the install icon in the address bar

Same as Windows — a small install icon at the right-hand end of the address bar. Click it, then click Install. It lands in your Applications folder and your Dock.

2
Safari: File → Add to Dock

Safari on recent macOS installs web apps too, it just calls it something else. With this page open, use the menu bar: File → Add to Dock, then click Add. Same result — its own window, its own Dock icon.

On an older macOS without that menu item, use Chrome or Edge instead.

What you actually get

Two layouts, one app.

On a phone it looks like any other app — a title bar at the top and a row of tabs along the bottom for Home, Prompts, Connect, Fixes, and More. On a computer it's a dashboard: a sidebar down the left with every section and the whole library, content on the right. No browser tabs, no address bar, and no connection required once you've opened it once.

01 — THE ONES YOU'LL TYPE

Six commands and two keys.

Everything else you can look up. These you should know cold.

claudeStart a session — from inside the project folder.
/modelSwap model & effort. Fable 5 high to plan, Sonnet 5 xhigh to do.
/mcpWhat's connected. unreal should be green with the editor open.
/rewindThe undo button. Restores code, conversation, or both.
/pluginWhat's installed, and the Errors tab when something's off.
/loginSwitch accounts — fixes "signed in but no access".
Shift + TabCycle permission modes: ask → auto → plan.
Esc EscInterrupt, then open rewind on an empty prompt.
The habit

Fable to plan, Sonnet to do

Fable 5 · high for features, architecture calls, and hairy debugging — pair it with plan mode. Sonnet 5 · xhigh ("extra") to execute the approved plan. That's the studio convention; swap with /model.

The one rule

End Unreal work with "prove it"

"Verify it in the editor" turns Claude into a self-checking loop — it runs the map, looks at the result, and fixes what it finds before telling you it's done. Done means demonstrated.

02 — PROMPT STARTERS

Paste one. Change the nouns.

Real prompts from the department pages, in one tappable place. Tap a department, hit COPY, edit the specifics. The point isn't the exact wording — it's the shape: context, then what "done" looks like.

you › Add a cooldown to the dash ability — data-driven, designer-tunable from the ability's data asset. Follow our conventions and show me the diff before writing.
you › Review this branch against unreal-cpp before I open the PR. Flag anything that would get called out in review.
you › Build the editor target and fix any compile errors from my merge. Keep going until it's green, then summarize what you changed.
you › The nightly cook failed. Pull the log, find the cause, and either fix it or tell me exactly which asset and who touched it last.
you › QA hit this crash in last night's build [paste callstack]. Triage it: what broke, is it a known issue, and what's the fix?
you › Write functional tests covering the dash cooldown — normal use, spam, and the edge case where the ability data asset is missing. Run the ability suite and show me the results.
you › Read BP_EnemySpawner and tell me why spawns hitch on wave start. If the loop belongs in C++ per our boundary rules, draft the native version.
you › After you land the dash cooldown, verify it in the editor: PIE, dash twice, confirm the second one is blocked for 3 seconds, and check the log for ensures.
you › In the courtyard section of HEX_Chapter2, add waist-high cover so no sightline between spawn points runs longer than 15m. Use our blockout meshes and show me a top-down screenshot when done.
you › Every torch in this level: raise 20 units, warm the light color 10%, and bump attenuation radius to 800.
you › Prototype a grappling hook in Blueprint on the test character: hold to aim, release to fire, reel-in speed as a tunable variable. Keep it clean enough for engineering to read.
you › Explain what BP_DoorPuzzle actually does, step by step, in designer language.
you › If we raise enemy armor 15% across tier 3, what happens to time-to-kill for each weapon archetype? Show me the before/after, then apply it if nothing breaks the 8-second ceiling.
you › After you place the cover, run the map and confirm nothing blocks the player path from spawn to the west gate. Screenshot anything that looks wrong.
you › Lint everything I have checked out before I submit. Fix what's mechanical, list what needs my judgment.
you › Lint /Game/Environments/Chapter2 — full report. Auto-fix naming and folder placement; flag anything over texture budget for me to look at.
you › I just imported 40 rock meshes into /Game/Env/Rocks. Apply our env-prop import preset, generate 3 LODs each, fix names to convention, and show me the before/after list.
you › Find every texture in the project above 2K that's only ever used on props smaller than a meter.
you › Bump roughness 0.1 on every material instance under /Game/Characters/HEX_Vann and screenshot her in the lookdev map.
you › Profile the market scene from the player path. Am I inside budget on the base console target? Rank whatever's over by cost and suggest the cheapest wins.
you › What do I have checked out right now, is any of it locked by someone else, and can you split it into one changelist per asset zone with descriptions?
you › After the LOD pass, open Chapter2 and screenshot the vista from the tower at LOD distances — I want to see if anything pops.
you › Run the full automation suite on the current build and give me a plain-English summary: what failed, what's flaky, what's new since Friday.
you › Three crashes from tonight's session [paste]. Which are dupes of each other, which are known, and what do I file for whatever's new?
you › Bug #2231 says the elevator soft-locks if you jump during the door close. Try the repro in Chapter1_Elevator, capture the state when it locks, and attach everything to the ticket draft.
you › I found a bug where dropping an equipped weapon during a dash dupes it. Write a regression test for that exact sequence.
you › Engineering says #2231 is fixed in this morning's build. Re-run the repro and confirm.
you › Is the fix for the vendor duplication bug in build 4312? If not, which build will have it?
you › Run the release checklist against RC3. Give me a table: item, status, evidence, and anything that needs a human decision.
you › Morning rundown: nightly build status, anything broken and who owns it, and what landed yesterday against the milestone list.
you › We're cutting RC on Thursday. Start the release checklist now and tell me what's at risk of not being green by Wednesday night.
you › Here's the crafting system spec. Break it into tickets by department with dependencies, estimate relative size, and list every open question the doc leaves unanswered.
you › Here's the milestone review transcript. Decisions, action items with owners, risks raised — and flag anything that contradicts what we decided in last week's review.
you › Look across the last three weeks of tickets and build history — which areas of the project are trending unhealthy, and what's your evidence?
you › Here are my notes from the combat review. Turn them into decisions, action items with owners, and open questions.
you › Rewrite this update for the studio channel — same information, half the words, no jargon.
you › Explain replication to me like I'm a designer who's never shipped multiplayer. Use our game as the example.
you › This spreadsheet has our playtest survey results. What are the three things people actually complained about, with counts?
you › I need to tell a teammate their feature slipped. Draft something direct and kind, not corporate.
you › I'm about to argue we should cut the crafting system. Poke holes in my reasoning before I say it out loud.
03 — WHEN IT FIGHTS YOU

Four failures, four fixes.

Nearly every problem anyone reports is one of these. Check them in this order before asking.

01

"claude: command not found"

Close the terminal completely and open a fresh one. Installers update your setup, but only brand-new windows see it.

02

unreal shows failed in /mcp

In order of likelihood: is the editor actually open? Is the plugin enabled? Are the Toolset registries turned on inside Unreal? Did you start claude from inside the project folder?

03

Signed in but "no access"

You're on a personal account. Run /login and switch to your Lasting Light account. If the studio account itself fails, that's a ticket for your lead — not a you-problem.

04

It went sideways and I let it run

/rewind — or double-Esc on an empty prompt. Restore code, conversation, or both to any earlier point in the session. Nothing here is unrecoverable.

04 — CONNECTOR COMMANDS

The installs, without the reading.

The four worth having on day two. Full library — 17 connectors, filterable, with trust levels and the ones we recommend against — is on Connections.

Unreal Engine

Epic
$ claude plugin install unreal-engine-skills-for-claude-code@claude-plugins-official

C++ diagnostics

Official
$ claude plugin install clangd-lsp@claude-plugins-official

Sentry — crash triage

Official
$ claude plugin install sentry@claude-plugins-official

Jira & Confluence

Official
$ claude plugin install atlassian@claude-plugins-official

If the marketplace isn't found, run claude plugin marketplace add anthropics/claude-plugins-official once, then retry.

05 — THE FULL SITE

When you need more than a reminder.

Offline

This works with no signal.

Once you've opened the companion, this page plus the cheat sheet, skill library, connections, department pages, and FAQ are stored on your device. Useful on the floor, on a plane, or anywhere the studio wifi gives up. Pages update themselves whenever you're back online.