agentleFS
Sign inStart free
thenslsthensls/nsls-builder-toolkit/skills/ux-audit/SKILL.md

ux-audit

Skill0 starsChanged 4 days agoNo licenceView on GitHub

Conduct a heuristic UX audit of a web page, Figma frame, screenshot, or HTML snippet, OR run a Design Validation Layer that predicts member reaction to a proposed change before it ships. Produces (1) a Predicted SUS estimate against the 10 System Usability Scale dimensions, (2) findings against 21 Laws of UX, (3) WCAG 2.1 A/AA accessibility checks, (4) brand-style findings against NSLS or Society brand guidelines, and (5) optionally, a Design Validation readout — surface-area map, past-test cross-reference, member-fit persona panel, DESIGN.md alignment, and three views of impact confidence. Use when the user wants a UX review, usability audit, accessibility audit, brand audit, heuristic evaluation, design critique, or pre-test design validation. Audit triggers include "audit this", "review the UX of", "is this accessible", "WCAG check", "predict SUS", "heuristic eval", "brand audit", or pasting a URL / Figma link / screenshot with audit intent. Design-validation triggers include "validate this design", "design validate", "/design-validate", "QA this change", "predict member reaction", "what will members think", "is this safe to test", "test this hypothesis". Runs in two modes: full (all four layers plus optional Design Validation) or QA (usability + UX + accessibility + functional build quality — links resolve, responsive breakpoints, console errors, tap targets, form error states, semantic landmarks, code readiness — with no brand layer and no member research). QA-mode triggers include "QA this page", "QA this build", "is this ready to ship", "check the responsive behavior", "build-quality pass", "ux qa", or a call from /page-qa. Especially relevant for NSLS enrollment pages and Figma frames in the EE sprint.

26 other projects use a version of this.

Adopted by

Most recently taken up by

Used with

Projects with it also use ecosystem-reference, fractal-delegation and 10 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.
  • naman10parikhSkill

    ecosystem-reference

    Quick-access directory of Claude Code ecosystem repos, skills, plugins, MCPs, and patterns. Use when improving the harness.

    Also in 5 projects that use this

  • naman10parikhSkill

    fractal-delegation

    Also in 5 projects that use this

  • KirchliveSkill

    skill-routing

    Decides which of the installed skills a task needs and loads them before the work starts. This skill should be used at the beginning of any multi-step task — build, fix, refactor, migrate, review, plan, release, research, write, design, video — and again at every phase change, after context compaction, and when work moves into a different part of the codebase. Use it for requests like "let's build X", "fix this bug", "refactor Y", "plan the migration", "review this", and also when the user asks which skill applies, why a skill did not fire, or asks to check what is available.

    Also in 5 projects that use this

  • sublimotionSkill

    agent-runtime

    Launch and manage detached agent runs on EKS via the agent-runner CLI. Use when the user says "launch an agent run", "agent runtime", "agent-runner", "run this spec on the cluster", "check run status", "agent run logs", or "stop a run". Do NOT use for writing the agent-runner code itself (edit the sibling ../agent-runner repo), Terraform of the foundation (use terraform-automation), or GPU serving deployments (use infra-deployer).

    Also in 5 projects that use this

  • GoZippySkill

    repo-scout

    Also in 5 projects that use this

  • BenjaminGSkill

    harness-review

    Turn one PR's review comments into harness fixes — classify each cause by the most solid place it can live (codebase, lint, rules, skill), then draft the fixes in a separate PR.

    Also in 5 projects that use this

  • +6 more from naman10parikh

The file

Show its rules and text

We split this skill into the rules it gives an agent

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

  • 0

    Common

    Most of the 23 edited versions we read keep these.

  • 16

    Distinctive

    This author's own choices. Worth a look.

  • 11

    Very specific

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

No licence file, so all rights are reserved — 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 23 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.

Check your setup, free