implementation-debugging

implementation-debugging is a skill for Claude Code, Codex from dylantarre/animation-principles. It costs 19 tokens per session (757 once invoked), scanned A, original, MIT.

A troubleshooting guide for finding why web animations fail, look wrong, trigger at the wrong time, or behave differently across browsers.

In plain words
What is it for?
Use it to inspect CSS animation settings, visibility, layering, browser differences, and visual glitches.
Why use it?
It gives you a structured way to identify common causes such as incorrect timing, hidden elements, bad keyframes, and competing animations.

Skill for Claude CodeCodex

Written for no agent in particular: nothing here depends on one.

Good fit Use it to inspect CSS animation settings, visibility, layering, browser differences, and visual glitches.

Compare 6 skills from other repositories ↓
Install with agentmods
npx agentmods add skills/dylantarre/animation-principles/implementation-debugging
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.

Any agent
npx skills add dylantarre/animation-principles --skill implementation-debugging
Clone the repo
git clone --depth 1 https://github.com/dylantarre/animation-principles

Made for: Claude Code, Codex.

Wrote 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.

agentmods badge for implementation-debugging

README.md
[![agentmods](https://agentmods.dev/badge/skills/dylantarre/animation-principles/implementation-debugging.svg)](https://agentmods.dev/skills/dylantarre/animation-principles/implementation-debugging)
Your own site
<a href="https://agentmods.dev/skills/dylantarre/animation-principles/implementation-debugging"><img src="https://agentmods.dev/badge/skills/dylantarre/animation-principles/implementation-debugging.svg" alt="Measured on agentmods" height="20"></a>
Per session 19 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 757 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe. Third-party audits
  • Socket pass 18 Mar 2026
  • Snyk pass 15 Feb 2026
How audits are shown
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.1 $0.00019 $0.00757
Opus 5 $0.00010 $0.00378
Sonnet 5 $0.00004 $0.00151
Haiku 4.5 $0.00002 $0.00076

Measured 4d ago against content hash 44fb6c01c46b, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-08, from the pricing page.

Security

Grade A, and why

implementation-debugging 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 4d 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.

skills/12-by-problem-type/implementation-debugging/SKILL.md · 98 lines

How it starts

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

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

Read the full file on GitHub · 98 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. 4d ago First seen · 98 lines · 19 tokens per session scan A 44fb6c01c46b

Subscribe to this mod's changes

implementation-debugging is a skill published in the GitHub repository dylantarre/animation-principles (79 stars, last pushed 8mo ago), licensed MIT. It adds 19 tokens to every session and 757 once invoked, about $0.0001 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-09-03.

Related

Other skills, from other repositories

fixing-motion-performance

Audit and fix animation performance issues including layout thrashing, compositor properties, scroll-linked motion, and blur effects. Use when animations stutter, transitions jank, or reviewing CSS/JS animation performance.

ibelick/ui-skills · 45 tokens

ui-debug-workflow

Debug UI changes with a repeatable evidence-first workflow. Use when validating visual regressions, reproducing frontend bugs, comparing baseline vs changed behavior, collecting screenshots/DOM/logs, or producing stakeholder-ready UI debug reports. Keywords: ui bug, visual regression, browser devtools, playwright…

pantheon-org/tekhne · 72 tokens

frontend-visual-verification

Confirm a CSS/HTML/template change actually rendered in a running browser — without being fooled by stale browser cache. Use whenever you edited frontend code (CSS, EJS/HTML, components) and must verify the visual result, especially when a vision screenshot seems to contradict the DOM or the served asset.

pedroiff0/awesome-skills · 66 tokens

inspecting-hermes-desktop-dom

When you are developing apps/desktop and the user is running that same app (hgui / npm run dev), you can read the live rendered DOM of the window they are looking at — computed styles, geometry, which CSS rule actually won, console output — instead of inferring it from .tsx and being wrong.

AtlasOmnia/hermes-custom-pack · 28 tokens

inspecting-hermes-desktop-dom

Read the live Hermes desktop DOM/CSS over CDP.

NousResearch/hermes-agent · 20 tokens

baseline-ui

Quickly deslop UI code by fixing spacing, hierarchy, typography, and small layout issues. Use when the interface needs a fast cleanup or polish pass.

ibelick/ui-skills · 34 tokens