Keep the user anchored to the action they just took, then confirm the result without forcing a page-level transition. Avoid: Avoid full-screen loading for small form actions unless the whole page is blocked.

Skeletons preserve layout context and make the wait feel shorter than an isolated spinner. Avoid: Avoid skeletons when the final layout is unpredictable or the fetch usually completes instantly.

Search needs fast input affordance, lightweight loading feedback, and a graceful zero-result state. Avoid: Avoid decorative search animations on search-first pages where the input should always be visible.

Uploads need measurable progress when possible, then clear success or retry feedback. Avoid: Avoid fake percentage progress if the system cannot estimate completion.

Guide attention only when the next action is important enough to interrupt the normal interface. Avoid: Avoid highlighting many elements at once or repeating the same tour after acknowledgement.

Data motion should clarify what changed: trend shape, category comparison, distribution, or headline metric. Avoid: Avoid animating every chart on dense dashboards or delaying access to values users need immediately.

Reading progress should orient users without competing with the content itself. Avoid: Avoid scroll progress bars on short pages or apps with multiple nested scroll containers.

Small tactile bursts can make playful actions feel responsive without showing a full notification. Avoid: Avoid spark effects for serious, destructive, or high-frequency actions.

Expressive navigation should still preserve clear selected state and stable targets. Avoid: Avoid blob or dock effects when users need dense, predictable enterprise navigation.

A slider can use motion to make value changes feel tactile while keeping the exact value readable. Avoid: Avoid elastic handles when users need high-precision numeric entry.

A reveal motion should clarify the relationship between a compact container and the content inside it. Avoid: Avoid metaphorical reveals when the grouping is not real or when content should be immediately visible.

Creative hero motion should make the product, message, or atmosphere more tangible instead of adding a generic visual effect. Avoid: Avoid abstract 3D, particles, or headline effects when users need dense reading, form completion, checkout, or admin work.

Expose truthful observable activity first, then use ambient AI expression only as a supporting state. Avoid: Avoid vague thinking loops when precise progress, errors, privacy, or accountable tool states matter.

Errors should point to the exact fix before using broad page-level motion. Avoid: Avoid playful motion for destructive, financial, or security-sensitive failures.

Use skeleton for layout context; add shimmer only when the placeholder would otherwise feel static during a longer wait.

Use spinner for short or unknown waits; use progress bar when completion is measurable or the wait is long.

Use toast for non-blocking confirmation; use a success screen when completion changes the user journey.

Use scale for quiet button feedback, ripple for material-style surfaces, and haptic bounce for playful mobile-first actions.

Use fade for simple state changes; use shared element transitions when preserving object continuity matters.

Use active pill slide for segmented controls and filter chips, tab underline for navigation tabs, and fade for the content change that follows selection.

Use popover coach step when text guidance is needed, focus ring highlight when the control only needs attention, and spotlight coach mark when the whole surrounding UI should recede.

Use line chart draw for trends, pie chart reveal for simple distribution, and chart bar growth when category comparison must be more precise.

Use notification dot pulse for ambient newness, toast for readable confirmation, and badge count animation when the number itself matters.

Use click spark for playful reward, ripple for material-style surface feedback, and scale on press for quiet universal tactility.

Use gooey nav for playful route selection, active pill for product controls, and dock proximity scale for compact icon launchers.

Use bubble menu for a few compact actions, card nav for destination groups with context, and staggered menu for short link lists.

Use folder reveal when the storage/grouping metaphor is real, accordion for normal disclosure, and popover when the content is guidance rather than nested material.

Use atmosphere when mood supports the message; use product objects when users need to understand what the product is. Do not let background motion carry critical meaning.

Use an orb for ambient presence, a timeline for observable agent work, and indeterminate progress for unknown waits without fabricated detail.

Use particle networks for subtle system atmosphere, knowledge graphs for real relationships, and orbital systems for high-level feature ecosystems.

Use scroll stack for short narrative sequences, timeline reveal for dated or milestone order, and stagger list reveal for ordinary unordered content.

Disable the submitted button, show local progress, then confirm with a toast or success view depending on task importance.

Show structure while data loads, hand off to staggered content reveal, and handle the empty result without feeling broken.

Make search available, indicate fast querying, then distinguish result reveal from a true no-result state.

Prefer real progress, fall back to indeterminate motion only when progress is unknown, then show clear completion or retry feedback.

Explain the current step, highlight the exact control, show sequence progress, and make completion visibly accumulate.

Reveal the headline metric, draw the trend, compare categories, and then show the ordered milestones behind the change.

Use target-aware hover, tactile click reward, a stylized reveal, and ambient social proof only on pages where personality is part of the product.

Expose grouped destinations with card nav, use short staggered lists for compact menus, and preserve selected state with an active indicator.

Orient the reader with scroll progress, reveal a short stacked sequence, then use a timeline when the order becomes milestone-based.

Open with one strong message, make the product tangible, reveal feature depth only when it preserves scanning, and use path drawing for meaningful journeys or diagrams.

Show accountable tool states first, explain relationships when they are the product value, reserve flow visuals for real pipelines, and keep AI orbs as ambient status only.

Give the tap a small press response, slide the selected pill to preserve state continuity, then fade the content into the newly selected result.