Playbooks
Overview
A playbook is free-form standing guidance the Assistant reads every turn — house style, default image sizes, naming conventions, model preferences, anything you'd otherwise have to repeat. Playbooks are how you teach Loft your conventions once instead of restating them each time.
Where playbooks live
- Project Playbook — set from the Project Detail header (book icon). Applies to everything in the project.
- Asset Playbook — set from the Asset Detail page. Applies when working on that asset.
- User Playbook — your personal defaults, applied across your work.
- Model Playbooks — per-model craft guidance that shapes how prompts are compiled for a given model.
How they're used
The Assistant layers playbooks into its context automatically — project, then asset, then your personal guidance — so more specific guidance refines the broader guidance. Keep them short and declarative; they're read on every request, so concise rules beat long prose.
A playbook is a set of defaults, not a checklist. It fills in what you left unsaid when composing new content. When your message spells out what you want, the Assistant does not add playbook material on top of it, and it does not ask you about playbook items you did not raise.
Edits to an existing image
Select one image and ask for a change to it ("add a glow around her", "remove the sign", "keep everything the same but make the sky dusk") and the Assistant treats it as an edit in place: that image is the only input, the prompt locks composition, framing and subject position, and only the change you asked for is described. Playbook lines and asset descriptions stay out of the prompt, and a character's reference is not attached just because you mentioned them — a second image of someone already in the frame makes the model redraw them. Name the file, or say "reference", when you do want one included.