
problem-diagnosis
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.
- Installs
- 491
- Last 24h
- —
- Trending rank
- —
- Security
- Not audited
Install
Works with every agent the skills CLI supports.
npx skills add https://github.com/dylantarre/animation-principles --skill problem-diagnosis- 01
Install
Run the command in your project. The CLI asks which agents to install for.
- 02
Describe the task
Ask your agent for something this skill covers. It loads problem-diagnosis automatically when relevant.
- 03
Review the result
The agent follows the SKILL.md steps, scripts and references bundled with the skill.
SKILL.md
The instructions your agent reads when the skill is triggered.
Problem Diagnosis
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.
Core Mental Model
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.
Diagnostic Framework
Symptom: "Floaty" or "Weightless"
Likely Causes:
- Missing slow-in/slow-out (objects should accelerate with gravity)
- Insufficient anticipation before jumps
- No squash on landing impacts
- Timing too uniform (everything same speed)
- Missing secondary weight (hair/clothing not responding to gravity)
Fixes:
- Add ease-in at motion start
- Add squash frames at impact points
- Include settling oscillations after stops
- Vary timing based on mass
Symptom: "Stiff" or "Robotic"
Likely Causes:
- Missing arcs (linear interpolation instead of curves)
- No overlapping action (all parts move together)
- Twinning (left and right doing identical things)
- No secondary action
- Timing too uniform
Fixes:
- Add arc curves to all motion paths
- Offset timing of connected body parts
- Break symmetry in poses
- Add breathing and weight shifts
- Include micro-movements
Symptom: "Unclear" or "Hard to Read"
Likely Causes:
- Poor staging (elements overlap confusingly)
- Weak silhouettes
- Insufficient anticipation (action comes from nowhere)
- Not enough exaggeration
- Competing attention points
Fixes:
- Simplify background during key action
- Push poses to clear silhouettes
- Extend anticipation timing
- Increase exaggeration 20%
- Reduce secondary action during primary beats
Symptom: "Boring" or "Lifeless"
Likely Causes:
- No appeal in character posing
- Timing lacks contrast (no fast vs. slow)
- Missing anticipation-payoff structure
- Insufficient exaggeration
- No secondary action or texture
Fixes:
- Push personality in poses
- Create timing contrast (faster fasts, slower slows)
- Add clear anticipation beats
- Increase exaggeration of key poses
- Layer in secondary movement
Symptom: "Cartoony" (Unintentionally)
Likely Causes:
- Excessive squash and stretch
- Over-exaggerated timing
- Physics violations too extreme
- Follow-through too elastic
Fixes:
- Reduce squash/stretch to 10-20% range
- Add more frames to smooth extremes
- Ground with realistic settling time
- Pull back follow-through delay
Symptom: "Too Fast" / "Too Slow"
Likely Causes:
- Frame count mismatch with intention
- Missing ease-in or ease-out
- Key poses not held long enough
- Anticipation/payoff imbalance
Fixes:
- Adjust frame count (add/remove in-betweens)
- Check easing curves
- Hold key poses 2-4 more frames
- Rebalance anticipation vs. action timing
Diagnostic Process
- Identify the symptom — Name what's wrong in plain terms
- Isolate the problem — Is it the whole scene or specific moments?
- Check principles systematically:
- Timing and spacing?
- Squash and stretch?
- Anticipation and follow-through?
- Arcs?
- Staging?
- Exaggeration level?
- Secondary action?
- Test hypothesis — Make one change, evaluate
- Iterate — If unfixed, try next most likely principle
The Golden Rule
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.
FAQ
What does the problem-diagnosis skill do?
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.
How do I install problem-diagnosis?
Run npx skills add https://github.com/dylantarre/animation-principles --skill problem-diagnosis in your project. The skills CLI detects the agents you use and copies the skill into the right folder. For Claude Code you can also place the skill folder at ~/.claude/skills/problem-diagnosis/ (personal) or .claude/skills/problem-diagnosis/ (project).
Which AI agents can use problem-diagnosis?
Any agent that supports the open Agent Skills format (a folder with a SKILL.md file), including Claude Code, Codex, Cursor, GitHub Copilot, Gemini CLI, Windsurf, Cline, OpenCode and more.
Is problem-diagnosis safe to install?
No partner security audit is available yet. Skills can run commands and scripts, so read the SKILL.md and any bundled files before installing.
Who maintains problem-diagnosis?
It is published by dylantarre in dylantarre/animation-principles. It has 491 recorded installs.
More from dylantarre/animation-principles
video-motion-graphics
dylantarre/animation-principles
Use when creating After Effects compositions, Premiere Pro motion, video titles, explainer videos, or broadcast motion graphics.
mobile-touch
dylantarre/animation-principles
Use when designing iOS/Android gestures, haptic feedback, touch interactions, or native mobile animations.
framer-motion
dylantarre/animation-principles
Use when implementing Disney's 12 animation principles with Framer Motion in React applications
motion-designer
dylantarre/animation-principles
Use when designing visual motion systems, creating animation specifications, or when a designer needs guidance on crafting beautiful, meaningful movement.
micro-interactions
dylantarre/animation-principles
Use when designing small UI feedback moments like button states, toggles, form validation, loading indicators, or notification badges.
web-motion-design
dylantarre/animation-principles
Use when building CSS animations, JavaScript transitions, React/Vue motion, or any browser-based animation work.
Popular frontend & design skills
setup-matt-pocock-skills
mattpocock/skills
Configure this repo for the engineering skills: set up its issue tracker, triage label vocabulary, and domain doc layout. Run once before first use of the other engineering skills.
frontend-design
anthropics/skills
Guidance 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.
hyperframes-animation
heygen-com/hyperframes
All animation knowledge for HyperFrames — atomic motion rules, multi-phase scene blueprints, scene transitions, broader motion-design techniques, AND the seven runtime adapters (GSAP default, plus Lottie, Three.js, Anime.js, CSS keyframes, Web Animations API, TypeGPU). Use for any motion or animation task: pick 2-4 rules and compose, or load a blueprint, or look up runtime-specific API (e.g. GSAP eases / Lottie player / Three.js mixer). Also covers auditing an existing composition's choreography (animation map) and 24 named text-animation effects. HyperFrames-native: single paused timeline, seek-safe, deterministic.
prototype
mattpocock/skills
Build a throwaway prototype to answer a design question. Use when the user wants to sanity-check whether a state model or logic feels right, or explore what a UI should look like.
hyperframes-core
heygen-com/hyperframes
The HyperFrames composition contract — build one renderable project. Use for composition structure, the data- timing attributes, class="clip", tracks, sub-compositions, variables, framework-owned media playback, deterministic-render rules, and validation. Read before writing composition HTML.
vercel-react-best-practices
vercel-labs/agent-skills
React and Next.js performance optimization guidelines from Vercel Engineering. This skill should be used when writing, reviewing, or refactoring React/Next.js code to ensure optimal performance patterns. Triggers on tasks involving React components, Next.js pages, data fetching, bundle optimization, or performance improvements.