Transformation UI Sequence: Stage a Clear State Change

Build the sequence

1. Activate a mode, reach a threshold, equip a system, or confirm a state change. Display the activation condition before it triggers.
2. Confirm activation first, gather parts in distinct beats, pulse the core once, and hold the completed silhouette before showing capability.
3. Pause at completion, not during control-critical setup. First-view sequences may be fuller; repeat views need a skip or shortened path.
4. Increase coherence rather than particle count: separated pieces align, gauges synchronize, and the final outline becomes stable.
5. Use an original system name and one explicit state label. Keep status, duration, and exit condition visible after the spectacle.
6. Use controlled convergence toward the core and a modest completion push-in. Avoid spinning or full-screen flashes.
7. Assign one timbre to assembly, one pulse to completion, and an optional haptic at confirmed activation. Never require sound to understand state.
8. After completion, show the released ability, remaining duration, and how to leave or reactivate the state.

Production controls

Where it works—and where it fails

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 Transformation Release stimulus engine.
Repeated action: Activate a mode, reach a threshold, equip a system, or confirm a state change. Display the activation condition before it triggers.
Opening state: Make the actionable state and its consequence readable before input.
Trigger and timing: Confirm activation first, gather parts in distinct beats, pulse the core once, and hold the completed silhouette before showing capability.
Hit stop: Pause at completion, not during control-critical setup. First-view sequences may be fuller; repeat views need a skip or shortened path.
Amplification: Increase coherence rather than particle count: separated pieces align, gauges synchronize, and the final outline becomes stable.
Text: Use an original system name and one explicit state label. Keep status, duration, and exit condition visible after the spectacle.
Camera: Use controlled convergence toward the core and a modest completion push-in. Avoid spinning or full-screen flashes.
Sound and haptics: Assign one timbre to assembly, one pulse to completion, and an optional haptic at confirmed activation. Never require sound to understand state.
Next promise: After completion, show the released ability, remaining duration, and how to leave or reactivate the state.
Accessibility: Provide skip, pause, reduced-motion, and non-flashing variants. State changes need persistent text and shape cues; avoid rapid flashes and vestibular camera motion.
Ethical boundary: Use transformation to clarify a chosen state. Do not disguise consent, lock users into a mode, or make exit controls hard to find.
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.

Continue art direction