01
Create a project
Open CineBible, click New Project, and name it after the spot, film, scene, or client job.
Quick Start Guide
Build the memory layer for an AI film.
CineBible keeps approved prompts, seeds, thumbnails, character locks, reference IDs, and version history organized by project so every tool in the workflow can reuse the same production truth.
Project
Recipe
Reference
Export
Fast Path
Use this sequence when you need to turn scattered prompts and references into a reusable project bible.
02
Log each keeper
Paste the final prompt, model, seed, ratio, tags, rating, status, notes, and thumbnail into the recipe form.
03
Reuse the bible
Open recipes, copy prompts, fork versions, link characters and references, then export JSON for backup or handoff.
Step 1
Start with a project
- 1Use the left sidebar to create or select a production project.
- 2Double-click a project name to rename it when the job title changes.
- 3Use Export JSON for the full vault or Export Project for the active project only.
Local storage
CineBible saves data in the browser through IndexedDB. Export JSON when you need a backup, another machine, or a client handoff.
Step 2
Log a recipe
- 1Choose the model: Runway, Kling, Luma, Midjourney, Veo, Sora, or Other.
- 2Paste the exact prompt you sent to the model. This is the main field to preserve.
- 3Add seed, ratio, platform parameters, thumbnail, tags, star rating, status, and production notes.
Quality signal
Mark useful outputs as Keeper, experiments as Iterate, and failed attempts as Reject. The vault filters use those labels.
Recipe Vault
The right pane is where the project becomes searchable production memory.
Search
Find what worked
- Search across prompt text, tags, and notes.
- Filter by model when you only need Runway, Kling, Midjourney, or another platform.
- Filter by rating to isolate the strongest generations.
- Filter by status to review keepers, iterations, or rejects.
Open Card
Use recipe actions
- Copy Prompt sends the saved prompt to the clipboard.
- Fork creates a new version you can edit without losing the original.
- Lineage shows the version tree for a recipe family.
- Edit puts the saved recipe back into the form panel.
Characters
Lock continuity
- 1Open the Characters tab and create one card for each recurring person or product.
- 2Add a reference image, a locked prompt fragment, platform-specific IDs, and director notes.
- 3Use Copy Block to paste a consistency block into a new prompt.
Gallery check
Character galleries show recipes linked to that character, which makes visual drift easier to spot across generated shots.
References
Save reusable IDs
- 1Use the References tab for seeds, SREF codes, CREF URLs, element IDs, and platform handles.
- 2Add the platform, value, tags, notes, and thumbnail so the reference is recognizable later.
- 3Link references to recipes while logging a shot so every keeper carries its source controls.
Versioning
Fork and compare
- 1Open a recipe and click Fork before trying a new variation.
- 2Change only the details you are testing: product reveal, camera move, negative prompt, seed, or timing.
- 3Use Lineage to see which version came from which parent.
Compare tip
Hold Ctrl or Cmd while selecting two lineage items to unlock text diff and A/B compare.
Recommended Workflow
A practical order for commercials, AI films, music videos, and recurring brand assets.
Capture
Save every keeper
Do not rely on model history. Log the output as soon as you know it may be reused.
Connect
Link references
Attach characters and reference IDs to recipes so future prompts inherit the same continuity controls.
Handoff
Export often
Export project JSON before client review, production transfer, or major prompt experiments.