agentleFS
Sign inStart free
hebertzhuhebertzhu/agent-foundry/skills/fixing-accessibility/SKILL.md

fixing-accessibility

Skill0 starsChanged 8 months agoMITView on GitHub

用于无障碍审查与修复：当用户要检查或修 HTML 可访问性、ARIA、键盘导航、焦点管理、颜色对比、表单错误、dialog 或 WCAG 合规时使用。Combine with `frontend-design` or `ui-ux-pro-max` when 先做界面方案再做无障碍验收；Do not use for 纯视觉改版或一般性能优化。

19 other projects use a version of this.

Adopted by

Most recently taken up by

Used with

Projects with it also use ui-skills-root, improve-ui and 9 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.
  • Discriminative-shoji607Skill

    ui-skills-root

    Use before UI-related work to select the smallest useful UI Skills context through the ui-skills CLI.

    Also in 3 projects that use this

  • Discriminative-shoji607Skill

    improve-ui

    Audit an existing product surface against its own design evidence, identify verified UI problems, and write self-contained implementation plans for another agent. Strictly read-only on product source. Use when asked to review, refine, improve, or clean up an interface without replacing its identity; investigate design-system drift; or prepare a design handoff.

    Also in 3 projects that use this

  • studio-lgtmSkill

    make-interfaces-feel-better

    Apply design engineering best practices to polish UI components - use when reviewing or improving interfaces, animations, typography, or interaction details.

    Also in 4 projects that use this

  • swyxioSkill

    mobile-native

    Apply swyx's native mobile UX preferences when designing or critiquing iPhone/iPad flows, adapting tablet layouts, choosing communication-app notification behavior, or opening notifications/deep links/widgets/shortcuts before local content is ready. Also use for iOS/iPadOS generated build configuration, signing/install/launch problems, and device playtesting. Keep existing native or cross-platform stacks; excludes browser-only responsive work and backend-only changes without native UX or delivery implications.

    Also in 3 projects that use this

  • wxyhgkSkill

    improve-animations

    Survey a codebase's animation and motion code as a senior motion advisor, then produce a prioritized audit and self-contained implementation plans for other agents (or cheaper models) to execute. Read-only on source code — it plans improvements, it does not apply them. Use when the user asks to "improve the animations", "audit the motion", "make this app feel better", or wants a roadmap of animation fixes rather than a review of a single diff.

    Also in 4 projects that use this

  • VercelSkill

    emil-design-eng

    This skill encodes Emil Kowalski's philosophy on UI polish, component design, animation decisions, and the invisible details that make software feel great.

    Also in 5 projects that use this

The file

We split this skill into the rules it gives an agent

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

  • 0

    Common

    Most of the 18 edited versions we read keep these.

  • 2

    Distinctive

    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:

    Keep examples generic, privacy-safe, and portable across hosts.

    line 21
  2. Distinctive:

    Do not use as a catch-all for every visual preference disagreement.

    line 24

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

fixing-accessibility

Intent

  • 用于无障碍审查与修复：当用户要检查或修 HTML 可访问性、ARIA、键盘导航、焦点管理、颜色对比、表单错误、dialog 或 WCAG 合规时使用。Combine with frontend-design or ui-ux-pro-max when 先做界面方案再做无障碍验收；Do not use for 纯视觉改版或一般性能优化。

Default operating pattern

  1. Clarify audience, surface, success metric, and implementation boundary.
  2. Study relevant patterns, references, or constraints before proposing a direction.
  3. Define structure, interaction, copy, and visual hierarchy with a reusable rationale.
  4. Pressure-test accessibility, motion, maintainability, and platform fit.
  5. Return a concise recommendation and the next implementation move.

Pack fit

  • Included in: product-design
  • Keep examples generic, privacy-safe, and portable across hosts.

Boundary

  • Do not use as a catch-all for every visual preference disagreement.

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