From dylantarre-animation-principles
Use when animation "feels wrong" but you can't pinpoint why—debugging floaty movement, stiff characters, unclear action, or any motion that isn't working and needs systematic troubleshooting.
npx claudepluginhub joshuarweaver/cascade-content-creation-misc-1 --plugin dylantarre-animation-principlesThis skill uses the workspace's default tool permissions.
Think like a doctor examining symptoms. Something feels wrong. Your job is to identify the specific principle being violated and prescribe the cure. Systematic diagnosis beats random fixes.
Generates design tokens/docs from CSS/Tailwind/styled-components codebases, audits visual consistency across 10 dimensions, detects AI slop in UI.
Records polished WebM UI demo videos of web apps using Playwright with cursor overlay, natural pacing, and three-phase scripting. Activates for demo, walkthrough, screen recording, or tutorial requests.
Delivers idiomatic Kotlin patterns for null safety, immutability, sealed classes, coroutines, Flows, extensions, DSL builders, and Gradle DSL. Use when writing, reviewing, refactoring, or designing Kotlin code.
Think like a doctor examining symptoms. Something feels wrong. Your job is to identify the specific principle being violated and prescribe the cure. Systematic diagnosis beats random fixes.
When animation feels off, ask: What principle is being violated, and how?
"It doesn't look right" isn't actionable. The 12 principles are your diagnostic checklist. Every animation problem is a principle problem—find which one, and the solution becomes clear.
Likely Causes:
Fixes:
Likely Causes:
Fixes:
Likely Causes:
Fixes:
Likely Causes:
Fixes:
Likely Causes:
Fixes:
Likely Causes:
Fixes:
One fix at a time. Animation problems often have multiple causes, but changing everything at once makes it impossible to learn what worked. Diagnose, treat one principle, evaluate, repeat.