Communitygithub.com

unrushed

Video and animation skill. Motion direction for videos and animated pieces that must not look AI-generated. Use it to brief, style, storyboard, export or critique motion graphics, explainer and promo videos, animated titles, kinetic typography, transitions, particle and morph sequences, and prompts for video tools such as ChatCut, Remotion, After Effects or Claude Code. Use it as well when someone says a video looks generic, cheap or "made with AI", wants better animations or transitions, shares a site or clip whose motio

Was ist unrushed?

unrushed is a Claude Code agent skill that video and animation skill. Motion direction for videos and animated pieces that must not look AI-generated. Use it to brief, style, storyboard, export or critique motion graphics, explainer and promo videos, animated titles, kinetic typography, transitions, particle and morph sequences, and prompts for video tools such as ChatCut, Remotion, After Effects or Claude Code. Use it as well when someone says a video looks generic, cheap or "made with AI", wants better animations or transitions, shares a site or clip whose motio.

Funktioniert mit✓Claude Code~Codex CLI✓Cursor
npx skills add https://github.com/amladinon94-source/unrushed/tree/HEAD

In Ihrer bevorzugten KI fragen

Öffnet einen neuen Chat, in dem dieser Agent-Skill bereits geladen ist.

Dokumentation

Was macht unrushed?

Generic motion comes from defaults: every element fades up the same 30 px in the same half second, scenes dip to black, the palette is neon on navy, and nothing moves for a reason. Unrushed replaces adjectives with decisions. Every movement gets a purpose, a duration, a curve, a distance and a place in the order of things. "Smooth and modern" is not a direction; "enters over 700 ms on an expo-out curve, 16 px, 150 ms after the year" is.

The name is the stance: calm, deliberate motion that gives the viewer time to read and feel. Unrushed does not mean slow. A fast piece can be unrushed if every beat is chosen.

How to work with it

Unrushed is a set of commands around one loop: context → create → review → steer. The person directs; you execute and advise. Run the command they ask for. If they ask for something without naming a command, pick the one that fits and say which one you used. Suggest the next step at the end of each command, but do not run a chain of commands on your own: the human judgment between steps is the point.

Reply in the person's language. Command names stay in English.

Where the files are. Commands read files in references/. If that folder is not next to this file, read "References" at the end of this file before opening anything: it says where else to find them.

Project files

Commands share three files in the project folder. Read whichever exist before any command.

FileWritten byHolds
VIDEO.mdbriefWhat the piece is: topic, message, audience, format, sound, through-line, facts to verify
STYLE.mdstyleHow it looks and moves: material, palette, type, dials, signature move, forbidden list
STORYBOARD.mdstoryboardScene by scene: exact text, figure, motion, timing, transition

Templates are in assets/. If a command needs a file that does not exist, say so and offer to run the command that creates it, rather than inventing its contents.

Dials

Four settings shape every decision. Defaults suit most explainers; the person can change them at any time ("energy 7").

DialRangeDefaultWhat it changes
energy1–104Durations, distances, how much overshoot is allowed, how many things may move at once
density1–103Elements per frame, words per scene, how much empty space surrounds the protagonist
variance1–105How much scenes differ from one another in layout, rhythm and structure
materiala wordchosen in styleThe physical behaviour motion borrows: ink, paper, glass, cloth, fluid, particles, metal, light

How energy maps to numbers, as a starting point:

energyText entranceScene transitionOvershootMoving at once
1–3800–1200 ms1400–2000 msnone1
4–6500–900 ms900–1500 mssmall elements only1–2
7–8300–600 ms500–900 msallowed on accents2–3
9–10150–400 ms250–600 msexpressivemany, but choreographed

variance guards against the most common failure of a long piece: every scene built the same way. Above 4, vary at least one of composition, rhythm or entrance pattern between neighbouring scenes.

