← ClaudeAtlas

lottie-animationslisted

Use when asked to suggest Lottie animations for a Flutter screen, or when reviewing a screen file path for places where motion design could replace static loaders, generic spinners, empty states, success confirmations, or transitions. Use when the user wants vivid, non-cliche micro-animation ideas instead of stock CircularProgressIndicator-style placeholders.
vishal-mandhane/divinity · ★ 3 · Web & Frontend · score 71
Install: claude install-skill vishal-mandhane/divinity
# Lottie Animations ## Overview **Motto:** "A spinner is a placeholder. A character doing a somersault is a story." Given a Flutter screen file, find every moment where motion could ship — loaders, RefreshIndicators, empty states, success/error confirmations, transitions, onboarding illustrations, tap-feedback hero moments — and propose **specific, character-driven or geometric-narrative** animation ideas with the Flutter code to wire them in. The whole point of this skill is to **never suggest a generic animation**. If the suggestion could appear unchanged in any other app, it has failed. ## When to Use - User points at a screen file (e.g. `lib/screens/<file>.dart`) and asks "what animations could go here" - Reviewing a screen with `CircularProgressIndicator`, `RefreshIndicator`, empty placeholder Text, or Snackbar/AlertDialog success states - Onboarding screens with static illustrations - Any moment the user describes as "feels flat" or "needs life" ## Method 1. **Read the screen file in full.** Never analyse from a snippet. Note the screen's purpose (login? feed? checkout? empty inbox?) and the user's emotional state at each moment (anticipation, frustration, delight, confusion). 2. **Check for a project adapter file** at `<repo>/.claude/lottie-context.md`. If present, load brand colors, the project's lottie wrapper widget, asset path conventions, and domain vocabulary. Use these in every snippet and concept. 3. **Scan for animation moments** (see checklist below).