product-manager — Claude Code skill: animation priorities
Helps a PM decide which animations are worth building and which can wait, using business value instead of taste.
npx skills add dylantarre/animation-principles --skill product-manager -a claude-codeWhat product-manager does
The skill kicks in when you prioritize animation work or put together a motion roadmap. It walks through Disney's 12 animation principles, but from a product angle: each one comes with a business value note and a priority level.
Timing, staging and anticipation land in the must-have bucket because they affect usability. A pre-action cue cuts accidental submissions and the support tickets that follow. Easing and follow-through sit in should-have — perceived speed improves with no backend work. Secondary action, arc and exaggeration are the delight layer, added after core functionality ships.
One rule is baked into the framework: a reduced-motion alternative always goes into scope. That turns accessibility from a late review objection into a planning item.
What it helps with
- rank animation features by priority
- explain the business value of each principle to the team
- build a quarterly motion roadmap
- justify animation budget to stakeholders
- scope reduced-motion support up front
Example prompts for the agent
- Help me prioritize animations for the new onboarding flow
- Build a motion roadmap: what ships first, what waits
- Which animation principles pay off in a B2B dashboard?
How to install product-manager
1Skills CLI (Vercel)
npx skills add dylantarre/animation-principles --skill product-manager -a claude-code2Manually: put the files in place
~/.claude/skills/product-manager/SKILL.mdCopy the whole skill folder; for one project use .claude/skills/product-manager/
1Skills CLI (Vercel)
npx skills add dylantarre/animation-principles --skill product-manager -a codex2Manually: put the files in place
.agents/skills/product-manager/SKILL.mdFor all projects use ~/.agents/skills/
1Skills CLI (Vercel)
npx skills add dylantarre/animation-principles --skill product-manager -a cursor2Manually: put the files in place
.cursor/skills/product-manager/SKILL.mdCursor also reads .agents/skills/ and .claude/skills/
1GitHub CLI
gh skill install dylantarre/animation-principles product-manager2Manually: put the files in place
.github/skills/product-manager/SKILL.md1Skills CLI (Vercel)
npx skills add dylantarre/animation-principles --skill product-manager -a gemini-cli2Platform CLI
gemini skills install https://github.com/dylantarre/animation-principles --path skills/03-by-role-persona/product-managerManually: put the files in place
.devin/skills/product-manager/SKILL.mdThe legacy .windsurf/skills/ path still works
Skills CLI (Vercel)
npx skills add dylantarre/animation-principles --skill product-manager -a opencodeClaude.ai
Zip the folder and upload it in Settings → Capabilities → Skills
Step by step, with commands for each platform: How to install skills in Claude Code: five ways
Questions about product-manager
How do I install product-manager in Claude?
Run npx skills add dylantarre/animation-principles --skill product-manager -a claude-code. The skill file lands at ~/.claude/skills/product-manager/SKILL.md.
What does product-manager do?
It runs animation features through the 12 principles and sorts them into must-have, should-have and nice-to-have. Each principle carries a business value note and a metric to track.
Which platforms does the skill support?
Besides Claude it installs into Codex, Cursor, GitHub Copilot, Gemini CLI and OpenCode — only the agent flag changes in the install command.
Source text
SKILL.md · MIT
--- name: product-manager description: Use when prioritizing animation features, building motion roadmaps, or when a PM needs to understand the business value of animation principles. --- # 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.
© dylantarre · MIT · dylantarre/animation-principles