agentleFS
Sign inStart free
ankitluthraankitluthra/frontend-quality-graph/skills/frontend-interaction/SKILL.md

frontend-interaction

Skill0 starsChanged 3 months agoMITView on GitHub

Reviews frontend interaction quality — loading/empty/error states, motion discipline, and feedback on user actions. Invoked automatically by frontend-graph for fe.interaction and full UI graphs.

The file

We split this skill into the rules it gives an agent

2 rules. About 0 are common, 1 is distinctive, and 1 is very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈1

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 1

    Very specific

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

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

    Default severity: warn (does not block Pass?

    line 11
  2. Distinctive:

    No animation that blocks task completion or causes layout thrash

    line 20

≈ “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

Frontend interaction review

Default severity: warn (does not block Pass? unless UX is broken).
Return PASS, WARN, or FAIL (FAIL only for broken primary flows).

Must-check

  1. Primary async paths have loading feedback
  2. Empty and error states exist where users can hit them
  3. Actions give clear success/failure feedback
  4. Motion: at most 2–3 intentional motions for visually led work; no noise
  5. No animation that blocks task completion or causes layout thrash
  6. Destructive actions need confirmation when appropriate

Output format

VERDICT: PASS|WARN|FAIL
Findings:
- [file or area] issue → fix
(max 8)

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.

Check your setup, free