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.
npx skills add uiNerd16/aicanvas --skill design-motion-principlesgit clone --depth 1 https://github.com/uiNerd16/aicanvasWrote this? Show the measurements
A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.
[](https://agentmods.dev/skills/uinerd16/aicanvas/design-motion-principles)<a href="https://agentmods.dev/skills/uinerd16/aicanvas/design-motion-principles"><img src="https://agentmods.dev/badge/skills/uinerd16/aicanvas/design-motion-principles/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<a href="https://agentmods.dev/skills/uinerd16/aicanvas/design-motion-principles"><img src="https://agentmods.dev/badge/skills/uinerd16/aicanvas/design-motion-principles.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector pass
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.
| Model | Per session | Once invoked |
|---|---|---|
| Fable 5.1 | $0.00060 | $0.02921 |
| Opus 5 | $0.00030 | $0.01460 |
| Sonnet 5 | $0.00012 | $0.00584 |
| Haiku 4.5 | $0.00006 | $0.00292 |
Grade A, and why
design-motion-principles 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 10d 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.
How it starts
The opening of the file, as written. The whole thing — 328 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Design Motion Audit Skill
You are a senior design engineer specializing in motion and interaction design. When asked to audit motion design, you MUST follow this workflow exactly.
The Three Designers
- Emil Kowalski (Linear, ex-Vercel) — Restraint, speed, purposeful motion. Best for productivity tools.
- Jakub Krehel (jakub.kr) — Subtle production polish, professional refinement. Best for shipped consumer apps.
- Jhey Tompkins (@jh3yy) — Playful experimentation, CSS innovation. Best for creative sites, kids apps, portfolios.
Critical insight: These perspectives are context-dependent, not universal rules. A kids' app should prioritize Jakub + Jhey (polish + delight), not Emil's productivity-focused speed rules.
STEP 1: Context Reconnaissance (DO THIS FIRST)
Before auditing any code, understand the project context. Never apply rules blindly.
Gather Context
Check these sources:
- AGENTS.md — Any explicit context about the project's purpose or design intent
- package.json — What type of app? (Next.js marketing site vs Electron productivity app vs mobile PWA)
- Existing animations — Grep for
motion,animate,transition,@keyframes. What durations are used? What patterns exist? - Component structure — Is this a creative portfolio, SaaS dashboard, marketing site, kids app, mobile app?
Motion Gap Analysis (CRITICAL - Don't Skip)
After finding existing animations, actively search for missing animations. These are UI changes that happen without any transition:
Search for conditional renders without AnimatePresence:
# Find conditional renders: {condition && <Component />}
grep -n "&&\s*(" --include="*.tsx" --include="*.jsx" -r .
# Find ternary UI swaps: {condition ? <A /> : <B />}
grep -n "?\s*<" --include="*.tsx" --include="*.jsx" -r .
For each conditional render found, check:
- Is it wrapped in
<AnimatePresence>? - Does the component inside have enter/exit animations?
- If NO to both → this is a motion gap that needs fixing
What ships with it
9 files beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
- audit-checklist.md 5.0 KB
- references/accessibility.md 1.6 KB
- references/common-mistakes.md 5.1 KB
- references/emil-kowalski.md 9.5 KB
- references/jakub-krehel.md 9.8 KB
- references/jhey-tompkins.md 11 KB
- references/performance.md 2.0 KB
- references/philosophy.md 5.3 KB
- references/technical-principles.md 16 KB
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.
- 10d ago First seen · 328 lines · 60 tokens per session scan A 96acf08aa1ee
design-motion-principles is a skill published in the GitHub repository uiNerd16/aicanvas (51 stars, last pushed 3d ago), licensed MIT. It adds 60 tokens to every session and 2,921 once invoked, about $0.0003 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-30.
Other skills, from other repositories
ui-components
UI component library patterns for shadcn/ui and Radix Primitives. Use when building accessible component libraries, customizing shadcn components, using Radix unstyled primitives, or creating design system foundations.
design-system-architecture
Build scalable design systems with design tokens, component APIs, and documentation. Use when creating or evolving component libraries.
sigil-design
Generate, parse, and compile a unified DESIGN.md (33 categories, 519 tokens) that compiles to CSS, Tailwind v4, and W3C JSON. Use when creating a new design reference, extracting tokens from an existing site (sigil design extract), switching a project's visual identity, generating compiled token output, or auditing a…
sigil-playbook
The Sigil Playbook codifies the small vocabulary of structural patterns that make any new page "just work." Originating from the Reticle design language (Dedalus monorepo), these 10 rules — 6 compositional moves + 4 supporting patterns — replace dozens of ad-hoc layout decisions.
sigil-preset
Every custom preset MUST populate ALL 33 token categories and ALL fields.
sigil-migration
Before migrating, audit the existing project.