Recipes

Some videos you make once. Others you make again and again: the weekly product update, the release demo, the social cut of every launch. Those shouldn’t start from zero each time.

A recipe is how you keep the method. It’s a reference pack — written instructions, a worked example of the structure, and the ingredients (fonts, logos, components, sound) — that a connected agent reads before it builds. Point an agent at a recipe, hand it the new footage or data, and you get the next one in the same style.

Find them under Recipes in the sidebar, split into Community and My Recipes.

The three parts of a recipe

Open a recipe and you’re editing three things, on three tabs.

Instructions

Markdown the agent reads before it builds — and it outranks Mixture’s own default guides. This is where your method goes: how the piece is paced, what the type does, which motion is house style and which is banned, how data comes in, what the workflow is.

Write it as direction to a competent editor who’s never seen your brand:

Open on a full-bleed hold of the product for 1.2s before any type. Headlines are Söhne Semibold, 96px, always bottom-left in the safe area. Never centre-align body copy. Cuts land on the beat; nothing crossfades.

Specific and opinionated beats comprehensive. Every line is a rule the agent will actually follow.

Structure

A recipe’s structure is a live link to a project. You don’t export a frozen copy — you point the recipe at a real project, and its document becomes the worked example. Edit that project in the editor and the recipe follows automatically. Improve the master, and every future video made from the recipe improves with it.

The one transformation on the way in: footage becomes slots. Clips that were specific to the source project are rewritten to placeholder://footage/<slot> — inert references that the agent fills with the new project’s recording. The structure, timing and treatment survive; last month’s screen capture doesn’t come along.

Library assets are left alone. A logo or a font that lives at workspace level keeps its real reference, because it resolves from any project in the workspace — which is exactly what you want a brand asset to do.

Assets & components

The ingredients. Link the fonts, logos, sound beds, LUTs and saved components the recipe depends on, and they travel with it. Anything the example structure already uses is flagged as such, so you can see what’s load-bearing versus what you added for completeness.

This is what makes a recipe portable rather than a document full of broken references.

Making one

The fastest route is from a video you’ve already made and liked. Create a recipe from that project and its document becomes the structure immediately; then write the instructions while the decisions are still fresh in your head, and link the ingredients it leans on.

Give it a name and a one-line description — the description is what shows in the gallery and what an agent sees when it lists available recipes, so make it say what the recipe is for rather than what it’s called.

Using one

Two ways in:

From the app — apply a recipe to a project. If the project has no document yet, the scaffold seeds it, so you open the editor on the structure rather than a blank canvas.
From an agent — the recipe’s instructions become required reading, its linked assets become usable references, and the example document is there to study. The ask collapses to one line: “Make this week’s update using our Product Update recipe — here’s the recording.”

An agent can also read a recipe without applying it, to follow the pattern while editing an existing video.

Recipes start private to your workspace. When one is good enough to share, send it for review.

Private — only your workspace can see it.
In review — sharing sends a snapshot to our team. You can keep editing in the meantime; the reviewer sees what you submitted, not your later changes.
Published — it appears in everyone’s Community gallery, ingredients included.

After publishing, later edits stay private in your workspace until you Resubmit, which sends a fresh snapshot for review. Unpublish pulls it back out of the community at any time, and anyone who was relying on it loses access to the linked ingredients along with it.

If a submission isn’t approved, you’ll see the reviewer’s note on the recipe and can revise and resubmit.

Recipes vs components

Both are reuse, at different scales.

A component is a piece of design — a lower third, a stat card, an end card — that you drop into a video and stays linked to its source.
A recipe is a whole method: the structure, the pacing, the rules, and the components themselves as ingredients.

Components keep individual elements consistent. Recipes keep entire videos consistent.