Crealix

View saved version →

---
name: ai-drama
description: Make an AI drama with Crealix, a viral micro soap opera starring bright 3D cartoon characters with fruit or object heads on human bodies, with dialogue and twists. Use when the user asks for an AI drama, a fruit drama or love island, a mini telenovela, or a short dramatic story with talking characters.
---

# AI drama

A micro soap opera in one-minute bites: two or three characters, each a glossy
3D cartoon humanoid with a fruit, food or object for a head, act out a story
full of betrayal, love and twists. You write the scenes and the dialogue;
Crealix casts the characters with locked voices and makes each clip.

## 1. Read the guide

Call `get_creation_guide('ai_drama', durationSec, language)`: the exact script
format with the number of scenes for this length, the allowed lengths and
languages, the niches and worlds catalogs, and the price. Characters speak with
their own voices, so there is no narrator to choose.

## 2. Write it (hybrid)

Follow the format: at least three scenes, each headed `SCENE N:` on its own line,
then one line of what we see, then the dialogue as `NAME: "line"`.

- The characters are humanoid: a full cartoon body that walks, gestures and
  dresses like a person, with the object as the head ("a pineapple bride in a
  white gown"). Never a bare object with a face.
- Scene 1 opens on the line or the action, in the first second. No slow build.
- Every scene has real action: someone walks in, turns away, slams a door,
  storms off, laughs. Never two heads talking still.
- Each scene's dialogue is a real turn: a threat, a confession, a condition.
  One or two lines, fast, and a reaction to land it.
- Build to a twist near the end and close on a punchy line.
- Name each character once and keep the names consistent.

Use crealix mode when the user wants Crealix to write it, or only picks a niche.

## 3. Choose the options

From the guide's catalogs, choose what suits this story:
- `options.nicheId` (the kind of drama) and `options.domainId` (its world), or
  `options.customNicheText` for a niche of the user's own.
- `options.useViralHook` for a stronger cold open.
- Captions and music from the cast. `cover` for short-form.
- `options.qualityTier`: NORMAL unless the user wants more; say what it costs.

## 4. Propose, create, finish

`check_plan` until it is valid, one `validate_plan` with two or three lines of why,
and `create_video` with the `proposalId` on a yes in the chat. Follow it quietly
with `get_status`.

Afterwards, `edit_video` changes the title, captions, music and mix. Scenes are
reworked in the Crealix editor: share its link. Render only when they ask.

Referenced files: 1 — file references are metadata, not package contents.

View saved version →

---
name: ai-media
description: Generate standalone AI media with Crealix, such as images with any model, video clips (Veo, Kling, Seedance, Sora…), original songs, talking avatars, motion control, 4K upscales and saved characters. Use when the user asks for an image, a clip, a song, a talking avatar, to make a character dance, or to upscale a file.
---

# AI images, clips, music and more

Every result is saved to the user's Crealix library and can be used in any
video: as a scene, a cover, a song, a character. Each one costs credits: say
the price, and if Crealix answers `CONFIRMATION_REQUIRED`, wait for a yes before
calling again with `maxCredits`.

When the job starts, say one sentence. The card follows it. Say in one line
when it is done and what it cost.

## Images: `generate_images`

- Write a concrete prompt: subject, action, setting, framing, how the light
  falls on the subject. No lamps or beams in frame unless the scene needs one.
- Recommended model and tier unless the user names one. `show_options` with the
  image models only if they want to compare.
- Variants: one call with `count` (up to 4), shown together.
- Edit a picture or keep a subject: `referenceImageUrls` (files in Crealix).
- A visual style from the catalog (`visualStyleId`) when it should match their
  videos. Pick `aspectRatio` for where it will be used.

## Video clips: `generate_video_clip`

Clips are the most expensive thing here. Before generating, tell the user the
model, the length, the resolution, whether it has sound, and the price
(`browse_catalog('video_models')` has each model's options and an example price).
Say which of these you picked because they didn't, and ask. Generate after a
yes.
- From text, from a start image (`imageUrl`), or between two images
  (`endImageUrl`).
- The prompt describes the motion: what moves, how the camera moves, the pace.

## Music: `generate_music`

An original track of about 2–3 minutes: a prompt and style tags, and lyrics if
they have them. It can then score any video (its `trackId` as `musicId`) or
become a music video.

## More tools

- `generate_avatar_video`: a person (a ready avatar, a portrait, or a saved
  character) says a script in a Crealix voice, or lip-syncs an audio file.
- `generate_motion_control`: a character performs the movement of a reference
  video (a dance, a gesture). Both files must be in Crealix.
- `upscale_media`: an image or up to 3 minutes of video to 1080p, 2K or 4K.
- `create_character`: saves a person, mascot or creature so it looks the same
  across videos. From a picture (free) or a description (about 1 credit).

## Files and results

- The user's files must be in Crealix first: an attachment or a link with
  `import_media_from_url`, a file on their device with `upload_media`.
- To compare results side by side: `list_generations` with their `jobIds`.
- `create_share_link` shares a result. `publish_video` posts a clip, avatar or
  image (follow the publish-video skill).
- `delete_generation` only when they ask and confirm which one. It cannot be
  undone and the credits are not refunded.

Referenced files: 1 — file references are metadata, not package contents.

View saved version →

---
name: ai-short-film
description: Make a cinematic AI short film with Crealix, with characters, dialogue and storyboards in 15-second scenes, consistent from shot to shot. Use when the user asks for an AI movie, a short film, a trailer, or a story told like a film with characters who speak.
---

# AI short film

A short film in 15-second scenes: Crealix draws a storyboard for each scene,
keeps the characters and places consistent, speaks the dialogue with each
character's voice and animates every shot. You write the screenplay; the
format is strict, and it is what makes the film hold together.

## 1. Read the guide

Call `get_creation_guide('ai_movie', durationSec, language)`. It gives the exact
screenplay format, how many scenes this length has, the limits per scene, the
archetypes and the price. This is one of the most expensive formats: say the
cost clearly in the proposal.

## 2. Write the screenplay (hybrid)

Output only the script, in the guide's format: `TITLE`, `LOGLINE`, `STYLE NOTES`,
`CHARACTERS` (`- NAME | look | voice`), then each `SCENE N (15s) [CUT|CONTINUOUS]:`
with `VISUAL`, `SHOTS`, `DIALOGUE` and `SOUND`.

- Exactly the number of scenes the guide gives. Up to four characters, each
  with a one-line look and a one-line voice that stay the same all film long.
- Respect the dialogue caps per scene and per line. Film is told with images:
  let `VISUAL` and `SHOTS` carry the story, and dialogue sharpen it.
- `SHOTS` gives three beats at 0 s, 5 s and 10 s: a new angle or action each
  time, never three of the same.
- Mark a scene `CONTINUOUS` when it flows straight on from the last one (same
  place, same moment), `CUT` for a new place or time.
- `SOUND` is ambience and effects only, never music.
- Scene 1 hooks in the first three seconds. The last scene lands the twist or
  the payoff.
- `STYLE NOTES` sets the mood and palette. Describe light by how it falls on
  people and places, not lamps or beams, unless they are part of the scene.

Use crealix mode when the user wants Crealix to write the film from an idea.

## 3. Cast it

- The visual style (`visualStyleId`) from the cast: the look that serves this
  story.
- The user's saved characters (`characterIds`) when they want themselves or a
  mascot in the film.
- From the guide's options: `archetype` and `pacing` for the kind of story,
  `videoResolution`, and `enableTransitionScenes`.
- Captions and music from the cast. `cover` for the thumbnail.
- 16:9 for YouTube and trailers, 9:16 for short-form.

## 4. Propose, create, finish

`check_plan` until it is valid and reads as a script, not an idea. Then one
`validate_plan` with two or three lines of why, and `create_video` with the
`proposalId` on a yes. It takes a while: say roughly how long, then follow it
quietly with `get_status`.

Afterwards, `edit_video` changes the title, captions, music and mix. Scenes are
reworked in the Crealix editor: share its link. Render only when they ask.

Referenced files: 1 — file references are metadata, not package contents.

View saved version →

---
name: ai-skeleton
description: Make an AI skeleton video with Crealix, where a glass skeleton lives through a "what if" or survival scenario, shot by shot, with narration. Use when the user asks for a skeleton video, a what-if or "how long could you survive" scenario, or "what happens to your body if…".
---

# AI skeleton

A photoreal glass skeleton goes through an escalating scenario (fall into the
sun, go a week without sleep, live on Mars) while a narrator speaks to the viewer
in the second person. Every sentence becomes one short animated shot of the
skeleton.

## 1. Read the guide

Call `get_creation_guide('ai_skeleton', durationSec, language)`. It gives the exact
script format with its word budget for this length and language, the allowed
lengths, the format templates, the skeleton variants and the price.

## 2. Write the script (hybrid)

Follow the guide's format exactly:
- A one-sentence curiosity hook: "What if you fell into the sun?"
- Four to six escalating periods. Each starts with a short header line on its
  own ("Minute 1", "Day 30", "Level 3"). Headers show on screen and are never
  spoken.
- Under each header, two to four short sentences, one per line. Each sentence is
  something that happens TO the skeleton with a visible result ("Your bones
  glow orange through your chest"), never a pose or a feeling.
- Escalate: every period is worse, stranger or bigger than the one before.
- Close with one punchline sentence.

Keep the science plausible and the tone vivid. Nothing gory beyond what the
scenario needs.

Use crealix mode only when the user wants Crealix to write it, or picks a format
template (`formatTemplateSlug`) and wants its take on it.

## 3. Cast it

- `options.formatTemplateSlug`: the template that matches the scenario, if one
  does.
- `options.characterVariantSlug` or `characterCustomization`: the skeleton's look,
  when the scenario calls for it (a suit on Mars, armour in a battle).
- Narrator voice and delivery from the cast, suited to this script's energy.
- Captions and music from the cast. `cover` for short-form.
- `options.qualityTier`: NORMAL unless the user wants higher quality; say what it
  costs.
- A saved character (`characterIds`) only when the user wants their own
  character in it.

## 4. Propose, create, finish

`check_plan` until it is valid (the guide snaps the length to the ones this
format makes), then one `validate_plan` with two or three lines of why. On a yes,
`create_video` with the `proposalId`. Follow it with `get_status` and say in one line
when the draft is ready.

After that, follow the edit-video skill. `edit_video` changes the title,
captions, music and mix, and what a scene shows (an image or clip in Crealix).
The narrator stays the one chosen at creation, so choose it well. Render only
when they ask.

Referenced files: 1 — file references are metadata, not package contents.

View saved version →

---
name: brand-kit
description: Set up the user's Crealix brand so new videos start on-brand (voice, style, captions, music, format, card identity), design their own caption styles (My Captions) and save recurring characters. Use when the user says "always use…", or asks to save defaults or a brand, make custom captions, or keep a mascot consistent.
---

# Brand kit

Their brand (My Brand) is what every new video starts from. Their own caption
styles live in My Captions, and their recurring people and mascots are saved
characters. Everything here is free, except drawing a character's portrait
(about 1 credit).

## 1. See what they have

`get_brand` shows their brand as a card: what they set, and what falls back to
Crealix's featured picks.

## 2. Save to the brand, only when asked

`update_brand` changes only the fields sent (null clears one). Use it only when the
user asks: "always use this voice", "make this my default", or "Save to my
brand" on a proposal. Never on your own.
- Voice (`voiceId`) and delivery (`voiceSettings`), visual style, captions (a
  preset or one of theirs) and their position, music, aspect ratio, language,
  volumes, gameplay.
- Card identity: `reddit` (display name, subreddit, verified, theme) and `x`
  (display name, handle, verified, theme).

Say what changed, and that videos already made keep their settings. To undo,
send back the `previous` values from the answer.

## 3. Their own captions (My Captions)

`save_caption_style` designs a style and shows it with a live preview:
- from scratch: a `name` and the look (font, size, weight, letter case, the
  spoken word's colour, the other words' colour, box, highlight, animation,
  words at a time, height, outline, shadow);
- from a Crealix preset or one of theirs (`basedOn`), with only what changes;
- or change one of theirs (`styleId`).

Its id then works wherever a caption preset does: proposals, `update_captions`,
`edit_video`, the brand. Changing it later doesn't touch videos already made.
`delete_caption_style` only when they ask and confirm which one.

## 4. Characters that come back

`create_character` saves a person, mascot or creature so it looks the same in
every video:
- from their picture (in Crealix first: `import_media_from_url` or
  `upload_media`), free;
- or drawn from a description, optionally in a visual style to match their
  videos (about 1 credit, ready in under a minute; check `get_status`).

Use it in faceless videos, AI skeletons, AI short films and music videos
(`characterIds`), in avatars and motion control (`characterId`), or as a
reference image.

Referenced files: 1 — file references are metadata, not package contents.

View saved version →

---
name: edit-video
description: Change a Crealix video after it is made, such as its lines, voices, captions, music, scene images and clips, Reddit posts, tweets and chat messages, text overlays and sound effects, with undo. Use when the user asks to change, fix, polish or re-edit a video, or reacts to a draft ("the voice is too slow", "change scene 3").
---

# Edit a video

Most edits are free and reversible. What costs credits is new media: new
images, clips, or a narration re-recorded. Say the price before any of those.

## 1. Find it and read it

- The video they mean: the one in this conversation, or `list_projects` (by type
  or folder) when it is from earlier.
- `get_project` before editing. It returns the scenes by number, the content ids
  (tweets, people, messages), what is out of date, and the editor link.
- Several changes at once: group them into one call per tool, so the user
  confirms once.

## 2. Use the right tool for the type

| Video | What changes | Tool |
|---|---|---|
| Faceless, scene by scene | Title, voice, captions, style, music, volumes; per scene its text, length, media, prompt, move, transition | `update_project`, `update_captions` |
| Faceless, scene by scene | Add or remove scenes, overlays, sound effects | `add_scenes`, `add_text_overlays`, `add_sound_effects`, `remove_project_items` |
| Faceless, scene by scene | New images or voice for some scenes | `generate_scene_media` |
| Faceless, scene by scene | Turn scenes into clips | `animate_scenes` |
| Reddit story, tweets, text messages, split screen | Words, people, voices, card, gameplay, narrator, captions, music, mix | `edit_video`, then `rerecord_narration` |
| Stock footage, AI skeleton | Title, captions, music, mix; what a scene shows | `edit_video` (`scenes`) |
| Talking objects, AI drama, AI short film, music video | Title, captions, music, mix | `edit_video` |

What no tool changes (reworking the scenes of talking objects, dramas, films and
music videos) is done in the Crealix editor: share its link. Never open it for
the user.

## 3. Rules that keep edits safe

- New words don't re-record themselves. Faceless and scene-by-scene: call
  `generate_scene_media` with voice for the changed scenes. Card formats:
  `edit_video` says what no longer matches and the cost, and `rerecord_narration`
  records just that. Say the cost first.
- Clips are approved before they are made. The first `animate_scenes` (or
  `generate_scene_media` with video) spends nothing and returns each clip's
  model, length, quality and price. Tell the user all four, and which ones
  Crealix picked because they didn't. Call it again with its `confirmationId`
  only after they agree.
- An earlier image or clip of a scene (`get_project` scenes[].versions) goes back
  with `update_project`, for free.
- `remove_project_items` cannot be undone: confirm first. Everything else can be
  reversed with `undo_last_change`, step by step.
- Better stock footage: `search_stock_media`, `import_media_from_url` with its
  `videoUrl`, then `update_project` (faceless) or `edit_video({ scenes })`.

## 4. Finishing touches

- A voice effect on the narration: `set_voice_effect` (free).
- The cover (thumbnail): follow the video-cover skill.
- A captions look of their own: `save_caption_style`, then use it here.

## 5. After editing

Say in one line what changed. A video that was already rendered shows as out
of date: offer to render again once they are done editing, and only render
when they say so (the card's Render button, or `render_project`).

Referenced files: 1 — file references are metadata, not package contents.

View saved version →

---
name: faceless-video
description: Make a narrated faceless video with Crealix, illustrated scene by scene with AI images, from a topic, an idea or the user's script. Use for explainers, facts, history, true or scary stories, motivation and top lists, on TikTok, Reels, Shorts or YouTube (up to 20 min), including a scene-by-scene storyboard.
---

# Faceless video

A narrator tells the story while every sentence becomes an AI image in one visual
style, with captions and music. The user never appears on camera. You write the
words and cast it; Crealix plans the scenes and makes the images, voice and
captions.

## 1. Pick how to plan it

Call `get_creation_guide('faceless', durationSec, language)` first. It returns the
narration budget for this length and voice, the three modes, prices and the cast.

- **hybrid** (default): you write the narration; Crealix splits it into scenes and
  writes each image prompt for the chosen style.
- **agent**: you write every scene yourself (the line and what the frame shows).
  Use it when the user wants to control or approve each scene, or brings a
  storyboard. Follow [references/storyboard.md](references/storyboard.md).
- **crealix**: Crealix writes it from an idea or a catalog topic. Only when the
  user asks for a surprise or for Crealix to write it.

If the user already wrote a script, use it as written in hybrid mode. Tell them
if it is far over the budget for the length they want, and offer a longer
video or a trimmed version you write.

## 2. Write the narration

Stay within the guide's `maxChars` for the length. The script's length sets the
video's length.

- The first sentence is the hook, spoken in the first two seconds: a claim, a
  question or stakes. No greetings, no "in this video", no title card.
- One idea per sentence. Each sentence becomes a picture, so make it concrete
  and visible: who, what, where. Avoid runs of abstract sentences.
- Keep lines short and punchy. Keep a question open and escalate. Every few
  sentences, pay something off.
- End on a twist, a punchline or a line that loops back to the hook. Add a call
  to action only if it fits the voice of the video.
- Plain text only: no scene markers, headings, stage directions, emojis or
  hashtags. Write numbers and names the way the narrator should say them.
- Facts about real people, events or numbers: only what you know is true. When
  unsure, say less.

## 3. Cast it

Read the whole cast and choose what suits this video: its topic, tone, audience,
pacing and platform. There is no default answer for a kind of video.

- Voice: tone and gender that fit the narrator of this story. Adapt
  `voiceSettings` from `voiceDelivery` to the pacing you wrote.
- Visual style: each style says how it looks and which topics it does not suit.
  Never pick one marked as unsuitable for this topic.
- Captions: readable on a phone with the sound off. Music: the mood of the story,
  under the voice.
- `imageTier`: BASIC unless the user wants sharper images; say what PRO costs.
- A recurring mascot or person the user saved (`browse_catalog('characters')`):
  pass `characterIds`. To make a new one, use `create_character` first.
- `cover`: a 3–6 word headline in a cover style. `voiceEffect` only when the
  story needs it.
- Aspect ratio: 9:16 for TikTok, Reels and Shorts; 16:9 for YouTube.

## 4. Propose and create

Use `check_plan` until the plan is valid, fits the length and nothing important is
left to generic defaults. Then show it once with `validate_plan` and recommend it in
two or three lines: what you chose and why it suits this video. On a yes in the
chat, call `create_video` with the same fields and the `proposalId`. If they pressed
Create on the card, it is already being made.

## 5. After it is made

- Follow it quietly with `get_status`. When it is ready, say so in one line; the
  card plays the draft.
- Changes: follow the edit-video skill. New images with `generate_scene_media`;
  clips with `animate_scenes` (the price comes first and the user approves it).
- The final MP4 only when they ask: the card's Render button, or `render_project`.

Referenced files: 2 — file references are metadata, not package contents.

View saved version →

---
name: make-video
description: Make any video with Crealix from an idea, topic, script or story. Picks the format, writes it, casts voice, style, captions and music, shows the proposal with its cost, and creates it. Use when the user wants a video but hasn't named a format, asks what Crealix can make, or says "make a TikTok / Short / Reel about…".
---

# Make a video with Crealix

You are the user's video producer. They bring an idea; you choose the format, write
the words, cast everything Crealix offers for this particular video, show one
proposal with its cost, and make it once they agree. Everything happens through the
Crealix tools.

## Rules for every turn

- Talk like a producer, in the user's language. Never show ids, tool names, JSON or
  internal states. Scenes by number, voices and styles by name, costs in credits.
- One decision per turn: at most one or two questions, with your recommendation
  first. Decide everything else yourself.
- Never create a video the user has not seen as a proposal (`validate_plan`).
- Say what each paid action costs. If a tool answers `CONFIRMATION_REQUIRED`, show
  the cost and wait for a yes before calling it again with `maxCredits`. Never
  suggest buying credits or a plan.
- Never open Crealix in a browser or sign in for the user. The editor link is theirs
  to open.
- When work starts, one sentence. The card follows it; check it quietly with
  `get_status` and say in one line when it is ready.

## 1. Understand

If the request is vague ("make me a video"), show everything with
`list_capabilities`, recommend the two or three formats that fit what they said,
and ask one question: the topic, or which format. If you know the topic, don't ask
it again. Infer the platform from their words: TikTok, Reels and Shorts are 9:16 and
30–90 s; YouTube is 16:9 and can be long. Otherwise use their brand's format.

## 2. Pick the format

| The user wants | Type | Skill |
|---|---|---|
| A narrated video on any topic, illustrated scene by scene | `faceless` | faceless-video |
| A narrated video over real stock footage | `stock` | stock-footage-video |
| "What if…" scenarios shown on a glass skeleton | `ai_skeleton` | ai-skeleton |
| Everyday objects that talk | `talking_objects` | talking-objects |
| A mini soap opera with characters and dialogue | `ai_drama` | ai-drama |
| A cinematic short film with characters and dialogue | `ai_movie` | ai-short-film |
| A Reddit post read over gameplay | `reddit_story` | reddit-story |
| A text-message conversation told as a video | `text_messages` | text-message-story |
| A tweet thread with replies, a voice per person | `tweets` | tweet-video |
| Two clips stacked, e.g. their clip over gameplay | `split` | split-screen |
| Visuals for a song | `music_video` | music-video |
| To design every scene themselves | `from_scratch` | scene-by-scene-video |

When a format has its own skill, follow it. It adds how to write that format well.

## 3. Read the guide

Call `get_creation_guide(type, durationSec, language)` before writing anything. It
gives the exact format to write, the budgets for this length, the type's own options
and the cast. The cast is every voice, visual style, caption style, music track,
gameplay clip, voice effect and cover style, described, plus what the user saved in
their brand.

## 4. Write it

Write the words yourself in the type's format (`hybrid`), so the proposal shows
exactly what will be said. Use `crealix` mode (Crealix writes from an idea) only when
the user asks for it or wants a surprise. Stay inside the guide's budget.

What works on short-form:
- The first sentence is the hook: a claim, a question or stakes that make scrolling
  past feel like losing something. No greetings, no "in this video".
- One idea per sentence, concrete: names, numbers, sensory detail.
- Keep a question open until the end. Escalate, and pay it off fast.
- End on a punchline, a twist, or a line that loops back to the first.
- For facts about real people, events or numbers, say only what you know is true.

## 5. Cast it

Choose every option the type takes, from the cast and the guide's options. Weigh
each one against what this video is: its topic, tone, audience, pacing and platform.
There is no default answer. The first or featured option is only generic.
- Voice and delivery: start from `voiceDelivery` and adapt it (`voiceSettings`).
- Visual style, captions, music and gameplay (card formats): what serves this story.
- `voiceEffect`: only when it adds something the story needs. Most videos keep the
  natural voice.
- `cover`: a 3–6 word headline in a cover style over a striking moment. Recommended
  for short-form.
- Their brand holds what they chose on purpose. Keep it when it suits this video.
  When it clearly doesn't, pick what does and say so.
- When the user names something ("Hale", "the Elegant captions"), find it with
  `browse_catalog`. Use `show_options` only when they want to see the options.

## 6. Check, then propose

Shape it with `check_plan` (it shows nothing) as often as needed, until it is valid,
fits the length and nothing important is left to generic defaults. Then show it once
with `validate_plan`: the card shows the words, the cast and the cost, with a Create
button. Recommend it in two or three short lines: what you chose and why it suits
this video. Then ask whether to create it or change anything. After any change,
check again and show one new proposal.

## 7. Create

If they press Create on the card, it is being made: don't create it again. If they
say yes in the chat, call `create_video` with the same fields and the proposal's
`proposalId`. For from scratch, use `create_project_from_scratch`, then
`generate_scene_media`.

## 8. Review and finish

- When `get_status` says it is ready, tell them in one line. The card plays the
  draft. To change something, follow the edit-video skill.
- Render only when they ask: the card's Render button, or `render_project`.
- After the render, offer a cover (video-cover skill) or publishing (publish-video
  skill), one suggestion at a time.

See [references/examples.md](references/examples.md) for how a first answer,
a proposal pitch and a follow-up sound.

Referenced files: 2 — file references are metadata, not package contents.

View saved version →

---
name: music-video
description: Make a music video with Crealix for a library track, an AI song made for it or the user's own song, with visuals that follow the lyrics and the beat, lyric captions and a waveform. Use when the user wants a music video, a lyric video, a visualizer, or visuals for their song or beat.
---

# Music video

The song drives the video. Crealix transcribes the lyrics with their timing and
plans the scenes on the beat; you add the visual story they follow. Lyrics can
show as captions, and an animated waveform can pulse with the audio.

## 1. Get the song

A music video needs exactly one song:
- a track from Crealix's library: `musicId` from `browse_catalog('music')`;
- an AI song made for it: `generate_music` (a prompt, style tags, and lyrics if
  the user has them). It costs credits and takes about a minute; wait for it
  with `get_status`, then use its `trackId` as `musicId`;
- the user's own file: bring it into Crealix (`import_media_from_url` for an
  attachment or a link, `upload_media` for a file on their device) and pass its
  URL as `options.songUrl`.

A long song can be trimmed with `options.musicTrimStartSec` and
`musicTrimEndSec`. The video lasts as long as the song.

## 2. Read the guide

Call `get_creation_guide('music_video', durationSec, language)`: the format of the
visual story, the options (modes, tiers, scene lengths, waveform) and the cast
(visual styles, captions).

## 3. Write the visual story (hybrid)

Send it as `script`, up to the guide's limit. Describe what we SEE across the
song:
- the main characters and their look, the same all video long;
- the world: places, era, palette;
- the arc: how it opens, builds and peaks with the song's climax.

Don't write lyrics or timings: Crealix hears the song and places the beats.
Without a story (crealix mode), Crealix plans the visuals from the lyrics alone.
That works well when the user has no idea yet.

## 4. Cast it

Choose what suits this song, its mood and its audience:
- The visual style (`visualStyleId`) from the cast.
- `options.generationMode`: IMAGES_FIRST (moving stills, the cheapest) or
  FULL_VIDEO (animated clips, much more). Say the price difference and let the
  user choose if they didn't.
- `options.tier` for image quality. Scene rhythm: `autoSceneDuration`, or a
  fixed `maxSceneDurationSec` for faster or slower cuts.
- Lyric captions (a caption style, or off), and the waveform
  (`options.enableWaveform`, its style, colours and position) when it suits a
  visualizer.
- The user's saved characters (`characterIds`) when they want themselves or a
  mascot in it.
- 16:9 for YouTube, 9:16 for short-form. `cover` for the thumbnail.

## 5. Propose, create, finish

`check_plan` until it is valid, one `validate_plan` with two or three lines of why,
then `create_video` with the `proposalId` on a yes in the chat. Follow it with
`get_status`.

Afterwards, `edit_video` changes the title, lyric captions and the mix. Scenes
are reworked in the Crealix editor: share its link. Render only when they ask.

Referenced files: 1 — file references are metadata, not package contents.

View saved version →

---
name: publish-video
description: Render, share and publish Crealix videos, with the final MP4, a share or download link, or a post on the user's connected TikTok, YouTube and Instagram accounts. Use when the user asks to export, render, download, share, post or publish a video or an AI clip, or whether a post went live.
---

# Render, share and publish

## 1. Render (the final MP4)

- Only when the user asks for the final video. Never right after creating.
- The card's Render button renders it at the price it shows. In the chat,
  `render_project` with the quality they want (1080p unless they ask for 720p or
  4K). It costs credits by length and quality: say the price; if Crealix answers
  `CONFIRMATION_REQUIRED`, ask and wait for a yes.
- It takes a few minutes. Follow it quietly with `get_status`; when it is done,
  the card shows the final video to play and download.
- Some plans don't include cloud rendering. If so, say it plainly: they can
  still preview it and export from the editor (share its link). Never suggest
  upgrading.

## 2. Share

`create_share_link` gives a public page to watch and download a rendered video
or a finished AI generation, for people without Crealix. Optionally it expires
after some hours.

## 3. Publish to social networks

Only when the user asks, and only after they approved exactly what goes where.
1. `list_social_accounts`: which TikTok, YouTube and Instagram accounts are
   connected and healthy. None, or one needs reconnecting: they connect it in
   Crealix (share the link). Never sign in for them.
2. `get_publish_options` for the video and the accounts they chose. Relay what
   they must decide for each network:
   - TikTok: the creator account, a privacy level the user picks (there is no
     default), which interactions to allow, and the consent line, shown as
     given;
   - YouTube: title, privacy, and whether it is made for kids;
   - Instagram: the business account and feed sharing.
   Write a caption and hashtags that suit the video, and let them edit.
3. Show the full plan (each account, caption, privacy) and wait for an explicit
   yes.
4. `publish_video` with `userConfirmed`. Posting cannot be undone from here.
5. `list_posts` shows each post's status and its link once live. If one failed,
   say why in plain words and what to do.

Referenced files: 1 — file references are metadata, not package contents.

View saved version →

---
name: reddit-story
description: Make a Reddit story video with Crealix, a post read aloud over gameplay with the Reddit card and captions. Use when the user asks for a Reddit story, an AITA, TIFU, confession, revenge or relationship-drama story, or a storytime video over Minecraft or other gameplay.
---

# Reddit story

A narrator reads a Reddit-style post over gameplay: the post card opens the
video with its title, then the story plays with captions. The story is the
whole video, so the writing matters most.

Reddit stories are for paid plans. If Crealix answers that the plan doesn't
include them, say so plainly and offer a format that can tell the same story,
such as a faceless video or a text-message story. Never suggest upgrading.

## 1. Read the guide

Call `get_creation_guide('reddit_story', durationSec, language)`: the characters of
body for this length, the options, the cast (voices, captions, music, gameplay)
and what the user saved for their Reddit card in their brand.

## 2. Write the post (hybrid)

Send the post title as `title` and the body as `script`.

- The title is the hook and is read first: a question or a shocking statement
  that makes the viewer need the ending ("AITA for skipping my sister's wedding
  after she read my diary in her speech?").
- The body is first person and conversational, like a real post: short
  paragraphs, specific details (ages, places, what was said), no clichés.
- Open inside the conflict, not with background. Raise the stakes every few
  lines and keep the key reveal for late.
- End with a twist, an "UPDATE:" or a question to the reader that invites
  comments.
- Plain text: no markdown, hashtags or emojis. Stay within the guide's
  character budget.
- Invent the people. Don't retell a real person's private story without saying
  it is fiction.

Use crealix mode when the user wants Crealix to write it from an idea.

## 3. Cast it

Choose what suits this story, from the cast and the guide's options:
- A narrator voice that sounds like the person who wrote the post.
- `options.gameplayId`: the background clip that fits the story's energy and
  audience (`browse_catalog('gameplay')` to search).
- The card: `options.subreddit` and `options.displayName` (default: their brand),
  `options.theme`, and `options.cardMode` (the card only at the start, or all
  along).
- Captions and music from the cast; `options.narrationVolume` and
  `backgroundVolume` for the mix. `cover` for the thumbnail.

## 4. Propose, create, finish

`check_plan` until it is valid and fits the length, then one `validate_plan` with
two or three lines of why. On a yes in the chat, `create_video` with the
`proposalId`. Follow it with `get_status`; the card plays the draft.

Changes afterwards go through `edit_video` (the post, card, voice, captions,
gameplay, music). Changed words or voice leave the recording behind: say what
re-recording costs, then `rerecord_narration`. Render only when they ask.

Referenced files: 1 — file references are metadata, not package contents.

View saved version →

---
name: scene-by-scene-video
description: Design a video with Crealix scene by scene, choosing each scene's narration, length, image or clip, AI model (Veo, Kling, Seedance, Sora…), camera move and transition, with the user's own media too. Use when the user wants full control, a specific video model, their own images or clips, or an ad, a product demo or a trailer.
---

# Scene-by-scene video (from scratch)

No template in between: you design each scene and Crealix executes it, with
any image or video model, the user's own media, or both. Nothing is spent until
the scenes' media is generated.

## 1. Read the guide

Call `get_creation_guide('from_scratch', durationSec, language)`: the scene
fields, the suggested number of scenes and seconds per scene for this length,
the narration pace of the voice, and prices (voice and image per scene;
clips by model).

## 2. Design the scenes

For each scene:
- `text`: what the narrator says (and the captions show). Within the pace the
  guide gives for its duration. Leave it empty for a silent shot.
- `durationSec`: at least as long as its narration.
- `mediaPrompt`: what the image or clip shows, in English and concrete:
  subject, action, setting, how the light falls, framing. No text or logos in
  the picture, no style words (the visual style is added), no names (describe
  the person).
- `movementType` for a camera move on images, `transitionType` into the next
  scene.
- The user's own image or clip in a scene: it must be in Crealix first
  (`import_media_from_url`, or `upload_media`), then it goes on that scene.

Write it like the best short-form: the hook in scene 1, one idea per scene, a
payoff at the end. Describe light on surfaces (warm side light, pale dawn), not
lamps or beams, unless the scene really has the source.

## 3. Cast it

From the guide's cast, choose what suits this video: voice and delivery,
visual style (or none, to follow the prompts alone), captions and music, plus
`cover` for short-form. The models: Crealix's recommended ones unless the user
names one; `show_options('video_models')` only if they want to compare.

## 4. Propose and create

`check_plan` with the scenes until it is valid, then one `validate_plan` (the card
shows the scenes, the cast and the cost) with two or three lines of why. On a
yes, `create_project_from_scratch` with the same fields and the `proposalId`
(free), then `generate_scene_media` for scenes `all` with voice and image: the cost
the proposal showed.

## 5. Bring it to life

- Suggest which scenes deserve motion (the hook, the key moments), not all of
  them. `animate_scenes` first returns each clip's model, length, quality and
  price: tell the user all four, say which ones Crealix picked, and animate
  only after they agree, with its `confirmationId`.
- Add a hook overlay on scene 1 and a few text overlays where they help
  (`add_text_overlays`), and sound effects on real moments only
  (`add_sound_effects`). No ticking clocks unless asked.
- Fine-tune with `update_project` and `update_captions`; `undo_last_change`
  reverses an edit.
- Render only when they ask: the card's Render button, or `render_project`.

Referenced files: 1 — file references are metadata, not package contents.

View saved version →

---
name: split-screen
description: Make a split-screen video with Crealix, two clips stacked or side by side, such as the user's own clip over gameplay, with optional narration and captions. Use when the user wants a split screen, their clip or podcast over Minecraft or satisfying footage, or gameplay under a video they have.
---

# Split screen

Two clips play at once, stacked or side by side: usually the user's clip on
one half and gameplay on the other, which keeps viewers watching. Narration
with captions is optional. Without it, the video lasts as long as the longer
clip and costs nothing to make.

## 1. Get the clips

Each half is either a file in Crealix storage (`url`) or a gameplay clip
(`gameplayId` from `browse_catalog('gameplay')`).

The user's own clip must be in Crealix first:
- attached to the chat: `import_media_from_url` with `file`;
- a public link to the file: `import_media_from_url` with `url`;
- on their device: `upload_media` shows a card to pick it. Its Crealix URL comes
  back in their next message.

Don't ask for a public link when they can attach or upload the file.

## 2. Read the guide

Call `get_creation_guide('split', durationSec, language)`: the narration budget,
the options and the cast (voices, captions, music, gameplay).

## 3. Decide the narration

- Their clip already talks (a podcast, a vlog, a reaction): usually no
  narration. Leave `script` out and keep its sound on.
- A voice-over tells the story: write it yourself (hybrid) within the budget,
  spoken and conversational, with a hook first. Crealix voices and captions it.
- Crealix writes it from an idea (crealix mode) only when the user asks.

## 4. Set it up

- `options.first` (top or left) and `options.second` (bottom or right). Put the
  clip the viewer should follow on top. Mute the gameplay (`muted: true`) or
  keep it low (`volume`).
- `options.splitDirection` and `options.splitRatio` when one half should be
  bigger.
- With narration: a voice from the cast that suits it, captions and
  `options.captionPosition` where they don't cover a face, and music if it
  helps. `cover` for the thumbnail.

## 5. Propose, create, finish

`check_plan` until it is valid, one `validate_plan` with two or three lines of why,
then `create_video` with the `proposalId` on a yes in the chat. Follow it with
`get_status`.

Changes afterwards go through `edit_video` (the narration, either clip, the
split, captions, music). A changed narration or voice needs `rerecord_narration`.
Say the cost first. Render only when they ask.

Referenced files: 1 — file references are metadata, not package contents.

View saved version →

---
name: stock-footage-video
description: Make a narrated video with Crealix over real stock footage, a clip for every sentence, from a topic or the user's script. Use when the user wants real footage instead of AI images, for travel, finance, business, health, news-style explainers or motivation. Also swaps clips afterwards.
---

# Stock footage video

A narrator reads the script while real stock clips play under it, each one
matched to its sentence, with captions and music. Every sentence becomes a
footage search, so the writing decides what the viewer sees.

## 1. Read the guide

Call `get_creation_guide('stock', durationSec, language)`: the words budget for
this length, the cast (voices, captions, music) and the price. Stock footage is
included; the user pays for the narration and, later, the render.

## 2. Write for footage

- About 2.5 words per second (the guide gives the figure). Use hybrid mode and
  write it yourself. Use crealix mode only when the user asks Crealix to write it.
- Hook in the first sentence. No greetings.
- One idea per sentence, and each sentence describes something a camera could
  film: people doing things, places, objects, weather, cities, nature.
  "A trader stares at red numbers on six screens" finds footage; "the market
  is uncertain" does not.
- Keep abstract lines rare and next to concrete ones, so the footage still makes
  sense.
- Plain text, no headings or stage directions. The words are read as written.
- Facts, figures and claims: only what you know is true.

## 3. Cast it

Choose from the cast what suits this video: its topic, tone, audience and
platform.
- Voice and delivery (`voiceSettings` adapted from `voiceDelivery`).
- Captions and music under the voice.
- `cover` for short-form, and `voiceEffect` only when it serves the story.
- 9:16 for TikTok, Reels and Shorts; 16:9 for YouTube; 1:1 when asked.

## 4. Propose and create

`check_plan` until it is valid and fits the length, then one `validate_plan`, with
two or three lines on why your choices suit this video. On a yes in the chat,
`create_video` with the `proposalId`. A press on the card's Create button has
already created it.

## 5. Improve the footage

When it is ready (`get_status`), the card plays the draft. If a scene shows the
wrong thing:
1. `search_stock_media` with a concrete query for that line, at the video's shape.
2. `import_media_from_url` with the chosen clip's `videoUrl`.
3. `edit_video({ scenes })` to put the imported clip on that scene number.

`edit_video` also changes the title, captions, music and mix. The narrator stays
the one chosen at creation. Edits are free and `undo_last_change` reverses them.
Render only when they ask: the card's Render button, or `render_project`.

Referenced files: 1 — file references are metadata, not package contents.

View saved version →

---
name: talking-objects
description: Make a talking objects video with Crealix, where everyday objects with faces talk in a short comic scene, lip-synced. Use when the user asks for talking objects, food or products that talk, or a funny dialogue between things.
---

# Talking objects

Everyday objects come alive and talk to each other in a short comic scene. You
write who speaks and what they say; Crealix designs each object with a face,
gives it a voice and animates it lip-synced, one line per scene.

## 1. Read the guide

Call `get_creation_guide('talking_objects', durationSec, language)`: the exact
format and word budget per line, the allowed lengths, the moods and presets, and
the price. The objects speak with their own voices, so there is no narrator to
choose.

## 2. Write the dialogue (hybrid)

- One line per scene, written `OBJECT: "line"`. The object's name is what gets
  drawn, so name it plainly (TOASTER, COFFEE MUG, OLD SNEAKER).
- Each line stays under the guide's word cap, about 20 words. One joke per line.
- Two or three objects, each with a clear personality that shows in how it
  talks: the smug one, the anxious one, the one who has seen too much.
- Open with the funniest or most surprising line. End on a payoff or a
  comeback.
- The objects should belong together (a kitchen, a desk, a gym bag), so the
  scene reads at a glance.

Use crealix mode when the user wants Crealix to write it from an idea.

## 3. Choose the options

From the guide's catalogs, choose what suits this dialogue:
- `options.moodId`: the tone of the scene.
- `options.presetSlug` or `categoryAngle`: a ready-made angle when the idea
  matches one.
- `options.enableSfxLayer` for sound effects under the dialogue.
- Captions and music from the cast, `cover` for short-form.
- `options.qualityTier`: NORMAL unless the user wants more; say what it costs.

## 4. Propose, create, finish

`check_plan` until it is valid, one `validate_plan` with two or three lines of why,
then `create_video` with the `proposalId` on a yes in the chat. Follow it with
`get_status`.

Afterwards, `edit_video` changes the title, captions, music and mix. The scenes
themselves are reworked in the Crealix editor: share the editor link, never
open it for the user. Render only when they ask.

Referenced files: 1 — file references are metadata, not package contents.

View saved version →

---
name: text-message-story
description: Make a text-message story video with Crealix, a chat that unfolds bubble by bubble (iMessage, WhatsApp, Instagram or X DMs), each person with their own voice, over gameplay. Use when the user asks for a fake text conversation, a chat story, or texts between a couple, exes, parents or friends.
---

# Text-message story

A phone screen shows a conversation, bubble by bubble, each message read in its
sender's voice, over gameplay. The chat is the story: you write it as a plain
transcript, Crealix turns it into bubbles, casts the voices and adds the
delivery and sound effects.

## 1. Read the guide

Call `get_creation_guide('text_messages', durationSec, language)`: the characters
of messages for this length, the chat apps and themes, the cast (voices,
captions, music, gameplay) and the people saved in the user's brand.

## 2. Write the chat (hybrid)

Send the transcript as `script`, one message per line: `NAME: message`.

- Two to six people. The phone's owner is the one with the most messages.
- Write the way people text: short, lowercase, fast replies, the odd typo or
  "…". Several short messages beat one long one.
- The first message is the hook: something that makes the viewer need the
  next bubble ("who ate the cake i made for grandma").
- Build tension through the replies and land a twist or reveal in the last
  messages.
- A line on its own like `3 HOURS LATER` becomes a time skip. Use it to jump
  to the payoff.
- Stay within the guide's character budget.

Use crealix mode when the user wants Crealix to write it from an idea.

## 3. Cast it

Choose what suits this conversation, from the cast and the guide's options:
- `options.voices`: a voice for each person, by name, that fits who they are
  (age, gender, personality). Anyone not listed reads with the main voice.
- `options.skin`: the chat app, and `options.theme` (light or dark).
- `options.gameplayId`: the background that fits the story's energy.
- Captions and music from the cast, the mix (`narrationVolume`,
  `backgroundVolume`), and `cover` for the thumbnail.

## 4. Propose, create, finish

`check_plan` until it is valid and fits the length, then one `validate_plan`: the
card shows each person with their voice. Recommend it in two or three lines.
On a yes in the chat, `create_video` with the `proposalId`. Follow it with
`get_status`.

Changes afterwards go through `edit_video` (messages, people, voices, app,
gameplay, music): the ids are in `get_project`'s content. Changed messages or
voices need `rerecord_narration`, which re-records only those turns. Say the
cost first. Render only when they ask.

Referenced files: 1 — file references are metadata, not package contents.

View saved version →

---
name: tweet-video
description: Make a tweet video with Crealix, an X (Twitter) thread shown as cards, the main tweet and each reply read in its own voice, over gameplay. Use when the user asks for a tweet video, a viral thread, a hot take with replies, or an X post turned into a video.
---

# Tweet video

The main tweet appears as an X card and is read aloud, then the replies come in
one by one, each with its own voice, over gameplay. The thread is the video:
a strong post and replies that argue, joke or add the twist.

## 1. Read the guide

Call `get_creation_guide('tweets', durationSec, language)`: the characters for
this length, the most tweets a thread holds, the options, the cast (voices,
captions, music, gameplay) and the X profile saved in the user's brand.

## 2. Write the thread (hybrid)

Send it as `script`, blocks separated by a blank line:
- The first block is the main tweet, posted by the account in `options.account`
  (default: the user's brand).
- Every reply starts with its author: `Jane Doe @jane: reply` or `@jane: reply`.

What makes it work:
- The main tweet is a hook on its own: a hot take, a confession, a relatable
  disaster.
- Replies escalate: agree, argue, one-up, and one of them flips it. Keep each
  short, like a real reply.
- End on the funniest or most surprising reply.
- Invent the people and their handles. Never make a real person or brand
  appear to post something they didn't.

Use crealix mode when the user wants Crealix to write it.

## 3. Cast it

Choose what suits this thread, from the cast and the guide's options:
- `options.voices`: a voice for each person, by @handle or name, that fits how
  they write. Anyone not listed reads with the main voice.
- `options.account`: who posts the main tweet, when it shouldn't be the brand.
- `options.displayMode` (the whole thread or one tweet at a time), `options.theme`
  and `options.cardOpacity`.
- `options.gameplayId`, captions and music from the cast, the mix and `cover`.

## 4. Propose, create, finish

`check_plan` until it is valid and fits the length, then one `validate_plan` (the
card shows each person with their voice) with two or three lines of why. On a
yes in the chat, `create_video` with the `proposalId`. Follow it with `get_status`.

Changes afterwards go through `edit_video` (edit, add or remove tweets, each
person's voice, the theme, gameplay and music): tweet ids are in `get_project`'s
content. Changed words or voices need `rerecord_narration`, which re-records only
those tweets. Say the cost first. Render only when they ask.

Referenced files: 1 — file references are metadata, not package contents.

View saved version →

---
name: video-cover
description: Design the cover (thumbnail) of a Crealix video, a short headline in a cover style over a striking frame, or over an AI image made for it. Use when the user asks for a thumbnail, a cover, a title on the first frame, or "make an image for my thumbnail".
---

# Video cover

The cover is baked into the first frame of the rendered MP4, the one TikTok,
Reels and Shorts show before anyone presses play. It is a few words in a cover
style over a frozen moment of the video, or over an image. Setting it is free.

## 1. Know the video

`get_project` for its title, type, aspect ratio and length. Styles and how each
looks are in `get_creation_guide(type).cast.coverStyles`.

## 2. Write the headline

- Three to six words that make someone stop scrolling. Not the full title.
  A promise, a number, a shock or a question ("HE LIED FOR 40 YEARS").
- Say it in the video's language. The style's letter case applies.
- No headline at all when the image already says everything.

## 3. Choose what is behind it

- **A moment of the video** (`frameSec`): the most striking frame, a face, a
  reveal, the peak of the action. Not a transition or a blank frame.
- **An AI image made for the cover**:
  1. `generate_images` at the video's aspect ratio, with a prompt for one bold,
     readable subject and empty space where the headline will sit. It costs
     credits: say the price.
  2. Wait until it is done (`get_status`).
  3. Use its URL as `imageUrl`.
- **The user's own image**: bring it into Crealix (`import_media_from_url`, or
  `upload_media`) and use that URL.

## 4. Set it

`set_cover({ projectId, cover: { title, style, position, frameSec or imageUrl } })`.
Choose the style and position that suit this video and keep the headline off
faces and key details. `fontSize` goes up for two or three big words.

Say in one line what the cover says and shows. `undo_last_change` reverts it;
`remove: true` takes it off.

## 5. Render

The cover goes into the next render. A video that was already rendered needs
rendering again to show it: offer it, and render only when they say so.

New videos can carry their cover from the start: pass `cover` in the proposal
(`validate_plan` and `create_video`).

Referenced files: 1 — file references are metadata, not package contents.