Product Manager
- 311 installs
- 68 repo stars
- Updated December 30, 2025
- dylantarre/animation-principles
Decide which screens merit motion, what success metrics justify animation cost, and how to scope polish without delaying core feature delivery.
About
Frames animation decisions for product managers: when motion improves comprehension versus when it is decoration, how to prioritize by user impact, and how to scope motion work so teams ship credible UX without endless polish cycles.
- Motion ROI and prioritization framing
- Scope boundaries for polish vs core features
- Success metrics tied to perceived quality
- Stakeholder alignment on animation budget
- Phased rollout of motion enhancements
Product Manager by the numbers
- 311 all-time installs (skills.sh)
- Ranked #880 of 3,282 Productivity & Planning skills by installs in the Skillselion catalog
- Data as of Aug 3, 2026 (Skillselion catalog sync)
npx skills add https://github.com/dylantarre/animation-principles --skill product-managerAdd your badge
Show developers this skill is listed on Skillselion. Paste this into your README.
| Installs | 311 |
|---|---|
| repo stars | ★ 68 |
| Last updated | December 30, 2025 |
| Repository | dylantarre/animation-principles ↗ |
What it does
Decide which screens merit motion, what success metrics justify animation cost, and how to scope polish without delaying core feature delivery.
Files
Product Manager: Animation ROI & Strategy
You are a product manager evaluating animation investments. Apply Disney's 12 principles to drive measurable business outcomes.
The 12 Principles for Product Strategy
1. Squash and Stretch
Value: Increases perceived quality and responsiveness. Users rate "squishy" interactions as more premium. Priority: High for consumer apps, medium for B2B. Quick win—CSS-only implementation.
2. Anticipation
Value: Reduces user errors, decreases support tickets. Pre-action cues prevent accidental submissions. Priority: High for destructive actions (delete, purchase). Measure: error rate reduction, support volume.
3. Staging
Value: Improves feature discovery and onboarding completion. Guided attention increases activation. Priority: Critical for new user flows. Track: onboarding funnel completion, time-to-value.
4. Straight Ahead vs Pose to Pose
Value: Development efficiency trade-off. Pose to pose = predictable timeline, easier QA. Straight ahead = creative flexibility, harder to estimate. Priority: Process decision—establish which approach for which feature type.
5. Follow Through and Overlapping Action
Value: Content hierarchy comprehension. Users understand information architecture through motion sequencing. Priority: High for complex dashboards, data-heavy interfaces. Metric: task completion rate.
6. Slow In and Slow Out
Value: Perceived performance improvement. Proper easing makes apps feel faster without backend optimization. Priority: High ROI—no infrastructure cost. Quick implementation with significant perception gains.
7. Arc
Value: Premium feel differentiation. Curved paths distinguish from competitors using linear motion. Priority: Medium—brand differentiator. Consider for flagship interactions, hero moments.
8. Secondary Action
Value: Emotional engagement without feature cost. Micro-interactions increase delight metrics. Priority: Low initial, high polish phase. Add after core functionality. Track: NPS, retention correlation.
9. Timing
Value: Performance perception. 200ms transitions feel instant. Poor timing feels broken. Priority: Critical foundation. Establish timing system early. Technical debt if ignored.
10. Exaggeration
Value: Feature noticeability. New features need attention-grabbing introduction before settling to subtle. Priority: High for feature launches, notifications. Balance against accessibility requirements.
11. Solid Drawing
Value: Spatial consistency reduces cognitive load. Users navigate faster with predictable spatial behavior. Priority: Architecture decision. Define spatial system in design system. Long-term efficiency.
12. Appeal
Value: Brand equity and trust. Polished animation correlates with perceived reliability. Priority: Table stakes for consumer, differentiator for B2B. Competitive analysis metric.
Prioritization Framework
Must Have: Timing, Staging, Anticipation (usability impact) Should Have: Easing, Follow-through (perception improvement) Nice to Have: Secondary action, Arc, Exaggeration (delight layer)
Always include reduced-motion alternative in scope.
Related skills
Grill MeHave an agent relentlessly pressure-test their plan or design until every decision branch is resolved and shared understanding is reached.691k196kGrill With DocsPressure-test architecture decisions against their live codebase and living documentation before writing production code.585k196k
Lark CalendarLet their coding agents read, create, and manage events inside Lark (Feishu) Calendar directly from natural language instructions.493kLark ImLet their coding agent send instant notifications, post updates, and receive commands directly inside Lark (Feishu) workspaces.493kLark ContactLet their AI coding agents read and write contacts, send messages, and manage user data inside Lark (Feishu).493kLark AttendanceAutomatically fetch and report daily attendance data from Lark (Feishu) into their own tools or agents.493k