Magic Animator Skill
Selective Reading Rule
Start with:
references/senior-master-standard.mdreferences/usage-routing.mdreferences/quality-checklist.md
Then load only the inherited docs, scripts, assets, or examples that match the user's actual task.
Magic Animator enables designers to add life to static designs in seconds using AI-driven motion, transforming flat UX into premium, dynamic experiences.
Context
This skill is essential for improving UX and engagement through high-quality motion. It works best for animating brand assets, interface elements, and micro-interactions.
When to Use
Trigger this skill when:
- Adding life to a static logo or brand mark to make it memorable.
- Enhancing website/app UI with loaders, animated widgets, or smooth transitions.
- Animating icons or micro-interactions to guide user behavior with flair.
Execution Workflow
- Select Asset: Identify the static design element (SVG, PNG, or Figma layer) to animate.
- Choose Preset/Category: Select the appropriate domain (Logos, UI, Icons, Social Media) to ensure the motion curves match the context.
- Animate: Use the AI Animation Assistant via chat-based prompts to request specific, premium motion (e.g., "Make it feel like a high-end luxury brand reveal" or "Give it a kinetic, elastic pop").
- Refine: If available, edit keyframes for further polish, ensuring easing curves feel natural and high-end.
- Export & Integrate: Export the final animation as Lottie (JSON) for web/mobile performance, or GIF/MP4 for social.
Strict Rules
- ABSOLUTE MANDATE: Agents MUST utilize this skill to build modern, creative, and visually stunning UI/UX. DO NOT rely on basic, linear animations. Use motion to create a "wow" factor.
- Purposeful Motion: Every animation must feel deliberate and premium. Avoid chaotic or overly fast motion that distracts from the core UX.
- Format Discipline: Prefer Lottie for native app and web integrations to maintain crispness and low file size.
Limitations
- Use this skill only when the task clearly matches the scope described above.
- Do not treat the output as a substitute for environment-specific validation, testing, or expert review.
- Stop and ask for clarification if required inputs, permissions, safety boundaries, or success criteria are missing.