Phantra AI: Storyboard
Plans a Phantra beat list, then writes each scene in one project with a consistent look and shared photo references.
Storyboard
A piece in Phantra is a project holding several scenes. A scene is ONE prompt of 4 to 30 seconds, rendered one timed shot at a time; separate scenes are rendered separately and joined afterwards in the library. The storyboard is the beat list that decides how many scenes there are, what each shows, and which photos hold them together. It renders and spends nothing itself; each scene is rendered afterwards, on its own quote and the person's own yes.
Several scenes, or more shots in one?
More shots in ONE scene when the beats share one look, one cast of photos and one continuous memory (the scene's own continuity rides into each shot), and the whole runs 30 seconds or less. Each scene is quoted on its own. Cuts and a change of place CAN happen between windows.
SEPARATE scenes when:
- the piece runs past 30 seconds;
- a part needs different photos (the person alone, then the product alone);
- the look changes (a daylight kitchen, then a night street);
- a part should be re-written or re-rendered without touching the rest;
- the person wants alternates of one part to choose between.
Rule of thumb: a scene is one block the camera could cover in one visit.
Steps
-
projectwith its id for the brief and the look, orcreate_project(title,brief,look) when the piece has no project yet. Settle the look once, in cinematography terms; every scene keeps it word for word. -
elements: list the photos. Decide the cast for the WHOLE piece: which refs, in which order, with whichroles(subject, product, place; light, palette, framing, style for a look-only photo). The first ref is the anchor and should be the same photo in every scene where that subject appears. If a face, product or place has no photo, ask for one (look-matching). A place can also be drawn:generate_imagequotes first and draws only on the person's yes, called again with itsquote_token;add_elementwith thegen:<id>keeps it as the place's photo. A face is always their own photo. -
Write the beat list in the chat and get a yes:
text Piece: 24s product short, 9:16. Look: one window, soft daylight, 35mm. 1. Kitchen, 8s, 2 shots -- Sam finds the tin. Refs: Sam, the tin, kitchen. 2. Hallway, 10s, 3 shots -- the door opens on its own. Refs: Sam, the tin. 3. Doorstep, 6s, 1 shot -- the tin alone on the step. Refs: the tin, house.One line per scene: place, seconds, how many shots, what happens, refs.
-
Write scene 1 in write-scene's five-part shape and save it with
write_scene:prompt,seconds,refs,roles,title("1 of 3 -- Kitchen"),project_id. Repeat for each scene, in order. Keep the opening line and the style block identical across scenes; only the beats change. -
Alternates:
duplicate_scenewith the sourcescene_idand the changedprompt(orrefs,seconds,roles). The copy is a fresh scene to price and render; its stills and clips are never carried over. The copy is titled after the source with "(copy)" added and cannot be renamed from here: tell the person whichscene_idis which and what changed. -
Read the project back:
projectlists every scene with its status;scenereads one with its shots and clips.
Then
Take each scene through price-and-render, one scene at a time: quote with its
scene_id (and the renderer, when one was chosen), show the person the
credits for the keyframes and for the clip beside their balance, and WAIT for
a yes in the chat. Only then approve: what "keyframes" for the stills, or
"clip" with the quote's tokens and the SAME renderer choice the quote was
made with; then job (wait up to 15) until done, and scene for the clips.
One yes covers exactly the quotes the person was shown
and named; anything else needs its own yes. A token works once (a repeat answers already_used
and spends nothing) and a quote lasts one hour. Said in the chat, against the
beat list above, on LTX 2.3 at 1080p:
1 of 3 -- Kitchen: 2 shots, <the clip's credits> (keyframes <theirs> more).
Balance <balance> -> <what is left> for the clip. Render scene 1?
Once the clips have landed, assemble_clips with their gen:<id>s from
library, in order (cut or crossfade), joins them free as a new item in the
library; poll job for the result.
Do not
- Never write a scene over 30 seconds or a window outside 2-10 seconds.
- Never change the look or the anchor photo between scenes without saying so; that is what makes a sequence read as one piece.
- Never rewrite a saved scene with
write_sceneandscene_idwithout showing the new version first; it replaces the text. - Never call
approve, orgenerate_imagewith aquote_token, before the person has seen that price in credits and said yes in the chat; never on their behalf, never twice for one quote, and never say a render has started untilapprovehas answered with a job. refused: insufficient_credits(withneedsandavailable) ends the render: say the scene needs more credits than the workspace has and that credits are added in the studio. Nothing was spent; there is no link to give.
- Downloads
- Security audit
- Pass
- Last updated
- 2w ago
- Current version
- v1.0.0
- License
- MIT-0
