clearframe-inspiration
Skill1 starsChanged 24 days agoMITView on GitHub
Turn a video idea into a few distinct visual concepts and find the ClearFrame library pieces that build the chosen one (looks, objects, sketches, playbooks, mechanisms, examples). Use when someone asks for ideas, options or "what could this look like", or when choosing pictures for a new film from the library. Not for acting on notes about an existing cut (clearframe-review).
In this repository22 other files it gives its agents.
- AGENTS.mdAGENTS.md
- CLAUDE.mdCLAUDE.md
- clearframe-blocksSkill
- clearframe-canvasSkill
- clearframe-datavizSkill
- clearframe-directionSkill
- clearframe-engineSkill
- clearframe-explainSkill
- clearframe-integritySkill
- clearframe-librarySkill
- clearframe-motionSkill
- clearframe-reviewSkill
- clearframe-sceneSkill
- clearframe-scriptSkill
- clearframeSkill
- clearframe-workplaceSkill
- gemini-imageSkill
- gemini-omniSkill
- gemini-ttsSkill
- lyria-musicSkill
- runway-videoSkill
- veo-videoSkill
The file
We split this skill into the rules it gives an agent
3 rules. About 0 are common, 2 are distinctive, and 1 is very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈2
Distinctive · estimate
This author's own choices. Worth a look.
1
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 45
When the person asks for options, or the brief leaves the picture open, offer two or three concepts.
- Distinctive: line 79
Recognisable pieces: Keep them recognisable: the brief's own objects (its services, its product) make a borrowed composition feel made for …
- Very specific: line 84
Shape: Check a vertical frame (--vertical scaffold) when the film is for phones.
≈ “Common” is an estimate: at least 1 in 5 of the 350,495 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
From an idea to pictures
The library holds blocks, sketches, playbooks, palettes, type voices, cast objects in four looks, stage mechanisms and worked examples, each kept because it meets the bar in packages/engine/src/library/README.md. Don't tour it. Search it with the brief, offer a few distinct ideas, then open only the pieces the chosen idea needs.
1. Read the brief for three things
- The idea: what is true, or what changes.
- The audience: who watches, and what they already know.
- The feeling: calm, playful, urgent, premium, warm.
Infer them from the material and the wording. Ask only when the subject itself is missing.
2. Search in plain words
pnpm cf find "remind staff their FSA money expires in December" # studio: clearframe_catalog topic find, query
pnpm cf find "order delivery" --kind cast-shape,cast-look,example
pnpm cf find --id cast-move:travel # studio: topic item, name KIND:NAMEfind returns a short, mixed shortlist. Each line says what the entry is and when it fits. Read the "when" before choosing.
- Narrow per concept. Once a concept is in mind, search again with its own words and
--kind. - Exact authoring.
--idprints the props, fields and an example that compiles; copy it and adapt it. For a sketch, the example lists its text slots (sketchText) and named moments (sketchSay). Fill the slots with the brief's own words and land each moment on the narration word that names it. - Browse.
docs/library-index.mdlists everything when a search misses. - Overrides. A project's or shared library's own entries take part in search.
| Kind | Gives you |
example | A finished, curated film to copy from (a README and storyboards) |
playbook, direction | A whole arc to start from (new DIR --playbook, --direction) |
treatment, palette, type | The look and the voice: colours, motion, type |
sketch | A drawn starting picture for one scene (canvas sketch) |
cast-shape, cast-look, cast-move | Objects that persist across cuts, drawn in a look and moved on spoken words |
mechanism, stage-element | Systems, code, worlds the camera travels, a colour handoff between scenes |
block | One kind of scene: a figure, a quote, a chart, kinetic words |
3. Offer distinct concepts, then decide
When the person asks for options, or the brief leaves the picture open, offer two or three concepts. Make them differ in the picture's idea, not its palette. Ways in:
- A metaphor: the order is a parcel on a journey.
- A place: one lit window in a sleeping city.
- A mechanism: packets moving through the real system.
- The words: kinetic type on the voice.
- The numbers: one figure, sourced, landing on a word.
For each concept, give:
- one line on what we would see;
- one line on why it suits this audience and feeling, in everyday words ("feels like a notebook sketch, so new hires relax");
- the two to four library entries that build it.
Then recommend one and carry on. By default the agent decides, and the person can choose another. Don't quiz them. One strong concept is enough when the brief is clear; there is no quota.
Choose a look for the audience and the rest of the film, not for variety. Keep to the project's rules: every displayed number is sourced, there are no sample figures as evidence, and there is no text in generated images.
4. Adapt it to the brief
What you can change, from lightest to deepest:
| Change | How | Example |
| The words | sketchText fills a sketch's placeholder type. Cast objects take label, and blocks take their props. | {"FIRST": "Stale logs"} |
| When things happen | sketchSay lands a sketch's named moments on narration words. Cast moves and canvas elements take say. | {"ALL": "Lights"} |
| The look | theme (palette), type, the cast look, and the stage material (dither, chrome…) on a shape or a ground. | "theme": "noir" |
| What is drawn | Copy the sketch's elements and edit them: other icons, fewer cards, other positions. In the studio, clearframe_catalog topic sketch (name, sketchText, sketchSay) returns the filled elements for the film's shape. In a build script, sketch(name, preset, {text, say}) from packages/engine/src/film/sketches.mts does the same. By hand, pnpm cf sketch NAME [--vertical] prints them. Put the result in props.elements (without props.sketch). | sketch shortcut |
| How something behaves | The graph, accumulate, estimate and field props take a formula or a seed, not elements: change the formula, the domain, the labels and the cue words (find --id mechanism:graph, clearframe-explain). They are never data. | examples/settling |
| Detail, then the whole | place: [x, y] draws each beat's picture as a panel of one world; the last beat's view takes them all in (find --id mechanism:board). It does not clip. | find --id mechanism:board |
| A new reusable picture | A sketch module, or a JSON sketch in the project's library/sketches/, so other films can use it by name. | packages/engine/src/library/README.md |
- Start light. Change words and cues first; copy elements only when the picture itself must change, such as a different number of things, different objects, or a different layout.
- Shapes. A copied drawing is laid out for one frame shape, so copy it once per shape.
- Recognisable pieces. Keep them recognisable: the brief's own objects (its services, its product) make a borrowed composition feel made for it.
5. Preview before building it all
- One beat. Paste the item's example into a beat, then
still DIR --at S --draftorsheet DIR --draft. - Shape. Check a vertical frame (
--verticalscaffold) when the film is for phones. - Palettes.
looks DIR --beat IDcompares one scene across palettes. - First look. The first full look is still a rough cut (
draft DIR --rough); detailed drawing comes after notes. - Phone size.
qa DIRwrites a 360 pxphone.png.
Worked calibration (one idea four ways, and different ideas with different choices): references/concepts.md. Read it when unsure how far apart concepts should be.
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

