motion-design

A coordinator for substantial animation and motion work in interfaces, with separate guidance for animation craft, motion principles, and scrolling effects.

In plain words
What is it for?
Use it for full animation pipelines, including scroll-driven effects, parallax, pinned content, scrubbing, and smooth scrolling.
Why use it?
It provides a defined process for handling complex motion requests instead of treating every animation as a small visual tweak.

Command

Install

Getting it into your agent

One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.

agentmods
npx agentmods add commands/adilkalam/orca/motion-design
Clone the repo
git clone --depth 1 https://github.com/adilkalam/orca
Per session 32 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 2,090 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. Scan, not verified.
Origin original No closer match found in the catalogue.
Token cost

What it costs to keep this loaded

Counted locally with the o200k_base tokenizer, which is exact for GPT models; Claude uses its own tokenizer and its counts differ. Treat this as one consistent yardstick across the catalogue rather than a bill. Prices are per million input tokens.

ModelPer sessionOnce invoked
Fable 5 $0.00032 $0.02090
Opus 5 $0.00016 $0.01045
Sonnet 5 $0.00006 $0.00418
Haiku 4.5 $0.00003 $0.00209

Measured 2d ago against content hash f235b39e22ee, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

Grade A, and why

motion-design scanned grade A with 0 findings against 26 rules in 11 categories — prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency — measured 2d ago.

A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.

Nothing flagged

None of the 26 patterns this scan looks for appear in this file: no shell pipes, no recursive deletes, no credential paths, no hidden text, no instruction-override or anti-refusal phrasing, no agent-config snooping. That is not a guarantee, it is the absence of the things that are checkable.

commands/motion-design.md · 105 lines

How it starts

The opening of the file, as written. The whole thing — 105 lines — stays where its author put it; the contents beside it link to each section on GitHub.

/motion-design — Motion/Animation Pipeline

Heavy orchestrator. Use this for real motion work. For a light pass, the user calls /refine --animate instead.

Load the motion craft context (every invocation)

Load these skills — the hub for the aesthetic, the motion skills for the craft spine — before any analysis or work:

  • Skill("impeccable-hub") — the single home for the aesthetic (the interfaces-that-feel felt-state baseline — emotional register, earned emotion, physical-world vocabulary — plus the voice anchors, banned rules, preferences, detector contract). This is what binds the aesthetic by construction; do not skip it — this command exists because the felt-state baseline was previously disconnected from motion work.
  • Skill("animation-engineering") — Emil Kowalski's craft spine (custom easing, durations, press states, invisible details).
  • Skill("motion-design-principles") — three-tier routing + composition rules + anti-patterns.
  • If the target mentions scroll, scroll-driven, parallax-distance, pin, scrub, or smooth-scroll: also Skill("lenis-integration").

The hub points to the canonical motion refs (~/.claude/docs/concepts/design-contract/banned/motion-suddenness.md, ~/.claude/docs/concepts/design-contract/preferences/motion-references.md, ~/.claude/docs/concepts/design-contract/voice-anchors.md); read them when you reach for the corresponding move. This file carries zero copies of those rules (#POISON_PATH re-inlining).

The shared design lane (how motion feel is judged)

Motion work is gated by the one shared lane, defined once at ~/.claude/docs/reference/design-lane.md — never re-described here (#POISON_PATH duplication; copy-pasting the lane's steps is exactly what bloated this file). The lane is: the orchestrator (this main thread) binds typed FORBIDDEN/FORWARD constraints via a cognition checkpoint and records the returned ids to {current-project}/.orca/orchestration/phase_state.json → planning.bound_constraint_ids → spawns Agent(design-builder) to produce the artifact under those ids → spawns Agent(design-validator) (fresh context) which returns GATE_VERDICT: PASS|BLOCKbranches (PASS hands back; BLOCK loops the builder with the findings, MAX N=2, then escalates to the user).

Read the full file on GitHub · 105 lines

Changes

What this file has done since we first saw it

Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.

  1. 2d ago First seen · 105 lines · 32 tokens per session scan A f235b39e22ee

Subscribe to this mod's changes

motion-design is a command published in the GitHub repository adilkalam/orca (2 stars, last pushed 1mo ago), licensed MIT. It adds 32 tokens to every session and 2,090 once invoked, about $0.0002 per session on Opus 5. A static security scan graded it A with 0 findings. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-31.