What problem does it solve?
Interfaces often pass usability tests but feel cold and mechanical to users. This Skill diagnoses technically correct but emotionally flat UIs and prescribes concrete changes at the copy, motion, and interaction layers so the product acknowledges how the person actually feels.
Core Features & Use Cases
- Felt-State Translation Process: A four-step method that names the user's emotional state, finds a physical-world analogue, extracts behavioral properties (weight, resistance, rhythm), and maps them to interface layers like easing curves, delays, and copy tone.
- Emotional Timing & Motion Guidance: Concrete rules for information weight, error recovery spacing (300–600ms), celebration arcs, easing semantics, spring physics, and animation durations (150–600ms).
- Copy Voice by State: A reference table defining voice for loading, empty, user-error, system-error, success, and onboarding states.
- Use Case: A settings flow tests fine in usability sessions but users describe it as cold. Run this Skill to audit each state, rewrite error copy so the system owns its failures, and retune transitions so confirmations feel warm rather than mechanical.
Quick Start
Review this screen flow and tell me where the interface ignores the user's emotional state, then prescribe copy and motion changes for each moment.