Stimulus engine · Production guide

Immediate Impact UI: Design Fast, Satisfying Feedback

Make one input feel decisive without turning the whole screen into noise.

Original-design vocabularyAccessibility includedNo existing-IP imitation

6-second vertical specimen · 1080×1920 · 30 fps · no audio

Watch the interaction grammar

In the specimen, a central HIT target compresses, pauses, springs back, and emits a ring and debris. The next target remains visible.

Generation model and effort: not recorded. The production prompt below is reconstructed from the specimen and taxonomy; it is not the original generation prompt.

Build the sequence

  1. Tap, click, key press, hit, break, confirm, or clear. Reserve the strongest response for the primary action.
  2. Return the first state change immediately. Use an 80–120 ms hit stop only at the decisive moment, then recover quickly.
  3. Freeze the target and nearby particles, not navigation or assistive controls. The pause should clarify contact, not delay control.
  4. Invert the target, release one impact ring, add sparse debris, and pop the gain count once. Scale intensity with action importance.
  5. Use one short verb or result number. Hold it long enough to read; never cover the next required control.
  6. Prefer local recoil. If camera shake is essential, keep it brief, low amplitude, user-disableable, and absent in reduced-motion mode.
  7. Pair one transient with the contact and a lower recovery sound. Haptics should be optional, brief, and reserved for confirmed input.
  8. Keep the next actionable target visible before the recovery ends, so the rhythm continues without a manipulative countdown.

Production controls

Input

Tap, click, key press, hit, break, confirm, or clear. Reserve the strongest response for the primary action.

Timing

Return the first state change immediately. Use an 80–120 ms hit stop only at the decisive moment, then recover quickly.

Hit stop

Freeze the target and nearby particles, not navigation or assistive controls. The pause should clarify contact, not delay control.

Amplification

Invert the target, release one impact ring, add sparse debris, and pop the gain count once. Scale intensity with action importance.

Text

Use one short verb or result number. Hold it long enough to read; never cover the next required control.

Camera

Prefer local recoil. If camera shake is essential, keep it brief, low amplitude, user-disableable, and absent in reduced-motion mode.

Sound & haptics

Pair one transient with the contact and a lower recovery sound. Haptics should be optional, brief, and reserved for confirmed input.

Next expectation

Keep the next actionable target visible before the recovery ends, so the rhythm continues without a manipulative countdown.

Where it works—and where it fails

Good uses

  • Primary game actions and confirmed hits
  • Successful form submission or command completion
  • Short tutorial moments that teach cause and effect

Failure modes

  • Shaking every interaction until hierarchy disappears
  • Adding delayed particles before confirming the input
  • Letting numbers, debris, and camera motion obscure the next action

Accessibility

Provide reduced-motion behavior with color, shape, and text state changes instead of shake. Preserve focus, sufficient contrast, and a persistent textual result.

Manipulation boundary

Celebrate a completed action. Do not use the same intensity to pressure purchases, hide errors, or make repeated paid actions feel inevitable.

Creator-ready English prompt

Reconstructed prompt. Derived from the recorded specimen and classification data; not presented as the original prompt.

Produce a 6-second vertical UI motion sample that uses the Immediate Impact stimulus engine.
Repeated action: Tap, click, key press, hit, break, confirm, or clear. Reserve the strongest response for the primary action.
Opening state: Make the actionable state and its consequence readable before input.
Trigger and timing: Return the first state change immediately. Use an 80–120 ms hit stop only at the decisive moment, then recover quickly.
Hit stop: Freeze the target and nearby particles, not navigation or assistive controls. The pause should clarify contact, not delay control.
Amplification: Invert the target, release one impact ring, add sparse debris, and pop the gain count once. Scale intensity with action importance.
Text: Use one short verb or result number. Hold it long enough to read; never cover the next required control.
Camera: Prefer local recoil. If camera shake is essential, keep it brief, low amplitude, user-disableable, and absent in reduced-motion mode.
Sound and haptics: Pair one transient with the contact and a lower recovery sound. Haptics should be optional, brief, and reserved for confirmed input.
Next promise: Keep the next actionable target visible before the recovery ends, so the rhythm continues without a manipulative countdown.
Accessibility: Provide reduced-motion behavior with color, shape, and text state changes instead of shake. Preserve focus, sufficient contrast, and a persistent textual result.
Ethical boundary: Celebrate a completed action. Do not use the same intensity to pressure purchases, hide errors, or make repeated paid actions feel inevitable.
Keep enough contrast for text and primary UI, and make the meaning clear in reduced-motion and no-audio settings.
Create original abstract subjects. Do not imitate existing works, characters, logos, brands, or proprietary UI.
Open this engine in the Prompt Workshop

Continue art direction

Recommended expression themeView the generated specimenCompare all 13 engines