Write with an agent

How it works

Mothlight projects are plain JSON, and the format is deliberately forgiving: almost every field has a default, so a file containing nothing but a name and a few lines of script is valid. That is the whole trick. Your assistant writes the structure and the words, and every shot arrives in the editor already written, waiting for you to add a picture.

• Shots play in order on a 1080×1920 canvas at 30fps.
• A shot with no visual shows as “needs a visual” in the editor — that is the point.
• Everything else has a sensible default, so a file with just names and scripts is valid.
• Save the result as a .json file and open it with Mothlight, or import it here.

The prompt

Copy this, replace the topic on the last line, and paste it into your assistant of choice.

Write a short-form video script as a Mothlight project file.

Return ONLY a JSON object, no prose and no code fences, in this shape:

{
  "schemaVersion": "0.1",
  "name": "<a short title for the video>",
  "segments": [
    { "script": "<one or two spoken sentences>" },
    { "script": "<the next beat>" }
  ]
}

Rules:
- One shot per beat of the story. Aim for 4-8 shots.
- Each "script" is what a narrator says out loud over that shot. Keep it to one or
  two sentences — roughly 3-6 seconds of speech.
- Write for the ear, not the page: short sentences, plain words, no headings or
  bullet points inside a script.
- Do not invent image, video, or audio fields. The human adds the pictures.
- The whole video should run about 30-60 seconds.

Topic: <describe your video here>

Opening the result

Save what you get back as a .json file. Then either open it from your Files app, share it to Mothlight, or use Import project… from the menu on the project list. If something is wrong with the file, Mothlight says which shot has the problem rather than showing a stack trace.

Beyond the basics

The full format — schema version 0.1 — also covers per-shot durations, captions, text overlays, Ken Burns on stills, video trims, and a project soundtrack. The quickest way to see all of it is to build a project in the app and use Export project: what comes out is exactly what goes back in.