← Back to templates

Web motion

Interaction feedback for buttons and cards

Make hover, pressed, loading and success states consistent.

Your inputs

Requested output

A reusable component and configuration integrated into the existing repository, required styles or shaders, a runnable demo, a list of changed files, validation results and known limitations.

Original model policy · no model was executed

model-agnostic coding agent

Original usage notes

  • A prompt for a development agent implementing changes in an existing codebase; the requested output is code.

Prompt with your inputs

The default values are filled in. This prompt has not been executed.

Original reusable prompt
Create a reusable micro-interaction system for {{components}} in the existing application. The intended feel is {{feel}}. Define motion tokens for duration, easing, distance and scale. Cover hover, keyboard focus, pressed, loading, success and disabled states where relevant. Keep feedback immediate and restrained, preserve the layout footprint and prevent accidental double submission during loading. Use existing component APIs rather than duplicating components. For this UI task, prefer CSS and the Web Animations API or an animation library already installed. Do not introduce Three.js or a new animation dependency unless this specific effect requires it. Animate transform and opacity where possible, avoid layout thrashing, and preserve existing semantic HTML, focus order and interaction behavior.

Implementation constraints:
First inspect the existing repository and installed versions. Reuse its routing, styling, build tools and dependency conventions. Use React Three Fiber only if the project already uses it or the integration is clearly justified; otherwise use the existing Three.js integration or a minimal isolated component. Do not assume version-specific APIs: check the installed package documentation and types. Do not change unrelated pages or silently replace the application architecture. Explain any required new dependency before adding it. Dispose GPU resources, remove event listeners and stop rendering when the component is not visible. Respect prefers-reduced-motion and provide a readable non-WebGL fallback. Keep links and controls in accessible HTML above the canvas. Return the changed files, configuration knobs, tests performed and known limitations.

Acceptance criteria:
- All interactive states remain visually distinguishable without relying on motion alone.
- Touch users receive feedback without depending on hover.
- Focus rings remain visible and disabled elements do not look actionable.
- Async success is announced accessibly where appropriate and focus is not unexpectedly moved.
- Reduced-motion mode removes translation and spring overshoot while keeping state changes clear.

Requested checks · not performed

  • All interactive states remain visually distinguishable without relying on motion alone.
  • Touch users receive feedback without depending on hover.
  • Focus rings remain visible and disabled elements do not look actionable.
  • Async success is announced accessibly where appropriate and focus is not unexpectedly moved.
  • Reduced-motion mode removes translation and spring overshoot while keeping state changes clear.

Execution record

Download template record ↓

Source & preservation

Kumyu Academy creative templates