unity-visual-feedback

Unity Visual Feedback Designer

Make every action readable and every moment feel alive — through clarity, feedback, animation, and polish

When to Use This Skill

• Designing feedback for a specific player action (jump, attack, interact, fail)
• Diagnosing why a scene feels unclear or actions feel unresponsive
• Defining animation states and their emotional intent
• Adding juice and polish without breaking clarity or performance
• Deciding what UI the game needs and how to present it

Design the mechanic first using unity-mechanics (this plugin). Design level visual atmosphere using unity-level (this plugin). Design audio response using unity-audio (this plugin).

Feedback Ownership

This skill starts the feedback design chain for any player action. It owns the visual layer: animation, particles, screen effects, state changes, and UI. The audio layer is designed in unity-audio. Neither skill alone covers "action feel" — both are required.

Workflow order: unity-mechanics (mechanic works?) → unity-visual-feedback (visual response) → unity-audio (audio response). Always design visual feedback before audio — the visual establishes timing and intensity that audio must match.

---

Core Philosophy

"If an action matters, it must feel noticeable."

Every mechanic the player uses must produce a feedback response that communicates: that worked or that didn't work. Silent actions erode trust in the controls.

"If the player misses it, it doesn't exist."

Visual hierarchy is not decoration. An interactive object that blends into the background is a broken design. Clarity is a higher priority than beauty.

Feedback Before Polish

Apply layers in order. A scene with no clarity cannot be rescued by juice. A feedback system that is ambiguous cannot be fixed by screen shake.

---

Five-Layer Workflow

Apply in this order — each layer depends on the one before:

Layer 1 — VISUAL CLARITY      Can the player read the scene?
Layer 2 — FEEDBACK SYSTEMS    Does every action communicate its result?
Layer 3 — ANIMATION           Does movement convey emotion and intent?
Layer 4 — JUICE               Does every satisfying action feel satisfying?
Layer 5 — UI / UX             What UI is necessary and how should it be presented?