Overview
Interaction specifications fail when they describe what an animation looks like rather than how it behaves. "Smooth fade-in" is not a specification. It is a preference that every engineer interprets differently, producing implementations that range from a 100ms opacity transition to a 600ms blur-and-scale sequence — none of which is what the designer intended.
The Interaction Design Specification Prompt builds specifications that are unambiguous to an engineer who has never seen the prototype — with exact timing values, named easing curves, trigger conditions, and the edge cases that determine whether the interaction degrades gracefully or breaks visibly.
What you get: - Trigger-action-feedback model: the three-part structure that makes every interaction specification complete - Timing specification format: the exact values and units that eliminate interpretation - Easing curve library: the named curves that map to CSS easing functions without conversion - State transition map: the complete set of states and the interactions that move between them - Edge case specification: the behaviors that only appear under specific conditions - Handoff format: the specification document structure that engineers can implement without a walkthrough
Built for: product designers and interaction designers writing specifications for engineering implementation in web and mobile products.