| name | motion-react-microinteractions |
| description | Implement refined React and Motion for React microinteractions. Use for buttons, menus, nav, modals, tabs, cards, accordions, layout transitions, reveal wrappers, hover/tap states, mobile menus, and interactive UI that should feel premium without heavy GSAP timelines. |
Motion React Microinteractions
Overview
Make small interactions feel crafted. Microinteractions are state communication. They should be quiet, fast, and consistent.
Website Nonnegotiables
- Inspect before coding: structure, framework, homepage or main entry file, styling system, JavaScript or interaction system, assets, and build commands.
- Before major changes, explain planned files and wait unless the user clearly says proceed, build, create, implement, or fix.
- Use existing project conventions first. Explain major new dependencies before adding them.
- Never ship generic visual work: no default card grids, placeholder copy, weak type, random gradients, stock-like media, or template heroes.
- Build version 1, inspect the rendered result, improve spacing, type, hierarchy, motion, media, hover states, and responsiveness, then run checks again.
- Run available lint, build, and test commands when possible. Report commands, changed files, and any untested areas honestly.
- Check desktop and mobile. Respect accessibility, semantic markup, focus states, and reduced-motion preferences.
Workflow
- Read the user's brief and identify the website category, audience, content reality, visual references, and asset availability.
- Inspect the project before editing when code exists.
- Apply this skill's specific rules from
references/motion-react-microinteractions-guide.md.
- Explain planned files before major changes unless the user has clearly said to proceed.
- Build, inspect, polish, and verify before final delivery.
Reference
Read references/motion-react-microinteractions-guide.md when this skill triggers for a concrete website build, redesign, visual review, or implementation plan.
