agentleFS
adymireadymire/CraftLayer/skills/animation-and-motion/SKILL.md

animation-and-motion

Skill0 starsChanged 3 days agoMITView on GitHub

Use accessible, performant motion to communicate state, feedback, and spatial relationships in interfaces.

The file

We split this skill into the rules it gives an agent

11 rules. About 0 are common, 11 are distinctive, and 0 are very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈11

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 0

    Very specific

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

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    Use when motion clarifies a state transition, response, hierarchy, or relationship, or when reviewing animation in a product interface.

    line 10
  2. Distinctive:

    Do not add motion merely to decorate a screen, delay access to content, or make required information available only through animation.

    line 15
  3. Distinctive:

    Prefer small transitions on opacity or transform.

    line 27
  4. Distinctive:

    Keep timing and easing consistent with related interactions.

    line 29
  5. Distinctive:

    Test on touch, keyboard, reduced-motion settings, and representative lower-powered devices.

    line 34
  6. Distinctive:

    Verify animations do not obscure focus, content, or status announcements.

    line 36
  7. Distinctive:

    Keep important content visible if animation fails or is disabled.

    line 42
  8. Distinctive:

    Avoid flashing, rapid repeated movement, parallax that disorients, and unbounded animation loops.

    line 44
  9. Distinctive:

    Ensure the panel's state and content remain understandable without motion.

    line 61
  10. Distinctive:

    Check reduced-motion behavior, keyboard focus, touch input, timing, performance, non-animated comprehension, and whether the motion …

    line 72
  11. Distinctive:

    Use the motion specification and review guide when several transitions need consistent timing or when motion affects navigation, feedback, …

    line 78

≈ “Common” is an estimate: at least 1 in 5 of the 350,495 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

Animation and Motion

When to use

Use when motion clarifies a state transition, response, hierarchy, or relationship, or when reviewing animation in a product interface.

When not to use

Do not add motion merely to decorate a screen, delay access to content, or make required information available only through animation.

Inputs and assumptions

Inspect interaction purpose, platform, device performance, existing motion tools, reduced-motion support, keyboard/touch use, and whether the animation is essential to comprehension.

Workflow

  1. State what user action or system state the motion communicates.
  2. Prefer small transitions on opacity or transform; avoid layout churn and long blocking sequences.
  3. Keep timing and easing consistent with related interactions.
  4. Make controls usable immediately and avoid preventing cancellation, navigation, or repeated input.
  5. Respect prefers-reduced-motion; remove nonessential movement or replace it with a clear static state.
  6. Test on touch, keyboard, reduced-motion settings, and representative lower-powered devices.
  7. Verify animations do not obscure focus, content, or status announcements.

Decision rules

  • Motion communicates feedback or continuity; it is not a substitute for accessible state.
  • Keep important content visible if animation fails or is disabled.
  • Choose CSS or an existing motion library before adding another dependency.
  • Avoid flashing, rapid repeated movement, parallax that disorients, and unbounded animation loops.

Example

.panel {
  transition: opacity 160ms ease, transform 160ms ease;
}

@media (prefers-reduced-motion: reduce) {
  .panel {
    transition: none;
  }
}

Ensure the panel's state and content remain understandable without motion.

Common failures

  • Animating height or position in a way that causes layout jank.
  • Ignoring reduced-motion preferences.
  • Using motion to indicate success without accessible text or status.
  • Overusing scroll effects that compete with reading.

Validation

Check reduced-motion behavior, keyboard focus, touch input, timing, performance, non-animated comprehension, and whether the motion supports a specific user task.

Supporting guide

Use the motion specification and review guide when several transitions need consistent timing or when motion affects navigation, feedback, or layout.

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.