anticipation-mastery

Use when designing action sequences, user interactions, state transitions, or any motion that needs telegraphing to feel intentional rather than sudden.

16 stars

Best use case

anticipation-mastery is best used when you need a repeatable AI agent workflow instead of a one-off prompt.

Use when designing action sequences, user interactions, state transitions, or any motion that needs telegraphing to feel intentional rather than sudden.

Teams using anticipation-mastery should expect a more consistent output, faster repeated execution, less prompt rewriting.

When to use this skill

  • You want a reusable workflow that can be run more than once with consistent structure.

When not to use this skill

  • You only need a quick one-off answer and do not need a reusable workflow.
  • You cannot install or maintain the underlying files, dependencies, or repository context.

Installation

Claude Code / Cursor / Codex

$curl -o ~/.claude/skills/anticipation-mastery/SKILL.md --create-dirs "https://raw.githubusercontent.com/diegosouzapw/awesome-omni-skill/main/skills/design/anticipation-mastery/SKILL.md"

Manual Installation

  1. Download SKILL.md from GitHub
  2. Place it in .claude/skills/anticipation-mastery/SKILL.md inside your project
  3. Restart your AI agent — it will auto-discover the skill

How anticipation-mastery Compares

Feature / Agentanticipation-masteryStandard Approach
Platform SupportNot specifiedLimited / Varies
Context Awareness High Baseline
Installation ComplexityUnknownN/A

Frequently Asked Questions

What does this skill do?

Use when designing action sequences, user interactions, state transitions, or any motion that needs telegraphing to feel intentional rather than sudden.

Where can I find the source code?

You can find the source code on GitHub using the link provided at the top of the page.

SKILL.md Source

# Anticipation Mastery

## The Setup Principle

Anticipation prepares the audience for action. Discovered through theatrical observation, Disney animators found that without a preparatory movement, actions appeared to happen "out of nowhere"—confusing rather than exciting. The principle: before any significant action, there must be a counter-movement.

## Core Theory

**Newton's Third Law, Visualized**: Physical actions require preparation. A pitcher winds up before throwing. A cat crouches before pouncing. Anticipation makes this mechanical necessity visible and dramatic.

**Attention Direction**: Anticipation tells viewers where to look and what to expect. It transforms surprise into suspense—a more engaging emotional state.

## The Three Functions

1. **Physical preparation**: The body must coil to spring (jumping, throwing, punching)
2. **Mental preparation**: The audience needs time to register incoming action
3. **Emotional preparation**: Building tension before release amplifies impact

## Timing Dynamics

**Duration signals magnitude**: Brief anticipation (2-4 frames) for small actions. Extended anticipation (12-24 frames) for major moments. A full second of wind-up tells viewers something significant is coming.

**Inverse proportion**: The bigger the anticipation, the faster the following action can be while remaining readable.

## Interaction with Other Principles

**Staging depends on anticipation**: The preparatory pose directs attention to where action will occur.

**Timing is defined by anticipation ratio**: Classic formula is 1:2—one beat of anticipation for two beats of action.

**Squash/stretch often appears here**: Characters compress before explosive movement.

**Exaggeration amplifies anticipation**: Cartoon wind-ups exceed physical possibility for comedic effect.

## Domain Applications

### UI/Motion Design
- Button hover states: subtle scale-up anticipates the click response
- Page transitions: brief pause or micro-movement before navigation
- Loading states: pulsing or winding animation before content appears
- Drag interactions: slight resistance before element "releases"

### Character Animation
- Jump preparation: full crouch with held pose before launch
- Punch delivery: shoulder rotation backward before forward strike
- Emotional shifts: beat of stillness before reaction

### Micro-interactions
- Toggle switches: brief compression before snap to new state
- Notifications: subtle entrance from off-screen before settling
- Tooltips: micro-delay with subtle scale from origin point

### Game Design
- Attack wind-ups: readable tells that allow player response
- Ability charging: visual buildup matching power accumulation
- Boss patterns: exaggerated anticipation creates learnable mechanics

## Common Mistakes

1. **Skipping anticipation entirely**: Actions feel robotic and sudden
2. **Over-anticipating minor actions**: Creates sluggish, over-animated feel
3. **Wrong direction**: Anticipation must oppose the action direction
4. **Uniform timing**: Vary anticipation length based on action importance

## The Reversal Technique

