Use when designing interface states, feedback, hover/focus/press, gestures, direct manipulation, navigation transitions, loading/error/empty behavior, or deciding where interaction should carry the design concept.
The English summary is being prepared. Showing the original description.
See how to installReview the instructions the agent will receive before you install.
For every interactive element define:
Animation is justified when it improves at least one:
If none apply, remove it.
Per viewport, prefer:
Do not animate every section entrance. Repetition destroys salience.
Design one interaction that expresses the brand or product concept. Make it optional to task completion and give it a reduced-motion equivalent.
Never make hover the only way to discover essential content. Drag-only functionality requires a non-drag single-pointer alternative where required by the accessibility baseline.
For product flows, read references/product-edge-cases.md before release and cover the states that apply; a polished happy path is not a complete interaction model.
No reviews yet. Tell others what you thought.
No login needed. Share how it worked for you, ask a question, or note where it did not run.
No comments yet. Be the first to write one.
Use for release-level accessibility and performance review, including WCAG 2.2 AA, keyboard/focus, target size, reduced motion, semantic controls, Core Web Vitals, images/fonts/JavaScript, and animation or 3D performance budgets.
The English summary is being prepared. Showing the original description.
Use to audit a generated or heavily templated interface for generic AI aesthetics, unjustified trend patterns, component-registry residue, vague copy, repetitive motion, novelty theater, or visual decisions that lack brand/UX rationale.
The English summary is being prepared. Showing the original description.
Use when a website needs a strong visual point of view, distinct concept routes, composition, typography, color/materiality, imagery direction, spatial rhythm, or a memorable signature idea.
The English summary is being prepared. Showing the original description.
Use when deciding whether to implement UI from native HTML/CSS, accessible primitives, shadcn-style source components, or visual component registries such as 21st.dev, Aceternity, React Bits, Motion Primitives, Magic UI, or Animate UI.
The English summary is being prepared. Showing the original description.
Use after substantial web projects or repeated design defects to convert evidence into reusable skill improvements through root-cause analysis, regression scenarios, and controlled proposals without silently changing the core OS.
The English summary is being prepared. Showing the original description.
Use when the design concept calls for Three.js or React Three Fiber 3D, WebGL/WebGPU, Rive, Spline, Theatre.js, SVG, canvas, shaders, particle systems, or other immersive creative-web techniques.
The English summary is being prepared. Showing the original description.