agentleFS
Sign inStart free
ECD5AECD5A/OrchestrUI/skills/ui-quality-audit/SKILL.md

ui-quality-audit

Skill1 starsChanged 3 months agoMITView on GitHub

Audit an OrchestrUI-based frontend for visual coherence, accessibility, responsiveness, motion discipline, performance, data visualization quality, licensing, and misuse of UI libraries. Use before declaring toolkit-based UI work complete.

1 other project uses a version of this.

Adopted by

Most recently taken up by

  • Other versions1 project uses a version of this.

    Word for word · 0

    None found.

    Edited · 0

    None found.

    Wrote their own version · 1

    1. Dmkdok/product-factory★ 1same name

    How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.

  • In this repository7 other files it gives its agents.

The file

We split this skill into the rules it gives an agent

1 rule. About 0 are common, 1 is distinctive, and 0 are 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.

  • 0

    Very specific

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

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    Read references/rubric.md before completing a full audit.

    line 12

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

UI Quality Audit

Audit the rendered result and implementation, not only the plan. Score each category 0 (blocking), 1 (acceptable with a documented tradeoff) or 2 (release-ready): visual coherence; library discipline; accessibility; responsiveness; motion/reduced-motion; data-viz readability; Rive lifecycle/asset rights; engineering checks/dependencies/secrets; licensing/Pro/React Bits restrictions.

Fix every 0 within scope, rerun affected checks, and then report the score out of 18, evidence, blockers fixed, remaining tradeoffs and checks executed. Do not award points for requirements that were not exercised; mark them not applicable with evidence and score 2 only when absence removes the risk.

Read references/rubric.md before completing a full audit.

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