Hey, this isn’t a Cursor setting. The model itself tends to reach for motion wrappers, which is a common pattern in modern Vue and React code via motion-v / @vueuse/motion / framer-motion. There’s no “Disable motion” checkbox, so the only levers are rules and model choice.
What to try:
-
Create
.cursor/rules/no-motion.mdcwith an explicit negative andalwaysApply: true:--- alwaysApply: true --- Do NOT use motion-v, @vueuse/motion, framer-motion, or any animation library. Do NOT generate <motion.div>, <motion.span>, <motion.*> or import { motion }. Use plain HTML/Vue elements. If animation is needed, use CSS transitions or @keyframes.A strict negative plus specific package names works better than a generic “no motion”.
-
If the rules still get ignored, that’s a known issue with adherence for
alwaysApply. There’s a thread here: `alwaysApply: true` rules are being completely ignored now. Also copy the same text intoAGENTS.mdin the project root, it sometimes works more reliably. -
Switch from
autoto a specific model, like Claude 4.6 Sonnet or GPT-5.4. Auto sometimes picks models with a stronger bias toward motion wrappers. Different models follow rules differently. -
If the project is already messy, send the agent a separate message like: “Remove all motion-v / framer-motion / @vueuse/motion usage from the project and replace with plain elements”.
Let me know if the rules still don’t stick. If so, share your .mdc file contents and the Request ID, and we can dig into what’s going on.