DeepSeek x Opus Motion Skill

---
name: motion-design-prompt-generator
description: Make DeepSeek (or any model) produce motion-design videos that match what Claude Opus 5.5 makes from the same prompt, for any request in any style — brand films, showreels, kinetic typography, explainers and data stories, product and UI promos, character stories and music videos, abstract loops, title sequences. It reads the prompt like Opus, derives an art direction from it, plans before coding, builds a Remotion (React + SVG) project on a tested starter with generated sound, and reviews its own work with a five-juror critique. Triggers on 动效, 动态设计, 视频, 短片, 动画, 复刻 opus 效果, 扩写提示词, Remotion, motion graphics, showreel, MV.
---

# Opus-parity motion films (Remotion)

**Goal:** the same prompt, given to Opus 5.5 and to the model running this skill, gives films that look, move and sound almost the same, whatever the subject or style.

The gap is rarely taste. It is behaviour. Opus:
- honours every value in a long prompt;
- turns vague words into concrete design decisions;
- designs every element properly instead of settling for a placeholder;
- plans the whole timeline before coding;
- builds one shared system, so things stay consistent;
- looks at its own output and fixes it.

A weaker model skips each of these unless it is made explicit. This skill makes them explicit, on the Open Design architecture:

| Open Design piece | Here |
| --- | --- |
| A functional skill that owns the workflow | This file: priorities, the stages and the element playbooks |
| A `DESIGN.md` contract read by every render | The design contract at the top of `src/spec.ts`; `design-systems/*.md` are seeds for it |
| Templates | `templates/remotion-starter/`, tested (full source in `REFERENCE.md`) |
| A Design Jury critique gate | Stage 6: five jurors, fix until each scores ≥ 8 |
| An anti-slop checklist | The ban list in stage 6 |
| Deterministic rendering | Remotion: every frame is a pure function of the frame number |

## Priority order

When rules compete for attention, keep them in this order:
1. **The prompt's own words**: every value, beat, copy line and ban.
2. **Look and craft at the style's level**: composition, palette, type, and every element designed properly (see the playbooks). Texture and light come in here too. This is what a viewer judges first.
3. **Continuity**: real transformations, persistent identity, plausible physics.
4. **Rhythm and sound.**
5. **Bookkeeping**: ledgers, tables and checks. They serve 1–4 and never replace them.

**Helpers and examples are mechanics, not style.** `motion.tsx` decides where things are and how they move. It never decides what they look like. Never ship a helper's neutral default, such as a plain box or stick limbs, as the design. Never copy an example's subject, palette or layout into a different film. Every film gets its own designed look, at least as rich as it would be without the helpers.

## Invocation

- Any request for a motion piece runs the pipeline. Ask no questions: resolve gaps in stage 1 and state them in 解读.
- **Each new prompt is a new film**, built fresh from the starter, even in a conversation that already made one. Reuse earlier code only when the user says to modify it (修改, 改一下, 在上一版基础上, fix this). In a file-tool host, create a new project folder for the film.
- **Modes.** The default is to build. 只要提示词 / 扩写 / “prompt only” stops after stage 2 and outputs the expanded brief as one fenced `text` block.
- **Hosts.** Chat-only: output files as code blocks (stage 7). With file and shell tools: write the files, run `npx tsc -p .`, `npm run render` and `npm run check`, look at the stills, fix, then report.