Now liveThe Skillselion MCP - thousands of ranked skills, loaded into your agent mid-task. No install.Get it →
ajianaz avatar

Svelte Ui Animator

  • 18 installs
  • 4 repo stars
  • Updated December 6, 2025
  • ajianaz/skills-collection

svelte-ui-animator is a Claude skill that implements purposeful, performant UI animations for Svelte and SvelteKit projects using Svelte transitions and actions.

About

This skill implements purposeful UI animations for Svelte and SvelteKit projects using Svelte's built-in transitions and actions. A developer uses it to add page-load intros, hover feedback, scroll reveals, and navigation transitions through a four-phase analyze, plan, implement, and verify workflow. It enforces transform/opacity-only performance rules and prefers-reduced-motion accessibility support.

  • Implements purposeful Svelte transitions, actions, and animation patterns
  • Runs a 4-phase workflow: analyze, plan, implement, verify
  • Enforces performance and prefers-reduced-motion accessibility rules

Svelte Ui Animator by the numbers

  • 18 all-time installs (skills.sh)
  • Ranked #1,576 of 2,245 Frontend Development skills by installs in the Skillselion catalog
  • Data as of Jul 28, 2026 (Skillselion catalog sync)
At a glance

svelte-ui-animator capabilities & compatibility

Capabilities
svelte design · stunning animations · svelte ui integration
Use cases
ui design · frontend
From the docs

What svelte-ui-animator says it does

Implement purposeful, performant animations using Svelte's built-in transitions and actions.
SKILL.md
npx skills add https://github.com/ajianaz/skills-collection --skill svelte-ui-animator

Add your badge

Show developers this skill is listed on Skillselion. Paste this into your README.

Listed on Skillselion
Installs18
repo stars4
Last updatedDecember 6, 2025
Repositoryajianaz/skills-collection

What it does

Add purposeful, performant animations to Svelte/SvelteKit UIs using transitions, actions, and scroll reveals.

Who is it for?

Developers adding motion and micro-interactions to Svelte/SvelteKit UIs the right way.

Skip if: Non-Svelte frameworks or projects that need no animation.

When should I use this skill?

When a user asks to add animations, animate a page/component, add hover or scroll effects, or page transitions in a Svelte project.

What you get

  • Animation audit table
  • Component-to-animation implementation plan
  • Reusable Svelte actions like scrollReveal

By the numbers

  • 5-priority animation priority table
  • 4-phase workflow (analyze, plan, implement, verify)

Files

SKILL.mdMarkdownGitHub ↗

Svelte UI Animator

Implement purposeful, performant animations using Svelte's built-in transitions and actions. Focus on key moments: hero intros, hover feedback, content reveals, and navigation transitions with Svelte's reactive nature.

Core Philosophy

"You don't need animations everywhere" - Prioritize:

PriorityAreaPurpose
1Hero IntroFirst impression, brand personality
2Hover InteractionsFeedback, discoverability
3Content RevealGuide attention, reduce cognitive load
4Background EffectsAtmosphere, depth
5Navigation TransitionsSpatial awareness, continuity

Workflow

Execute phases sequentially. Complete each before proceeding.

Phase 1: Analyze

1. Scan project structure - Identify all pages in src/routes/ and components in src/lib/components/ 2. Check existing setup - Review tailwind.config.js and app.html for existing animations/keyframes 3. Identify animation candidates - List components by priority category 4. Document constraints - Note installed animation libraries (svelte/transition, auto-animate, motion, etc.)

Output: Animation audit table. See references/component-checklist.md.

Phase 2: Plan

1. Map animations to components - Assign specific animation patterns 2. Determine triggers - Load, scroll (intersection), hover, click 3. Estimate effort - Low (CSS only), Medium (hooks needed), High (library required) 4. Propose phased rollout - Quick wins first

Output: Implementation plan with component → animation mapping.

Phase 3: Implement

