implementation-debugging — Claude Code skill: install and overview
This skill diagnoses web animation glitches and broken transitions. It helps when CSS or JS motion drops frames, renders off-screen, or fails to repeat.
npx skills add dylantarre/animation-principles --skill implementation-debugging -a claude-codeWhat implementation-debugging does
The skill structures web animation troubleshooting around motion principles. It isolates issues into duration mismatches in Timing, missing keyframe values in Pose-to-Pose, and layering collisions in Staging. Visual stutter or subpixel tearing fall under Solid Drawing checks.
The guide includes concrete steps for common rendering bugs. When motion runs choppy, it flags layout thrashing and directs work toward transform and opacity. If an element jumps after playing, it points to setting animation-fill-mode: forwards. It also supplies a reflow trick with void element.offsetWidth for restarting CSS keyframes in JavaScript.
Non-animatable properties will fail silently. Properties like display cannot interpolate frames. Without swapping them for opacity or translation, smooth movement will not happen.
What it helps with
- Eliminate initial frame flickers and start jumps in CSS animations
- Fix broken end states by setting correct fill modes
- Resolve choppy frame rates caused by layout thrashing
- Reset and replay CSS animations reliably via JavaScript
Example prompts for the agent
- The modal fade animation stutters on mobile viewports, check the properties for layout thrashing
- My CSS keyframe animation snaps back to the beginning when it finishes instead of staying open
- The loader animation only runs once when toggling the active class, how do I reset the reflow?
How to install implementation-debugging
1Skills CLI (Vercel)
npx skills add dylantarre/animation-principles --skill implementation-debugging -a claude-code2Manually: put the files in place
~/.claude/skills/implementation-debugging/SKILL.mdCopy the whole skill folder; for one project use .claude/skills/implementation-debugging/
1Skills CLI (Vercel)
npx skills add dylantarre/animation-principles --skill implementation-debugging -a codex2Manually: put the files in place
.agents/skills/implementation-debugging/SKILL.mdFor all projects use ~/.agents/skills/
1Skills CLI (Vercel)
npx skills add dylantarre/animation-principles --skill implementation-debugging -a cursor2Manually: put the files in place
.cursor/skills/implementation-debugging/SKILL.mdCursor also reads .agents/skills/ and .claude/skills/
1GitHub CLI
gh skill install dylantarre/animation-principles implementation-debugging2Manually: put the files in place
.github/skills/implementation-debugging/SKILL.md1Skills CLI (Vercel)
npx skills add dylantarre/animation-principles --skill implementation-debugging -a gemini-cli2Platform CLI
gemini skills install https://github.com/dylantarre/animation-principles --path skills/12-by-problem-type/implementation-debuggingManually: put the files in place
.devin/skills/implementation-debugging/SKILL.mdThe legacy .windsurf/skills/ path still works
Skills CLI (Vercel)
npx skills add dylantarre/animation-principles --skill implementation-debugging -a opencodeClaude.ai
Zip the folder and upload it in Settings → Capabilities → Skills
Step by step, with commands for each platform: How to install skills in Claude Code: five ways
Questions about implementation-debugging
How to install implementation-debugging in Claude Code?
Run npx skills add dylantarre/animation-principles --skill implementation-debugging -a claude-code in your terminal.
What does the implementation-debugging skill do?
It provides a diagnostic framework for broken UI animations. The skill offers actionable checklists for CSS overrides, frame drops, and rendering issues.
Why does an animation fail to hold its final state?
By default, CSS animations snap back to their base styles once finished. Adding animation-fill-mode: forwards keeps the target element at its final keyframe.
Source text
SKILL.md · MIT
---
name: implementation-debugging
description: Use when animation doesn't work as expected, has bugs, or behaves inconsistently
---
# Implementation Debugging
Debug animation issues using Disney's principles as diagnostic framework.
## Problem Indicators
- Animation doesn't play at all
- Animation plays but looks wrong
- Works in dev, broken in production
- Inconsistent across browsers
- Animation triggers at wrong time
- Flickering or visual glitches
## Diagnosis by Principle
### Timing
**Issue**: Animation timing is off
**Debug**: Check duration values. Verify units (ms vs s). Check if CSS transition is being overridden. Inspect computed styles.
### Straight Ahead vs Pose-to-Pose
**Issue**: Keyframes not hitting
**Debug**: Verify all keyframe percentages. Check for typos in property names. Ensure values are animatable.
### Staging
**Issue**: Animation hidden or clipped
**Debug**: Check z-index, overflow, opacity. Verify element is in viewport. Check for `visibility: hidden`.
### Solid Drawing
**Issue**: Visual glitches during animation
**Debug**: Look for subpixel rendering issues. Add `transform: translateZ(0)` for GPU layer. Check for layout thrashing.
### Follow Through
**Issue**: Animation ends abruptly or wrong state
**Debug**: Check `animation-fill-mode`. Verify end state matches CSS. Check for competing animations.
## Common Bugs
| Symptom | Likely Cause | Fix |
|---------|--------------|-----|
| No animation | Property not animatable | Use transform instead of changing property directly |
| Flicker at start | No initial state | Set initial values explicitly |
| Wrong end state | Fill mode | Add `forwards` to animation |
| Choppy motion | Layout thrashing | Animate only transform/opacity |
| Works once only | Animation not reset | Remove and re-add class, or use JS |
## Quick Fixes
1. **Check DevTools Animation panel** - See timeline
2. **Verify animatable properties** - Not all CSS animates
3. **Add `animation-fill-mode: forwards`** - Keep end state
4. **Force GPU layer** - `will-change: transform`
5. **Check for `!important`** - May override animation
## Troubleshooting Checklist
- [ ] Is animation class/trigger being applied? (DevTools Elements)
- [ ] Are properties animatable? (`display` is not, `opacity` is)
- [ ] Check computed styles for overrides
- [ ] Is element visible? (opacity, visibility, display, z-index)
- [ ] Any JavaScript errors blocking execution?
- [ ] Check Animation panel in DevTools
- [ ] Test in incognito (no extensions)
- [ ] Compare working vs broken environment
## Code Pattern
```js
// Debug: Log animation events
element.addEventListener('animationstart', (e) => {
console.log('Animation started:', e.animationName);
});
element.addEventListener('animationend', (e) => {
console.log('Animation ended:', e.animationName);
});
// Debug: Check computed animation
const styles = getComputedStyle(element);
console.log('Animation:', styles.animation);
console.log('Transition:', styles.transition);
// Reset animation
element.classList.remove('animate');
void element.offsetWidth; // Trigger reflow
element.classList.add('animate');
```
## DevTools Tips
1. **Elements > Styles**: Check computed animation values
2. **Performance tab**: Record and analyze frames
3. **Animations panel**: Slow down, replay, inspect
4. **Console**: Log animation events
© dylantarre · MIT · dylantarre/animation-principles