agentleFS
Sign inStart free
ceptlnceptln/quota-burner/skills/ui-review/SKILL.md

ui-review

Skill18 starsChanged 2 months agoMITView on GitHub

Use to review one app page per run in a sandbox environment: screenshots, design-system deviations, UX of the main flow; fixes objective deviations only. Chantier: needs an approved chantier issue and a sandbox target.

20 other projects use a version of this.

Adopted by

Most recently taken up by

Used with

Projects with it also use accessibility and grill-me.

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.
  • ElasticSkill

    accessibility

    Accessibility guidance for Kibana. Use this skill when working with or reviewing EUI components, resolving a11y-related (@elastic/eui) ESLint issues, and ensuring proper use of ARIA attributes, focus management, keyboard interactions, and accessible naming conventions.

    Also in 3 projects that use this

  • GoogleSkill

    grill-me

    A relentless interview to sharpen a plan or design.

    Also in 3 projects that use this

The file

We split this skill into the rules it gives an agent

1 rule. 0 are common, 0 are distinctive, and 1 is very specific to this project.

  • 0

    Common

    Most of the 16 edited versions we read keep these.

  • 0

    Distinctive

    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:

    Read .quota-burner/CONTRACT.md and the configured team context before targeting.

    line 6

“Common” is measured: kept by at least 6 in 10 of the 16 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.

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

Read .quota-burner/CONTRACT.md and the configured team context before targeting. Standalone invocation follows repository permissions and does not authorize a PR by itself.

Review ONE app page per run in a sandbox environment, and fix the objective deviations found.

Targeting: page rotation lives in the chantier issue; your design system defines "objective deviation". Use the available browser tooling for before/after screenshots at desktop and mobile sizes, including key states.

Done: PR with before/after screenshots from synthetic sandbox data, attached through the repository’s review flow. Never a redesign: ambitious ideas become issues, not diffs.

Requires a sandbox target (deployed URL + test credentials) and its domains in your session's network allowlist; keep disabled until they exist.

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