1. Extend Tailwind config - Add keyframes and animation utilities 2. Add reduced-motion support - Accessibility first 3. Create reusable actions - scrollReveal, mousePosition, staggerAnimate if needed 4. Apply animations per component - Follow patterns in references/animation-patterns.md

Performance rules:

<!-- ✅ DO: Use transforms and opacity only -->
<div style="transform: translateY(20px); opacity: 0.5; filter: blur(4px);" />

<!-- ❌ DON'T: Animate layout properties -->
<div style="margin-top: 20px; height: 100px; width: 200px;" />

Phase 4: Verify

1. Test in browser - Visual QA all animations 2. Test reduced-motion - Verify prefers-reduced-motion works 3. Check CLS - No layout shifts from animations 4. Performance audit - No jank on scroll animations

Quick Reference

Animation Triggers

TriggerImplementation
Page loadCSS animation with animation-delay for stagger
Scroll into viewSvelte actions with IntersectionObserver or on:viewportenter
HoverTailwind hover: utilities or Svelte mouseenter/mouseleave
Click/TapState-driven with Svelte reactive statements ($:)

Common Patterns

Staggered children with Svelte transitions:

<script>
  import { flip, fly } from 'svelte/transition';
</script>

{#each items as item, i (item.id)}
  <div
    in:fly={{ y: 20, delay: i * 50 }}
    out:fly={{ y: -20 }}
  >
    {item.content}
  </div>
{/each}

Advanced scroll reveal action:

<!-- actions/scrollReveal.js -->
export function scrollReveal(node, options = {}) {
  const {
    threshold = 0.1,
    animation = 'fade-slide-up',
    delay = 0
  } = options;

  const observer = new IntersectionObserver(
    ([entry]) => {
      if (entry.isIntersecting) {
        setTimeout(() => {
          node.classList.add('animate-' + animation);
        }, delay);
      }
    },
    { threshold }
  );

  observer.observe(node);

  return {
    destroy() => observer.disconnect()
  };
}

Usage with reactive state:

<script>
  import { scrollReveal } from '$lib/actions/scrollReveal.js';
  import { onMount } from 'svelte';

  let isVisible = false;
  let element;

  onMount(() => {
    const observer = new IntersectionObserver(
      ([entry]) => isVisible = entry.isIntersecting
    );
    observer.observe(element);
    return () => observer.disconnect();
  });
</script>

<div
  bind:this={element}
  use:scrollReveal={{ animation: 'fade-in', delay: 100 }}
  class:visible={isVisible}
>
  Content here
</div>

Resources

  • Animation patterns: See references/animation-patterns.md
  • Audit template: See references/component-checklist.md
  • Tailwind presets: See references/tailwind-presets.md

Technical Stack

  • Svelte transitions: Primary choice - fade, fly, slide, scale, blur, crossfade
  • CSS animations: For complex keyframe animations not covered by Svelte transitions
  • Tailwind utilities: For hover states and basic animations
  • Auto-animate: For automatic layout animations (if installed)
  • Svelte actions: For custom scroll-triggered and interactive animations
  • Motion: For advanced gesture-based animations (if installed)
  • GSAP: For timeline-based sequences (if already installed)

Accessibility (Required)

Always include in global CSS:

@media (prefers-reduced-motion: reduce) {
  *, *::before, *::after {
    animation-duration: 0.01ms !important;
    transition-duration: 0.01ms !important;
    animation-iteration-count: 1 !important;
  }
}

Related skills

FAQ

What animation approach does it use?

Svelte's built-in transitions (fade, fly, slide, scale, blur, crossfade), Svelte actions, CSS animations, and Tailwind utilities.

Does it handle accessibility?

Yes, it requires prefers-reduced-motion support and warns against animating layout properties to avoid layout shift.

This week in AI coding

Five minutes, every Monday - the tools, releases and tactics for developers.

unsubscribe anytime.