Diogenesoftoronto/keating / video/keating-surface-tour/.agents/skills/motion-graphics
motion-graphics
VerifiedA short, design-led motion graphic where motion is the message — kinetic typography, stat count-up, chart/data-viz hit, logo sting / brand lockup, lower-third / callout / social overlay, animated map (highlight regions, connect places, zoom to a location), animated tweet / news-article / headline, webpage / UI animation (scroll, cursor, callouts), or fusing a real image's geometry into a chart. Usually under 10s (up to ~30s), no narration or live-action subject; renders to MP4 or transparent overlay. Longer / narrated / multi-scene → /general-video. Unclear → /hyperframes.
| File | Kind | Size |
|---|---|---|
| SKILL.md | skill md | 15.3 KB |
| agents/builder.md | markdown | 3.3 KB |
| agents/director.md | markdown | 5.6 KB |
| agents/finalize.md | markdown | 1.0 KB |
| catalog-map.md | markdown | 10.3 KB |
| categories/asset-fusion/module.md | markdown | 3.9 KB |
| categories/charts/module.md | markdown | 1.6 KB |
| categories/kinetic-type/module.md | markdown | 1.6 KB |
| categories/logo-reveal/module.md | markdown | 1.1 KB |
| categories/lower-thirds/module.md | markdown | 1.1 KB |
| categories/maps/bake-basemap.mjs | script | 14.4 KB |
| categories/maps/module.md | markdown | 9.4 KB |
| categories/news/module.md | markdown | 5.3 KB |
| categories/stat/module.md | markdown | 1.2 KB |
| categories/tweet/module.md | markdown | 1015 B |
| categories/webpage/module.md | markdown | 2.5 KB |
| grounding/PROTOCOL.md | markdown | 3.0 KB |
| grounding/locate.mjs | script | 8.0 KB |
| phases/source/guide.md | markdown | 1.9 KB |
| references/builder-contract.md | markdown | 2.8 KB |
| references/motion-vocabulary.md | markdown | 3.5 KB |
| references/shot-plan-ir.md | markdown | 2.6 KB |
| samples/asset-fusion/_ref-circle-highlight.html | other | 10.4 KB |
agents/director.md
View on GitHub# Motion-Graphics Director
Turn a request into a `shot-plan.json` for a short (~3–30s) **design-led motion graphic**. You run in **two parts** around the asset-sourcing step: **Part 1 (plan)** before sourcing, **Part 2 (design)** after. You do NOT write composition code — that's the Builder. Schema: `references/shot-plan-ir.md`.
## Part 1 — Plan (before sourcing)
Emit a DRAFT `shot-plan.json`.
0. **Decide first: does this need a search?** No → a **form category** (user supplies content). Yes → emit a search plan; the specific **search-driven category** (`webpage` / `news` / `tweet` / `asset-fusion`) is confirmed by what the search returns (Step 2 → finalized in Part 2).
1. **Classify** — form categories by intent below; search-driven categories are picked post-search:
| Category | Pick when… |
| -------------- | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| `kinetic-type` | a punchy line / quote / title; text is the hero |
| `stat` | a single hero number / count-up |
| `charts` | bar / line / pie / race / % from data |
| `logo-reveal` | a logo sting / brand lockup (user supplies the logo) |
| `lower-thirds` | name/title bars, callouts, social overlays |
| `maps` | a geographic shot — highlight regions, connect places, zoom to a location. Sub-fork: **vector** (D3, stylized) vs **basemap** (baked MapLibre — real satellite/dark/zoom-to-place) |
| `webpage` | highlight / animate a real captured web page or UI _(search-driven)_ |
| `news` | a news article → article-highlight: blur → zoom into keyword _(search-driven)_ |
| `tweet` | a tweet → animated card _(search-driven)_ |
| `asset-fusion` | a real photo/asset's geometry _becomes_ the chart _(search-driven)_ |
If genuinely ambiguous between two, ask exactly one question. Then load `categories/<id>/module.md` for that category's specifics.
2. **Asset strategy → `asset_needs[]`.** Each item: `{ role, kind: image|icon|logo|svg|news|web|tweet, query|source, treatment }`.
- asset-free (`kinetic-type`, most `stat`/`charts`) → `asset_needs: []`.
- `maps` → **vector** lane: `asset_needs: []` (D3/TopoJSON, runs live in HF). **basemap** lane (satellite/dark/zoom-to-place): `asset_needs: [{ type: "map-bake", … }]` (baked in Source — see `categories/maps/module.md`).
- `webpage` / `news` / `tweet` → search the real source (page / article / tweet) + a supporting image. **Two-pole queries only**: atomic (1–3 words, composable: portraits, logos, objects) OR specific (5–15 words: a news event, a tweet). Never the middle. A failed specific query is dropped, not broadened.
- `asset-fusion` → search or generate one hero asset.
- `logo-reveal` → user-supplied logo (`source`).
3. **Envelope**: `duration_s` (3–30), `fps` (30), `canvas` (default 1080×1920; 16:9 / 1:1 per platform), `style`, `palette` (hex list, or `"derive-from-asset"`), `font` (from the HF embed list), `beats`, `export` (`mp4` | `alpha-overlay`).
4. **Shot brief**: one paragraph — what the viewer experiences + the single dominant motion idea.
## Part 2 — Design (after sourcing)
Given the draft + resolved `assets/index.md` (if Step 2 ran) + `catalog-map.md`, design the shot **around the assets**:
- Pick the **catalog block(s)** + the `hyperframes-animation` rules / blueprints (catalog-aware — see `catalog-map.md`).
- Layout (hero-frame), motion (per `references/motion-vocabulary.md`), beats, pacing, exits.
- `asset-fusion`: read the asset's **geometric affordance** → `element_positions` (center / extent / safe-zones / avoid-zones) + **eyedropper palette** from the asset.
- Finalize `shot-plan.json`: `content.block` + `content.customize` + the per-category `content`.
## Heuristics (design-led short motion)
- **Motion IS the message**; no narration arc. Hook lands fast (~first 0.5s). **One dominant motif.** Pattern-interrupt if the piece runs >~2.5s (change exactly one thing). Effect intensity matches the energy. Legibility: a key element stays readable ≥~0.3s. Beats may be anticipated ~0.1s for perceived sync.
- **Reuse-first**: name a catalog block; ask for hand-authored motion only for gaps + the `asset-fusion` affordance.
Then hand `shot-plan.json` to the Builder.
Related skills
| Skill | Stars | Updated | Works with | Status | Install |
|---|---|---|---|---|---|
| brainstormingobra/superpowersYou MUST use this before any creative work - creating features, building components, adding functionality, modifying behavior, or planning anything new, in software or out of it (a talk, a business, a renovation). | Stars: 322k | Updated | Claude CodeCodex | Verified | Install |
| brand-guidelinesanthropics/skillsApplies Anthropic's official brand colors and typography to any sort of artifact that may benefit from having Anthropic's look-and-feel. Use it when brand colors or style guidelines, visual formatting, or company design standards apply. | Stars: 198k | Updated | Claude CodeCodex | Verified | Install |
| frontend-designanthropics/skillsGuidance for distinctive, intentional visual design when building new UI or reshaping an existing one. Helps with aesthetic direction, typography, and making choices that don't read as templated defaults. | Stars: 198k | Updated | Claude CodeCodex | Verified | Install |
| mcp-builderanthropics/skillsGuide for creating high-quality MCP (Model Context Protocol) servers that enable LLMs to interact with external services through well-designed tools. Use when building MCP servers to integrate external APIs or services, whether in Python (FastMCP) or Node/TypeScript (MCP SDK). | Stars: 198k | Updated | Claude CodeCodex | Verified | Install |