What problem does it solve? Animating SvelteKit apps with GSAP breaks easily: pages get reused on param changes, intros flash settled content before hydration, outros get skipped on back/forward navigation, and hidden content hurts indexing and LCP. This Skill provides a complete lifecycle contract (mount → initial state → intro → settled → outro → end state → unmount) plus recovery, cleanup, and verification rules so route and component animation behaves correctly. ## Core Features & Use Cases - Engine selection guidance: Decides between Svelte transitions, View Transitions, and GSAP per element, with rules to keep one engine per node. - Navigation-aware transitions: Covers beforeNavigate vs onNavigate outro strategies, navigation locking, popstate handling, page reuse vs {#key} remount, and swap-gap covers. - Initialization and recovery contract: Pre-paint hiding with deadlines, rollback on setup failure, reduced-motion paths, and a failure verification matrix protecting readability, SEO, and LCP. - Use Case: Add an interruptible GSAP page transition to a SvelteKit app where the outgoing page animates before the URL changes, back/forward skips the outro, and a blocked bundle still leaves content readable. ## Quick Start Use the gsap-sveltekit skill to add GSAP page transitions and component enter/exit animations to this SvelteKit app.