mastering-animate-presence

Audit Motion and Framer Motion code for AnimatePresence exit animation best practices.

3|Updated Apr 20, 2026
One-click install
npx skills add https://github.com/langgenius/due-date-hq-jwl --skill mastering-animate-presence-langgenius
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: mastering-animate-presence
Source: https://github.com/langgenius/due-date-hq-jwl/tree/main/.claude/skills/mastering-animate-presence
Command: npx skills add https://github.com/langgenius/due-date-hq-jwl --skill mastering-animate-presence-langgenius

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Exit animations in React apps often break silently: modals vanish instantly, list items jump during removal, and nested components disappear before their animations finish. This Skill audits Motion (Framer Motion) code against a defined rule set and reports every violation with exact file and line locations. ## Core Features & Use Cases - Rule-Based Auditing: Checks code against 12 rules across four categories: exit animations, presence hooks, mode selection, and nested exits. - Precise Findings: Outputs violations in file:line - [rule-id] format plus a severity summary table for triage. - Use Case: Before shipping a modal-heavy dashboard, run the audit on your components directory to catch missing AnimatePresence wrappers, absent exit props, index-based keys in animated lists, and uncoordinated nested exit timings. ## Quick Start Review the files in src/components for AnimatePresence and exit animation issues and list all findings with file and line numbers.

Frequently Asked Questions about mastering-animate-presence

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

FAQPage Schema
How do I audit Framer Motion exit animations in React?

Run the audit on your component files to check each motion element against 12 AnimatePresence rules. Findings are reported in file:line format with rule IDs like exit-requires-wrapper, plus a severity summary table.

Why does my modal disappear instantly instead of animating out?

The most common cause is a conditional motion element not wrapped in AnimatePresence, or a missing exit prop on the motion element. The exit-requires-wrapper and exit-prop-required rules detect both cases.

When should I use AnimatePresence mode popLayout vs wait?

Use popLayout for list reordering so exiting elements leave the layout flow, and use wait when sequencing enter and exit animations, but halve durations since wait nearly doubles total animation time. The mode-selection rules flag misuse of each.

Why do nested AnimatePresence children vanish when the parent exits?

Nested AnimatePresence components need the propagate prop so child exit animations run before the parent unmounts. The nested-propagate-required rule detects missing propagate, and nested-consistent-timing flags mismatched exit durations.

What are the limitations of this AnimatePresence audit?

The audit performs static rule-based review of Motion code and does not execute animations or measure runtime behavior. It covers exit animations, presence hooks, mode selection, and nested exits only, not general animation performance or styling.