agentleFS
mweinbachmweinbach/agent-coworker/.agents/skills/review-animations/SKILL.md

review-animations

Skill157 starsChanged 2 months agoLicence not identifiedView on GitHub

Reviews animation and motion code against a high craft bar derived from Emil Kowalski's design engineering philosophy. Default to flagging; approval is earned.

98 other projects use a version of this, 94 of them edited.

Adopted by

Most recently taken up by

Used with

Projects with it also use pick-ui-library, find-animation-opportunities and 8 more.

Other files people use alongside this one.

Files found in the same public projects as a version of this one, more often than they turn up anywhere else. Each project counts once, large collections count for less, and this file's own repository is left out.
  • boraoztuncSkill

    pick-ui-library

    Pick the library for a frontend task from a curated list — primitives, toasts, drawers, command menus, OTP, numbers, charts, virtualization, drag and drop, state, styling.

    Also in 52 projects that use this

  • boraoztuncSkill

    find-animation-opportunities

    Search a codebase or UI for places that don't animate but should, and reject everything that shouldn't. Read-only; it proposes motion with exact values, it does not implement it. Use when the user asks "what could be animated here?" or wants to "make this feel more alive". For fixing existing animations, use improve-animations or review-animations instead.

    Also in 67 projects that use this

  • emilkowalskiSkill

    ask-emil

    Ask which skill or flow fits your situation. A router over the skills in this repo.

    Also in 4 projects that use this

  • sanmidableSkill

    write-swift

    Also in 26 projects that use this

  • +6 more from boraoztunc

The file

We split this skill into the rules it gives an agent

7 rules. 4 are common, 2 are distinctive, and 1 is very specific to this project.

  • 4

    Common

    Most of the 96 edited versions we read keep these.

  • 2

    Distinctive

    This author's own choices. Worth a look.

  • 1

    Very specific

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

The licence could not be identified — read it at the source. We count its rules but don't quote them. Read them on GitHub.

“Common” is measured: kept by at least 6 in 10 of the 96 edited versions of this file we could read. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

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.