material matters more than it looks. Across dozens of reference pieces, what made motion feel premium was rarely the technique; it was light and material: motion blur, self-shadowing, refraction, grain. Choose the material first and let it decide how things accelerate, settle and overlap.

Commands

GroupCommandDoesReadsWrites
ContextbriefCaptures what the piece is and its one visual idea—VIDEO.md
ContextstyleDefines the visual and motion systemVIDEO.mdSTYLE.md
CreatestoryboardBreaks the piece into timed scenesVIDEO.md, STYLE.mdSTORYBOARD.md
Createrecipe <reference>Turns a site, clip or screenshot into reusable motion values—a recipe in the reply
Deliverexport <target>Compiles everything into a prompt or spec for one toolall three filesthe deliverable
ReviewcritiqueScores frames or a video and lists what to fixSTYLE.md if it existsa report in the reply

brief

Read references/narrative.md first. Ask only what you cannot infer from the conversation or files, and at most five questions at once:

  1. Topic, the goal (explain, sell, launch, teach, celebrate) and the one sentence the viewer should leave with.
  2. Audience: who they are, what they already know or believe, and what they should feel or do afterwards.
  3. Platform, aspect ratio, duration and sound. A silent piece carries its whole narrative in on-screen text and motion beats, which changes the timing rules.
  4. Facts the piece states (dates, names, figures, product claims). List them; each needs a source or is marked [verify]. For a product, ask whether you can see the product itself, its code or its interface.
  5. Anything already decided: brand, references, things to avoid.

Then propose, and let the person choose or correct:

  • The spine. Hook, promise, proof, payoff and ask, one line each, and the structure that fits the type of piece. The hook must work visually in the first second.
  • The through-line. The single visual idea that carries the whole piece, and the most important decision in the brief. Propose two or three options and recommend one. A piece about the history of AI made of nine unrelated effects reads as a demo reel; the same piece where one set of particles travels from a neuron to a human profile reads as a story. A good through-line is a transformation that means something.
  • The beat map. Sections with their tempo and beat lengths, and where the payoff lands on the tension curve.

Write VIDEO.md from the template.

style

Read references/principles.md, references/ai-tells.md and the index of references/techniques.md first.

Propose before deciding. Offer two or three directions and let the person choose; never pick a look silently. Directions must differ in material and ground, not only in colour: three palettes of the same idea are one direction. Do not reuse the look of earlier projects (earlier STYLE.md files, earlier pieces in the conversation) unless the person asks for it. For each direction give:

  • a name and one sentence on how it feels;
  • material, ground, palette, type, and light and finish;
  • the signature move and the library techniques it draws on;
  • a styleframe, one key frame rendered as a still, whenever you can render one, because people choose looks by seeing them.

Recommend one and say why it serves the through-line. Once the person chooses, complete it:

  1. Material. Choose it before colour. It sets the motion personality: ink settles, glass is precise, fluid overlaps, cloth lags behind its driver.
  2. Palette. A ground, an ink and at most one accent with a stated job ("the accent marks the present day"). Give hex values and roles.
  3. Type. Two families at most, each with a role and sizes for the target resolution. Avoid the defaults listed in ai-tells.md unless the person asks for them.
  4. Light and finish. What makes it physical: grain that moves (renewed every two frames, never a static overlay), motion blur on fast moves, shadow and depth, refraction or bloom only when the material has them.
  5. Dials. Set energy, density and variance, and say why.
  6. Signature move. One recurring motion that identifies the piece, such as particles that reassemble or a mask that always opens from the bottom. Name the entry in references/techniques.md it starts from.
  7. Forbidden list. The generic choices this piece in particular is tempted by.
  8. Interface system, when the piece shows a product or a tool: which components, icons and fonts the interface uses, and their licences. See references/visual-explanation.md.

Pieces that show several styles or techniques, such as a showcase or a demo of what a tool can do: define a frame system that stays constant (type, text zone, the through-line element), and give each style its own world, with its own ground, palette and light. If every style shares the same paper and ink, the viewer sees one style with different shapes.

