Daily commands
claudeStart a session — from inside the project folder./modelSwap model & effort (or click the model name by the message box)./mcpShow what's connected — unreal should be green when the editor's open./loginSwitch accounts (fixes "signed in but no access").Shift + TabCycle permission modes: ask → auto → plan.EscInterrupt Claude mid-task — course-correct, don't wait it out./rewindThe undo button. Or double-Esc on an empty prompt. Rewind code, conversation, or both to any earlier point in the session./pluginSee what's installed — Unreal, clangd, our studio playbooks. Errors tab tells you what's broken./Type slash + a skill name to invoke it deliberately.The habit
Fable 5 · highPlan. Features, architecture calls, hairy debugging. Pair with plan mode.Sonnet 5 · xhighDo. Execute the approved plan. The everyday workhorse ("extra").auto modeRecommended day-to-day — stops the forty-approvals-an-hour problem.plan modeClaude plans first, edits nothing until you approve. For big work."prove it"End Unreal tasks with "verify it in the editor" — done means demonstrated.The everyone-six skills
build-and-cook — build/check the project, fix what breaks, "is the nightly green?"
verify-in-editor — prove the change in the running game before "done."
log-and-crash-triage — paste any error; get cause, dupe-status, fix.
source-control — clean changelists, binary locks, checkout untangling.
meeting-to-action — notes/transcript in; decisions + owners out.
spec-to-plan — doc in; tickets, dependencies, open questions out.
If it breaks
command not found — close the terminal completely, open a fresh one.
"irm is not recognized" — you're in CMD, not PowerShell. PS C:\ = right window.
unreal shows failed in /mcp — editor open? plugin enabled? Toolset registries turned on? started in the project folder?
it went sideways and I let it run — /rewind, restore code and conversation. Nothing is unrecoverable.
no access after sign-in — /login, switch to your Lasting Light account.
Glossary
Skill — a playbook written for Claude: our commands, conventions, checklists.
Move — a project-aware workflow (planning/coordination) rather than an engine task.
MCP — a connection that gives Claude tools; ours drives the Unreal editor.
Connector — a prebuilt MCP with a one-click switch (Drive, Slack, Calendar…).
Effort — how long Claude thinks before acting: low → high → xhigh ("extra") → max.
PIE — Play In Editor; how Claude test-runs the game through the MCP.
Cook — converting project content into a playable build's format.
Changelist — one submitted batch of changes in source control.
The two hard lines
No secrets in AI tools — credentials, keys, contracts: sanctioned setup only, never personal accounts.
Nothing ships unreviewed — a human owns everything that reaches players, partners, or the public.
And one soft one: feed lessons back — if you corrected Claude twice, it belongs in a skill. Say "add this to the skill and open a PR."