axiom-uikit-animation-debugging

Debug CAAnimation issues in UIKit applications using diagnostic patterns.

Updated Dec 3, 2025
One-click install
npx skills add https://github.com/tuliopc23/flying-dutchman-app --skill axiom-uikit-animation-debugging
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: axiom-uikit-animation-debugging
Source: https://github.com/tuliopc23/flying-dutchman-app/tree/main/.claude/skills/axiom-uikit-animation-debugging
Command: npx skills add https://github.com/tuliopc23/flying-dutchman-app --skill axiom-uikit-animation-debugging

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill provides a systematic approach to diagnosing and fixing common issues with Core Animation (CAAnimation) in UIKit, such as completion handlers not firing, incorrect animation durations, janky animations, and discrepancies between simulator and device behavior.

Core Features & Use Cases

  • Systematic Diagnosis: Guides users through mandatory first steps to identify the root cause of animation problems.
  • Pattern-Based Solutions: Offers specific, actionable patterns to resolve common issues like completion handler failures, duration mismatches, and state persistence.
  • Decision Tree: Provides a clear decision tree to navigate towards the correct debugging pattern.
  • Use Case: When a CABasicAnimation's completion handler doesn't fire on a real device, or a spring animation behaves differently across devices, this Skill helps pinpoint the exact cause and apply the correct fix.

Quick Start

Run the mandatory first steps to diagnose the animation issue.

Frequently Asked Questions about axiom-uikit-animation-debugging

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
Why does my CABasicAnimation completion handler not fire on a real device?

UIKit animation completion handlers may not fire due to layer state persistence or simulator-device timing discrepancies. Systematic debugging through CATransaction analysis and specific diagnostic patterns identifies the root cause and applies the correct fix.

How do I debug janky UIKit animations systematically?

To debug janky UIKit animations, run mandatory diagnostic first steps including diagnostic print statements and layer state checks. This systematic approach identifies visual jank causes and applies specific patterns to resolve Core Animation performance issues.

What causes incorrect animation durations in Core Animation on iOS?

Incorrect Core Animation durations often stem from simulator-device timing discrepancies or improper CATransaction configuration. Analyzing layer states and transaction contexts through systematic debugging reveals the mismatch source and guides the correct duration adjustment pattern.

Can I use this systematic approach to fix spring animation differences between simulator and device?

Yes, this debugging approach specifically addresses simulator-device timing discrepancies in spring animations. By employing diagnostic print statements and CATransaction analysis, you can isolate why spring behaviors differ across devices and apply targeted fixes.

UIKit animation debugging not working, what are common limitations?

Common limitations in UIKit animation debugging involve overlooking mandatory first diagnostic steps and failing to check layer states. Bypassing the decision tree or ignoring CATransaction contexts often leads to unresolved completion handler failures and persistent visual jank.