Write STYLE.md. Include a ready-to-paste style block for the likely target (for ChatCut, the Design Style fields; see references/targets/).

storyboard

Build the storyboard from the spine and beat map in VIDEO.md; if they are missing, offer to run brief first. Build a table with one row per scene: start time, duration, exact on-screen text, the figure or visual, the technique, what moves (with curve, duration and distance), and the transition into the next scene.

  • Choose each scene's technique from the line's meaning. Read the index by meaning in references/techniques.md, pick the entry whose image enacts the line, and adapt its key parameters to STYLE.md. Name the entry in the table so export can carry its build notes. Keep the signature move as the thread; techniques serve it, not the other way round.
  • Give each beat a device from references/visual-explanation.md: the way the idea becomes visible (interface simulation, ghosts, same space with two behaviours, a camera push, one canvas…). Neighbouring beats use different devices or compositions. Run the slide test on every scene: if a paused frame reads as a slide, rework it.
  • Choose each transition from references/transitions.md by the relation between the two beats, and write the relation next to it. Never the same type twice in a row; at least four kinds in a piece over 60 s; the biggest one leads into the payoff.
  • When the piece shows a product or a tool, simulate its interface with real components: the product's own when you can see it, otherwise the design system it is built on. Never invent controls.
  • One protagonist at a time. Text enters when the main movement is about 60% complete, never during it.
  • Check reading time for every line of text with the rule in principles.md. For silent pieces, flag any line held for less than its reading time.
  • Use only facts from VIDEO.md. Anything not there is marked [verify].
  • Make sure the image and the text say the same thing. If the line says "funding freezes", the figure should freeze, not pile up.

Before finishing, review the storyboard as a whole and fix what fails, saying what you changed:

  • Spine. Each beat is tagged hook, promise, proof, payoff or ask, and the payoff is the strongest image at roughly 70–85% of the piece.
  • Rhythm. At least three different beat lengths; the beat map in VIDEO.md is followed. With Python available, python scripts/detect.py --storyboard STORYBOARD.md checks scene lengths and repeated transitions.
  • Transitions. No type twice in a row, at least four kinds over 60 s, the biggest one into the payoff.
  • Slide test. No scene reads as a slide when paused; neighbouring beats use different devices.
  • Variance. If scenes share the same structure, apply variance.

recipe <reference>

Turn a reference into values someone can reuse. Read references/principles.md.

  1. Inspect. With a browser, read computed transitions and keyframes, look for libraries (GSAP, Three.js, Lenis, OGL), and read the names and values of any on-page controls: authors often expose the exact parameters. With only a clip or screenshot, estimate and say so.
  2. Classify. Give the family (particles, physics and cloth, fluids, glass and lenses, organic forms, pixel and ASCII, generative patterns, 3D and waves, scroll and transitions) and the mental model: simulation, function of time, function of distance, per-pixel shader, or discrete rules.
  3. Extract values. Durations, curves, distances, counts and parameters.
  4. Say what it communicates and when it would be the wrong choice.
  5. Map it to targets. How to reproduce it in each tool, from "paste these values into ChatCut" to "needs Blender".
  6. Critical note. Cliché risk, licence, and anything you could not verify.

Write the result in the same format as the entries in references/techniques.md, with a slug, source and credit, what it is, what it communicates, key parameters, build routes, difficulty and critical note, so it can join the library. If the skill folder is editable, offer to add the entry and to list it in the index by meaning.

Extract values and intent; never copy a reference's code or assets into the person's project.

export <target>

Read references/targets/<target>.md (chatcut, remotion or generic; use generic for any other tool and adapt it). Compile VIDEO.md, STYLE.md and STORYBOARD.md into what the tool needs. The target file only translates: it never changes the creative decisions made in the project files.

If you are running inside the target tool itself, as with ChatCut's agent, or have its tools available, build directly instead of handing the person something to paste. The target file says how.

