agentleFS
dRafaleDdRafaleD/cybersec-skills/skills/engineering/lean-a11y/SKILL.md

lean-a11y

Skill2 starsChanged 56 days agoMITView on GitHub

Runs token-efficient accessibility reviews for Cursor and Codex. Inventories images without alt, click-only divs, and missing labels in local UI files, then reports compact accessible-name fixes. Use when the user asks for a11y, accessibility, alt text, keyboard, or ARIA review. Do not dump large JSX trees or rewrite the whole design system.

The file

We split this skill into the rules it gives an agent

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

  • 2

    Very specific

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

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

    Run ui. Queue <img> without alt, div onClick, inputs without label, target=_blank without rel.

    line 37
  2. Very specific:

    Prefer native elements (button, a) over ARIA theater.

    line 43
  3. Distinctive:

    Do not paste entire components.

    line 44

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

Lean A11y

Accessible name and keyboard first. Scripts list likely gaps; you confirm a few components.

Let SKILL_ROOT be the folder that contains this SKILL.md. Prefer python3; on Windows use py -3.

python3 "$SKILL_ROOT/scripts/lean_a11y.py" ui .
python3 "$SKILL_ROOT/scripts/lean_a11y.py" trim --chars 2500 path/to/out.txt

Mode

Default lean.

ModeBudget
leanui + up to 8 slices; references/name.md; ≤6 findings
standardup to 16 slices; ≤10 findings
deepstill no full CSS dump; ≤16 findings

Workflow

  1. Run ui. Queue <img> without alt, div onClick, inputs without label, target=_blank without rel.
  2. Slice-read. Cap quotes at 12 lines.
  3. Report the smallest name/keyboard fix. Stop unless asked to patch.

Hard rules

  • Prefer native elements (button, a) over ARIA theater.
  • Do not paste entire components.

Report template

## Lean-a11y (`<mode>`)

**UI:** <app> | **Budget:** files_read=<n>

| Sev | Location | Issue | Fix |
|-----|----------|-------|-----|
| HIGH | file:line | img with no alt | alt text or alt="" if decorative |

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.