agentleFS
HeyEddi-comHeyEddi-com/heyeddi-skills/skills/motion-physics/SKILL.md

motion-physics

Skill0 starsChanged 7 days agoMITView on GitHub

Spring micro-interactions for Vue 3 using @vueuse/motion. Use when introducing cards, dialogs, lists, hover, or press feedback. Forbids linear spatial easing, long staggers, and looping motion unless a loading state was requested.

  • Installs packages

1 other project uses a version of this.

Adopted by

Most recently taken up by

The file

We split this skill into the rules it gives an agent

7 rules. About 0 are common, 4 are distinctive, and 3 are very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈4

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 3

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Very specific:

    Do not invent transition coordinates.

    line 13
  2. Distinctive:

    When a moment matches a preset, use the preset.

    line 68
  3. Very specific:

    No linear transitions: never use ease-in-out or linear timing for spatial movements (x, y, scale).

    line 75
  4. Distinctive:

    No continuous looping: avoid looping pulses, infinite rotations, or floating animations on UI elements unless explicitly requested for an …

    line 77
  5. Very specific:

    Import MotionPresets from src/design/motion-presets.js.

    line 82
  6. Distinctive:

    Do not animate layout properties that PrimeVue or Quasar already own (drawer width, virtual scroller position) unless the user asked for …

    line 84
  7. Distinctive:

    When you have finished the user's request for this skill, suggest what to run next:

    line 89

≈ “Common” is an estimate: at least 1 in 5 of the 364,980 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

Spring Motion

Replaces generic fade and slide effects with spring physics from @vueuse/motion.

Do not invent transition coordinates. Use the three presets below. Shell and data components stay in @quasar-foundation and @primevue-aura. A card that grows into its detail in the same view is @layout-morph (Quasar v-morph), not a spring on position.

When the agent activates this skill

  • Introducing cards, modals, or list items to the DOM.
  • Card hover states, focus depth, and button tap compressions.
  • Staggering sequential data lists or dashboard panels.

Installation

npm install @vueuse/motion

Register MotionPlugin after PrimeVue in src/main.js. The bootstrap block is in @primevue-aura.

Physics profiles

// src/design/motion-presets.js
export const MotionPresets = {
  // Snappy feedback for clicks, toggles, and icon buttons
  microFeedback: {
    hovered: { scale: 1.02, transition: { type: 'spring', stiffness: 400, damping: 25 } },
    tapped: { scale: 0.97, transition: { type: 'spring', stiffness: 500, damping: 30 } }
  },

  // Structural panel / dialog entry
  modalEnter: {
    initial: { opacity: 0, scale: 0.95, y: 15 },
    enter: {
      opacity: 1,
      scale: 1,
      y: 0,
      transition: { type: 'spring', stiffness: 280, damping: 22 }
    }
  },

  // Stagger helper for lists / tables
  staggerItem: (index) => ({
    initial: { opacity: 0, y: 12 },
    enter: {
      opacity: 1,
      y: 0,
      transition: {
        delay: Math.min(index * 35, 200), // Cap max delay to prevent slowness
        type: 'spring',
        stiffness: 320,
        damping: 24
      }
    }
  })
};

When a moment matches a preset, use the preset. The directive defaults apply only when none of the three presets fit:

  • Interactive elements: { type: 'spring', stiffness: 350, damping: 25 }
  • Dialogs and overlays: { type: 'spring', stiffness: 280, damping: 22 } (same as modalEnter)

Anti-AI-slop motion rules

  • No linear transitions: never use ease-in-out or linear timing for spatial movements (x, y, scale). Always use spring damping.
  • Cap animation delays: never set list stagger delays greater than 40ms per item or total delay exceeding 200ms. staggerItem uses 35ms and caps at 200ms.
  • No continuous looping: avoid looping pulses, infinite rotations, or floating animations on UI elements unless explicitly requested for an active loading state.
  • Provide a prefers-reduced-motion path: skip spatial springs and use an instant opacity change.

Instructions

  1. Import MotionPresets from src/design/motion-presets.js. Do not copy the numbers into a component as one-off values.
  2. Bind v-motion to the preset that matches the moment.
  3. Do not animate layout properties that PrimeVue or Quasar already own (drawer width, virtual scroller position) unless the user asked for that motion.
  4. Loading indicators may loop. Everything else plays once.

When the task is complete: suggest next skills

When you have finished the user's request for this skill, suggest what to run next:

  1. Run:

    python .agents/skills/heyeddi/scripts/suggest_next_skill.py --current-skill motion-physics --project-root .
  2. Include the script's ### Next step block in your final reply.

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.