Every export:

  • states motion as numbers (ms, curve values, px, counts) next to the intent behind them, because tools follow numbers more reliably than adjectives, and generalise better when they know why;
  • for each technique named in the storyboard, carries its key parameters and build notes from references/techniques.md, so the tool knows how to build it and not only what it should look like;
  • includes the forbidden list from STYLE.md;
  • asks the tool to pilot the first scene and the closing before building the rest, and to report what it could not do;
  • ends with the review checklist from critique, so the tool checks its own frames.

critique

Read references/ai-tells.md, references/narrative.md, references/transitions.md, and STYLE.md if it exists. critique works on a finished video, on frames, or on a plan (STORYBOARD.md) before anything is built; critiquing the plan is the cheapest moment to fix rhythm and transitions.

If you have a video file and ffmpeg, run python scripts/detect.py <video> --storyboard STORYBOARD.md first: it reports dips to black, stretches where nothing moves anywhere in the frame, hard cuts, and the planned rhythm and repeated transitions. Then look at frames, sampled densely around every transition.

Score each criterion from 1 to 5 with one line of evidence:

CriterionQuestion
StoryDoes the hook work in the first second? Is the promise kept by a payoff that is the strongest image? Is the ask clear?
RhythmDo beat lengths vary with purpose: building, then holding after a reveal? Or does it tick along evenly?
ExplanationIs each idea shown happening, with a device, rather than written beside a demo? Does any paused frame read as a slide?
TransitionsDoes each transition say the relation between beats? How many kinds, and are any repeated back to back?
ConceptIs the figure understood without reading the text?
HierarchyDoes the eye know where to go first, second, third?
LegibilityCan every line be read in the time it is on screen?
ChoreographyOne protagonist at a time, overlap instead of dead frames?
TimingDo entrances decelerate, exits run faster, holds feel intended?
Material and lightDoes the piece have texture, depth, a physical feel? Does each style have its own world?
DistinctivenessHow many AI tells are present?
ConsistencyDoes it follow STYLE.md?

Then list the AI tells you found, and the three fixes with the most impact. Write each fix as an instruction ready to paste into the tool. When a scene looks generic because of its technique, device or transition, suggest an alternative from references/techniques.md, references/visual-explanation.md or references/transitions.md that says the same thing better. Be specific about what stills cannot show: motion, fluidity and rhythm need the video.

References

Read only what the current command needs.

The reference files live in a references/ folder next to this file. Some hosts install a skill as this single file: Claude accounts, and agents that load those skills, such as ChatCut's. If the folder is missing, read the same files from the public repository, replacing the path below:

https://raw.githubusercontent.com/amladinon94-source/unrushed/main/<path>

If you cannot reach them either, work from the embedded essentials in the single-file edition, if this is that edition, and say that the full references were not available.

FileRead for
references/narrative.mdHook, promise, proof, payoff and ask; structures by type of piece; beats, rhythm and the beat map. brief, storyboard, critique
references/visual-explanation.mdDevices that make an idea visible, the slide test, interface simulation with real design systems, cursor choreography. style, storyboard, export, critique
references/transitions.mdTransitions chosen by the relation between beats, a catalogue with durations and related techniques, eye trace and other ways to hide the seam. storyboard, export, critique
references/principles.mdTiming, curves, distances, choreography, type timing, material behaviour. style, storyboard, recipe, export, critique
references/ai-tells.mdWhat makes motion and video read as AI-generated, and what to do instead. style, export, critique
references/techniques.md38 techniques from real reference pieces, indexed by meaning and by family, with key parameters and build routes. style, storyboard, recipe, export, critique
references/targets/chatcut.mdExporting to ChatCut
references/targets/remotion.mdExporting to Remotion, through Claude Code or any coding agent
references/targets/generic.mdAny other tool, or a spec for a human animator
scripts/detect.pyAutomatic checks on an exported video, and on the rhythm and transitions of a STORYBOARD.md

Verwandte Skills