Global-AI-Group-Inc/content-generation-skills / skills/mira-after-effects
mira-after-effects
VerifiedBuild motion pieces inside the user's own After Effects through the Mira MCP: read the project, mark the beat of the music, animate with the Mira Motion Kit (kinetic type, camera depth, velocity-matched transitions, expressions, grade) or ExtendScript, add plates, overlays, templates and sound, check contact sheets, render on the user's machine. Use it when the user says "build this in After Effects", "собери ролик в афтере", "промо в After Effects", "make a motion reel", "add grain and a LUT", or when adobe_status reports a connected After Effects. Requires the Mira for Adobe panel with the bridge switched on. NOT for generating clips (mira-generate) or Blender scenes (mira-blender-scene).
| File | Kind | Size |
|---|---|---|
| SKILL.md | skill md | 9.5 KB |
| references/bank-schema.md | markdown | 2.9 KB |
| references/depth.md | markdown | 4.5 KB |
| references/doctrine.md | markdown | 5.2 KB |
| references/motion-kit.md | markdown | 16.5 KB |
| references/recipes.md | markdown | 7.1 KB |
| references/workflow.md | markdown | 5.3 KB |
references/workflow.md
View on GitHub# Workflow: from a brief to a rendered motion piece
1. **Look first.** `adobe_status` (host, version, bridge on, `busy`), `adobe_get_project` and
`adobe_command list_layers` (what is open, the active comp, its layers). Never build into a
project the user is editing without saying so; offer a new composition.
2. **Reference and brand.** Ask for one or two reference videos and run `adobe_reference` on each
(a file, an https link, or a layer; `makeRef: true` when the user wants it beside the work):
keep its `avg_shot`, `cuts_per_10s`, palette and the sheet of shots, and name what to copy — the
pace, the type (weight, case, size, how it enters), the transitions, the palette. Take the brand:
the `brand` recipe returns what the user saved in the panel (colours, two typefaces, logo); ask
for the rest (product screenshots). Without these the piece defaults to centred text on a
gradient with fades.
3. **Read what is available.** `list_elements` (backgrounds, overlays, transitions, LUT presets,
sounds, templates with placeholders, fonts) and, if `$AE_LIBRARY/bank/BANK.md` exists, the bank.
Look at the previews of what you intend to use. Never invent ids or paths.
4. **The beat.** Put the track in the composition and call `adobe_beat_markers` on it (mode
`downbeats`, or `every` with 2 for a denser grid). Keep `grid_offset`, `beat_seconds`, the drops
and the sections: every scene boundary, cut, sound hit and type entrance is a grid value. If the
BPM is off by a half, double or triplet feel, run it again with `bpmHint`.
5. **Three storyboards.** Write three different directions as tables — Frame / Beat / On screen /
Why — each true to the reference and the brand. The user picks one; do not build before that.
6. **Stills per scene.** Build every scene as a still (layers placed, type set, no animation yet)
and show `adobe_contact_sheet` at one moment per scene. Fix the storyboard here: it costs seconds.
When a scene must match a design, a screenshot or a still, measure it, do not eyeball it:
`adobe_measure_reference` with `size` first, then `swatch` on flat areas, `gradient` along fills,
`radius` on rounded boxes, `fontsize` on each line of type and `crop` where an edge is unclear.
Scale every position, radius and size by composition width / reference width. The reference is
a measuring source, never an asset: do not cut pieces out of it, rebuild them as layers. Then
`adobe_audit_frame` with the same reference at the still's time: fix the numbered worst cells
(their box is in frame pixels, with the reference colour beside yours) and audit again until it
passes. The audit sees colour and layout only; read the text on its image yourself.
7. **Animate scene by scene.** Library elements go in with `adobe_place_element` (templates with
`texts`, `controls` and `media`; a luma wipe at the cut with the incoming layer starting a little
before it; a whoosh 0.3-0.5 s before a cut, a riser 1-2 s before a drop). Motion comes from the
Kit (`adobe_apply_recipe`, or `MK.*` inside a script): `text_animate` for type, `parallax` and
one `camera` move for depth, `transition` on the cuts, `keys` with named eases, `punch` on the
bars. Structural steps go through `adobe_command` (`set_parent`, `precompose`, `add_marker`);
whole scenes through `adobe_execute_script` with `MK.scene`. Plates first, then the subject,
then overlays, then the grade.
8. **Check.** After every scene: `adobe_contact_sheet` at its key times (a transition at cut-0.2 /
cut / cut+0.2) and the `check` recipe with the target `platform` (text out of frame, text on
text, text under the platform's UI, and motion that reads as robotic: nothing moving, linear
keys, entrances on one frame, a cascade that drags, fast moves without blur). Fix before moving on.
9. **Render.** Before it, `ease_repair` once over the main composition (only keys nobody shaped
change; it reports how many it eased and kept), `safe_zone` for the platform while you check (a
guide layer, never rendered) and `check` with the same `platform`. Then `adobe_render` with the platform `preset` (reels, tiktok, shorts, youtube, master)
and `upload: true` when the file should land in the Mira library; poll `adobe_render_status`
with `waitSeconds`. A saved project renders in the background (the user keeps working); unsaved
changes render inside After Effects, which is busy until it finishes. Loudness comes from the
layer levels: the music around -14 LUFS integrated, voice above it.
10. **Director's notes.** Apply the user's notes as named changes, not as "make it better":
| Note | Change |
|---|---|
| "slow every zoom to 0.7x" | stretch the scale keys of every zoom by 1/0.7, keep their start |
| "hard cut here" | remove the transition at that marker, cut on the grid value |
| "hold it" / "hold N frames" | move the next scene's in-point by N frames, re-snap to the next beat |
| "push in on the button" | `camera` `push` over one bar, or scale 100 → 110-115 % toward the button's centre |
| "whip to the next shot" | `transition` style `whip` on the cut, `dur` 0.2-0.3 s |
| "match cut" | align the shape or motion of the outgoing and incoming shot on the cut frame |
| "punchier" | shorter entrances (0.25-0.35 s), stronger ease out, one more cut per bar |
| "calmer" | fewer cuts (one per bar or two), longer holds, gentle ease, no shake |
Related skills
| Skill | Stars | Updated | Works with | Status | Install |
|---|---|---|---|---|---|
| reverse-engineer-anythingmorluto/reaReverse engineer native, managed, Electron/JavaScript, packaged, firmware, and browser targets with REA, and build agent environments (AgentEnv bundles) of web applications from a live instance or a capture, and of Linux desktop apps with a task from a request. Use shipped-artifact or requested runtime evidence to explain features, compare versions, decompile code, or guide a reconstruction. Skip REA for ordinary source-repository architecture analysis. | Stars: 472k | Updated | Claude CodeCodex | Verified | Install |
| diagnosing-superpowersobra/superpowersUse when a superpowers session went wrong and your human partner wants to know why — repeated work, ignored plans, stumbles, poor results, a skill that didn't fire, "it took too long", "why is it so expensive", "what is it doing" — or wants to build a bug report for the superpowers maintainers, for the current session or a past one identified by id or path, on any harness. | Stars: 322k | Updated | Claude CodeCodex | Verified | Install |
| dispatching-parallel-agentsobra/superpowersUse when facing 2+ independent tasks that can be worked on without shared state or sequential dependencies | Stars: 322k | Updated | Claude CodeCodex | Verified | Install |
| executing-plansobra/superpowersUse when executing an implementation plan in the current session as the implementer yourself — your human partner chose inline execution, or no subagent tool is available | Stars: 322k | Updated | Claude CodeCodex | Verified | Install |