timing-principle-mastery
Use when determining animation durations, controlling pacing, establishing rhythm, or making motion feel appropriately weighted and emotionally resonant.
What this skill does
# Timing Mastery ## The Weight of Time Timing is the number of frames (or milliseconds) an action takes. It's deceptively simple—just duration—yet it communicates weight, emotion, and energy more powerfully than any other principle. Change the timing, change the meaning. ## Core Theory **Physical communication**: Timing tells us about mass and force. Heavy objects start slow, stop slow. Light objects respond instantly. A bowling ball and a balloon falling the same distance—timing alone differentiates them. **Emotional communication**: Timing tells us about character state. Sluggish timing reads as tired, depressed, or massive. Snappy timing reads as alert, nervous, or lightweight. ## The Frame Rate Foundation At 24fps (film standard): - 1-2 frames: Instantaneous (impacts, pops) - 4-6 frames: Quick (snappy responses) - 8-12 frames: Standard (natural movement) - 16-24 frames: Deliberate (weighted, considered) - 24-48 frames: Slow (dramatic, heavy) - 48+ frames: Very slow (massive, underwater, dream-like) At 60fps (UI/games), multiply by 2.5 for equivalent feels. ## Timing Categories **Physical timing**: Governed by mass, gravity, and force (objective) **Theatrical timing**: Governed by story needs and emotional beats (subjective) **Musical timing**: Governed by rhythm and tempo (structural) **UI timing**: Governed by responsiveness and user perception (functional) ## Interaction with Other Principles **Slow in/slow out is timing's texture**: The overall duration and the internal spacing work together. **Anticipation affects timing perception**: A long wind-up makes subsequent action feel faster. **Staging uses timing for hierarchy**: Important elements move on different timing than subordinate ones. **Exaggeration often means timing exaggeration**: Stretched holds, compressed actions. ## Domain Applications ### UI/Motion Design - **Instant (0-100ms)**: Button feedback, toggle switches—no perceptible delay - **Quick (100-200ms)**: Micro-interactions, hover states—responsive but visible - **Standard (200-300ms)**: Page transitions, modals—comfortable, comprehensible - **Deliberate (300-500ms)**: Complex transitions, onboarding—time to absorb - **Slow (500ms+)**: Dramatic reveals, ambient animation—contemplative ### Character Animation - **Personality through timing**: Bouncy = fast timing; grumpy = slow timing - **Mass through timing**: Elephant walk = 24+ frames per step; mouse = 4-6 frames - **Emotional state**: Depression slows timing; excitement speeds it - **Age indication**: Young = snappy recovery; old = slow, deliberate ### Motion Graphics - **Rhythm establishment**: Consistent timing creates beat - **Contrast through timing**: Slow builds, fast reveals - **Musical sync**: Animation locked to audio tempo ### Game Design - **Responsiveness**: Input-to-response timing defines "game feel" - **Hit stop**: Momentary pause on impact (adds weight) - **Juice**: Quick, satisfying timing on feedback events ## Common Mistakes 1. **Uniform timing**: Everything same duration feels monotonous 2. **Too fast**: Motion becomes invisible, jerky, unpleasant 3. **Too slow**: Interface feels sluggish, unresponsive 4. **Ignoring context**: Casual game timing in enterprise software ## The Timing Contrast Principle Timing gains meaning through contrast. A fast action feels fast because something before it was slow. A held pose feels dramatic because motion surrounds it. Monotonous timing lacks emphasis. ## The Duration Hierarchy Create timing systems where relationships are consistent: - Base unit (e.g., 200ms) - Quick = base × 0.5 (100ms) - Slow = base × 1.5 (300ms) - Dramatic = base × 2 (400ms) Systematic timing feels cohesive; random durations feel chaotic. ## The Hold One of timing's most powerful tools is the absence of motion. Held poses create: - Emphasis (letting a moment land) - Anticipation (pregnant pause before action) - Readability (time for audience to register) Never underestimate the power of stillness. ## Implementation Heuristic Start with 200-300ms as default duration for standard interactions. Adjust based on: mass (heavier = longer), distance (further = longer), importance (crucial = longer to register), emotional tone (playful = snappier). When something feels "off," timing is often the culprit—experiment with 50% shorter and 50% longer before other adjustments.
Related in General
modeling-omnistudio-epc-catalog
IncludedSalesforce Industries CME EPC product-modeling skill for Product2-based catalog creation. Use when creating EPC products, configuring product attributes, building offer bundles with Product Child Items, or reviewing EPC DataPack JSON metadata for product catalog changes. TRIGGER when: user creates or updates Product2 EPC records, AttributeAssignment payloads, AttributeMetadata/AttributeDefaultValues, Offer bundles, or ProductChildItem relationships. DO NOT TRIGGER when: designing OmniScripts/FlexCards/Integration Procedures (use building-omnistudio-omniscript, building-omnistudio-flexcard, or building-omnistudio-integration-procedure), implementing Apex business logic (use generating-apex), or troubleshooting deployment pipelines (use deploying-metadata).
relationship-science-coach
IncludedUse this skill for direct, practical adult relationship coaching: couples conflict, repair, trust, marriage, dating, flirting, attachment patterns, emotional connection, sex, desire differences, eroticism, kink negotiation, affection, love languages, breakups, and long-term passion. Draw on Gottman, EFT and Hold Me Tight, attachment science, modern sex research, Perel, Nagoski, Kerner, Schnarch, Love and Stosny, and flexible love-language tools. Be concrete and low-hedge. Redirect only for imminent danger, abuse, coercive control, minors, non-consent, self-harm, stalking, or medical/legal/psychiatric decisions.
building-sf-integrations
IncludedSalesforce integration architecture and runtime plumbing with 120-point scoring. Use this skill to set up Named Credentials, External Credentials, External Services, REST/SOAP callout patterns, Platform Events, and Change Data Capture. TRIGGER when: user sets up Named Credentials, External Services, REST/SOAP callouts, Platform Events, CDC, or touches .namedCredential-meta.xml files. DO NOT TRIGGER when: Connected App/OAuth config (use configuring-connected-apps), Apex-only logic (use generating-apex), or data import/export (use handling-sf-data).
venue-templates
IncludedAccess comprehensive LaTeX templates, formatting requirements, and submission guidelines for major scientific publication venues (Nature, Science, PLOS, IEEE, ACM), academic conferences (NeurIPS, ICML, CVPR, CHI), research posters, and grant proposals (NSF, NIH, DOE, DARPA). This skill should be used when preparing manuscripts for journal submission, conference papers, research posters, or grant proposals and need venue-specific formatting requirements and templates.
let-fate-decide
IncludedDraws the 12 Houses of the Zodiac Tarot spread to inject entropy into planning when prompts are vague, ambiguous, or casually delegated. Interprets the spread to guide next steps. Use when the user says 'let fate decide', 'YOLO', 'whatever', 'idk', or other nonchalant phrases, makes Yu-Gi-Oh references, or when you are about to arbitrarily pick between multiple reasonable approaches. Prefer over ask-questions-if-underspecified when the user's tone is casual or playful rather than precision-seeking.
net-ops
IncludedCross-platform network troubleshooting (Windows, macOS, Linux) via local or remote shell. Use for: DNS broken, can't resolve hostnames, nslookup/dig works but apps fail, NRPT, WFP, scutil, /etc/resolver, systemd-resolved, /etc/resolv.conf, NetworkManager, VPN DNS leak residue (ProtonVPN/Mullvad/WireGuard/AnyConnect), AV/firewall blocking DNS or DoH, Tailscale DNS interaction, intermittent connectivity, remote diagnostics over SSH.