Skip to main content
skill CX Codex

trust-reliability — Claude Code skill: animations that build trust

A skill for animations that make interfaces feel dependable: predictable motion, steady timing, no surprises. Useful for payments, forms and settings.

Install into Claude Code · Skills CLI (Vercel) All methods and platforms ↓
npx skills add dylantarre/animation-principles --skill trust-reliability -a claude-code
Open on GitHub

What trust-reliability does

The skill lays out how to animate interfaces so they don't unsettle people. It takes the classic animation principles and applies them to UI: minimal squash & stretch (5-10%), brief anticipation (50-100ms), symmetrical ease-in-out. Motion should read as solid, not rubbery.

Inside there's a timing table by element type: transitions 250-350ms, feedback 150-200ms, modals 200-300ms, loading runs linear. Three CSS variables are defined: --trust-smooth, --trust-enter, --trust-exit. A separate set of consistency rules keeps things steady — the same action always gets the same animation, duration variance stays within ±50ms, and random timing is out.

The skill advises against straight ahead action in favour of pose-to-pose, since the result is more controlled. It also asks you to respect system motion preferences and degrade gracefully when animation is off. If your project has drifting timings and every screen moves at its own pace, that's a reason to check consistency first.

What it helps with

  • make a payment flow animate calmly and predictably
  • align transition and modal timings to one scale
  • remove random durations from repeated actions
  • handle graceful degradation when motion is disabled
  • pick easing for user feedback responses

Example prompts for the agent

  • Review the checkout animation against the trust-reliability skill
  • Make modal transitions follow trust-reliability
  • Align the settings screen animations with trust-reliability

How to install trust-reliability

1Skills CLI (Vercel)

npx skills add dylantarre/animation-principles --skill trust-reliability -a claude-code

2Manually: put the files in place

~/.claude/skills/trust-reliability/SKILL.md

Copy the whole skill folder; for one project use .claude/skills/trust-reliability/

Step by step, with commands for each platform: How to install skills in Claude Code: five ways

Questions about trust-reliability

How do I install trust-reliability in Claude?

Run npx skills add dylantarre/animation-principles --skill trust-reliability -a claude-code. The skill lands at ~/.claude/skills/trust-reliability/SKILL.md.

What does trust-reliability do?

It sets rules for trust-building animation: moderate durations, symmetrical easing, minimal deformation, and identical behaviour for identical actions.

Which platforms support the skill?

Besides Claude, it installs into Codex, Cursor, GitHub Copilot, Gemini CLI and OpenCode, each with its own install command.

Source text

SKILL.md · MIT
---
name: trust-reliability
description: Use when creating animations that build user confidence, establish credibility, and communicate dependability.
---

# Trust & Reliability Animation

Create animations that establish confidence, consistency, and dependable user experiences.

## Emotional Goal

Trust develops through predictable, controlled movements that respect user expectations. Reliability means animations behave consistently and never surprise negatively.

## Disney Principles for Trust

### Squash & Stretch
Minimal stretch (5-10% maximum). Controlled deformation shows stability. Elements should feel solid and grounded, not rubbery.

### Anticipation
Subtle but present (50-100ms). Brief preparation signals what's coming without surprises. Users should always know what to expect next.

### Staging
Clear, unambiguous presentation. One action at a time. Important elements are obvious. No hidden or confusing movements.

### Straight Ahead Action
Avoid for trust-building. Prefer pose-to-pose for predictable, controlled results. Every frame should be intentional.

### Follow Through & Overlapping Action
Restrained follow-through. Elements settle quickly without excessive bouncing. Professional, controlled completion of movements.

### Slow In & Slow Out
Smooth, symmetrical easing. `ease-in-out` creates predictable, professional motion. No sudden accelerations or jarring stops.

### Arc
Gentle, predictable curves. Consistent arc patterns across similar interactions. Avoid erratic or unexpected paths.

### Secondary Action
Minimal and purposeful. Supporting animations should reinforce, not distract. Loading indicators should be calm and steady.

### Timing
Moderate, consistent timing (250-400ms). Never too fast (feels rushed) or too slow (feels broken). Same elements should always animate at same speed.

### Exaggeration
Very minimal (5-10%). Near-realistic movements feel professional and trustworthy. Subtle refinement over dramatic effect.

### Solid Drawing
Maintain perfect proportions. No warping or distortion. Elements should feel stable and well-constructed.

### Appeal
Clean, balanced designs. Symmetry suggests stability. Professional aesthetics over playful charm.

## Timing Recommendations

| Element | Duration | Easing |
|---------|----------|--------|
| Transitions | 250-350ms | `ease-in-out` |
| Feedback | 150-200ms | `ease-out` |
| Loading | Continuous | `linear` |
| Modals | 200-300ms | `ease-out` |

## CSS Easing

```css
--trust-smooth: cubic-bezier(0.4, 0, 0.2, 1);
--trust-enter: cubic-bezier(0, 0, 0.2, 1);
--trust-exit: cubic-bezier(0.4, 0, 1, 1);
```

## Consistency Rules

1. Same action = same animation, always
2. Duration variance: maximum ±50ms
3. No random or variable timing
4. Respect system motion preferences
5. Graceful degradation when disabled

## When to Use

- Financial transactions and payments
- Form submissions and data entry
- Authentication flows
- Settings and configuration
- Progress indicators
- Confirmation dialogs
- Enterprise applications

© dylantarre · MIT · dylantarre/animation-principles

Similar skills

Everything for Frontend and UI →

From the same set86

Project sponsors

Companies that keep this analytics open
Gold sponsor

Impressions, clicks and code copies — open statistics. We keep the numbers public for the same reason NeBlask itself is public. Become a sponsor