For comedic or surprising effect, violate anticipation expectations. Long wind-up followed by tiny action. No wind-up before massive action. The principle's power is proven by how jarring its absence feels.

## Implementation Heuristic

Every action above 200ms duration should have anticipation. Scale anticipation duration to 30-50% of the main action. When actions feel "empty," anticipation is usually missing.

Related Skills

skill-protocol-mastery

16
from diegosouzapw/awesome-omni-skill

This skill should be used when the user asks to "create a skill", "write a SKILL.md", "validate skill structure", "improve skill description", "understand skill protocol", "design skill architecture", or needs guidance on progressive disclosure, trigger phrases, writing style, or skill validation for Claude Code.

anticipation-payoff

16
from diegosouzapw/awesome-omni-skill

Use when designing action sequences, gags, reveals, or any motion that needs setup before delivery—preparing audiences for what's coming and maximizing impact.

javascript-mastery

16
from diegosouzapw/awesome-omni-skill

Comprehensive JavaScript reference covering 33+ essential concepts every developer should know. From fundamentals like primitives and closures to advanced patterns like async/await and functional p...

deepseek-code-mastery

16
from diegosouzapw/awesome-omni-skill

Referencia completa para operar DeepSeek Code (1M tokens por chat via web, open source, sin expiracion) como sistema multi-agente subordinado a Claude Code. v4.2 certificado — Serena auto-init en agent mode (3 tools de code intelligence sin intervencion manual), quantum merge con deduplicacion de clases ES6 (extract_classes + pick_better_implementation, strategy function_based), skills_dir fallback automatico en orchestrator, Phase 2 token tracking real. Token-Efficient Pipeline (save_response.py directo a disco, ~96% ahorro), Semantic Engine central (TF-IDF, cosine similarity, Bayesian Beta, temporal decay, Mann-Kendall), Skills por similaridad semantica, memoria dual (surgical + global), Intelligence Package (5 features), dual quantum sessions, multi-step, multi-session, converse, y protocolo de sesiones 3-fases. Usar cuando el usuario pida delegar codigo, generar funciones, crear features, o cualquier tarea de generacion masiva.

bgo

10
from diegosouzapw/awesome-omni-skill

Automates the complete Blender build-go workflow, from building and packaging your extension/add-on to removing old versions, installing, enabling, and launching Blender for quick testing and iteration.

Coding & Development

web-design-guidelines

16
from diegosouzapw/awesome-omni-skill

Review UI code for Web Interface Guidelines compliance. Use when asked to "review my UI", "check accessibility", "audit design", "review UX", or "check my site against best practices".

voxanne-branding-expert

16
from diegosouzapw/awesome-omni-skill

Strategic branding, business development, and UI/UX design expertise for Voxanne AI. Combines business strategy, visual design principles, and market positioning to create enterprise-grade branding assets and go-to-market strategies. Use when designing logos, creating brand guidelines, developing marketing strategies, or positioning products against competitors like ChatGPT, Anthropic, and Google.

vibe-techdesign

16
from diegosouzapw/awesome-omni-skill

Create a Technical Design Document for your MVP. Use when the user wants to plan architecture, choose tech stack, or says "plan technical design", "choose tech stack", or "how should I build this".

vapor-ui

16
from diegosouzapw/awesome-omni-skill

Vapor UI design system component and icon guide, UI mockup generator, and Figma design converter. Provides component catalog, icon lookup, usage patterns, props documentation, and converts Figma designs to production-ready vapor-ui code. Use when user asks "vapor-ui components", "vapor-ui icons", "아이콘 찾기", "vapor-ui 사용법", "vapor-ui를 사용해서 시안 구현", "convert figma", "figma to code", "implement design from figma", provides a Figma URL, or mentions specific components like "Button", "Input", "Modal".

ux-visualizer

16
from diegosouzapw/awesome-omni-skill

Analyzes source code or requirements to generate high-fidelity screen and state transition diagrams. Specialized in SPA state mapping.

ux-ui-exp

16
from diegosouzapw/awesome-omni-skill

UI/UX design intelligence with Bootstrap 5, Font Awesome, SweetAlert2. Use: /ux-ui-exp {command}

ux-spec-author

16
from diegosouzapw/awesome-omni-skill

Converts UX/design intent into testable design specifications that feed requirements. Use when defining user flows, accessibility, or design constraints.