Index of every page on this site: llms.txt
All skills
dylantarre avatar

/product-manager

@8359713
Run it yourself

Use when prioritizing animation features, building motion roadmaps, or when a PM needs to understand the business value of animation principles.

Use this Skill: https://skilld.dev/gh/dylantarre/animation-principles/product-manager

Nothing lands on disk. Nothing to clean up.

Fork this Skill

Edit a local copy. It keeps the author and licence.

SKILL.md

≈40 tokens for metadata: the name and description. ≈818 when used: this file.

Description uses 2.0% of example budget

Before choosing a Skill, your Agent reads its name and description. All available Skills share that space.

  • A shorter description leaves more room for other Skills. This entry exceeds our 1% size suggestion.

In our Claude Code example, all Skill names and descriptions share 8,000 characters. This Skill uses ≈162 characters, or 2.0%.

The 1% threshold is a size suggestion. Longer descriptions can still fit.

Your model, settings, and other Skills decide how much text your Agent can read.

Example settings and source

The example uses a 200k-token context and default Claude Code settings. The count includes the name, description, separators, and when_to_use when present. Codex also counts local file paths.

Skit's source and limits: Codex 0.160.1, Claude Code 2.1.292.

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.

Source: SKILL.md on GitHub

No rule matched.

skilld matched fixed text patterns in SKILL.md and file names. Patterns miss obfuscated code.

skilld run checks every file with the same patterns. It asks for approval before it loads a Skill with a behavior marked Needs approval.

1 warning2mo5 checks · Risk SAFE
  • Gen Agent Trust Hub2mo

    This skill is a pure documentation resource for product managers regarding animation principles. It contains no executable code, network connections, or security risks.

  • Socket2mo

    No alerts

  • Snyk2mo

    Risk: LOW · No issues

  • Runlayer9mo

    1/1 file flagged

  • ZeroLeaks7mo

    Score: 93/100 · 2 sections analyzed

Signed by skilld at 8359713. This ties the file your Agent reads to that commit on GitHub. It does not review the instructions.

Last checked against GitHub last month.

Dormantupdated 11 months ago

README badge

README badge for dylantarre/animation-principles/product-manager