agentleFS
Sign inStart free
ArcanEdge-AIArcanEdge-AI/coding-agent-playbook-claude-code/skills/production-ux-accessibility/SKILL.md

production-ux-accessibility

Skill0 starsChanged 4 months agoMITView on GitHub

Review frontend production readiness, user experience, accessibility, responsive behavior, forms, validation, loading states, empty states, error messages, keyboard navigation, screen reader basics, focus management, color contrast, browser compatibility, broken links, and critical user-flow usability. Use when a production pass needs UX or accessibility review of frontend screens, forms, navigation, or critical user journeys.

1 other project uses a version of this, 1 of them edited.

Adopted by

Most recently taken up by

The file

We split this skill into the rules it gives an agent

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

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈6

    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:

    Avoid redesigning the product.

    line 62
  2. Distinctive:

    Do not introduce a new design system.

    line 77
  3. Distinctive:

    Do not make broad visual changes without approval.

    line 78
  4. Distinctive:

    Do not reduce accessibility for visual polish.

    line 79
  5. Distinctive:

    Do not hide validation errors.

    line 80
  6. Distinctive:

    Do not remove content or functionality to simplify the UI.

    line 82

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

Production UX Accessibility

Core purpose

Identify UX or accessibility issues that block or degrade critical user flows; apply fixes only within authorized remediation scope.

Use this skill when

  • The production pass needs UX or accessibility review.
  • The application has frontend screens, forms, navigation, or critical user journeys.
  • The user wants production polish that helps users complete key tasks.

Do not use this skill when

  • The repository has no user interface.
  • The task is only backend or infrastructure.
  • The user wants a full redesign instead of production-readiness polish.

Check for

  • Mobile responsiveness
  • Broken layouts
  • Inconsistent UI states
  • Missing form validation
  • Poor error messages
  • Missing loading states
  • Missing empty states
  • Keyboard navigation
  • Screen reader basics
  • Color contrast
  • Browser compatibility risks
  • Broken links
  • Focus management
  • Disabled state behavior
  • Critical flow usability issues
  • Inaccessible controls
  • Missing labels
  • Confusing success states

Default workflow

Resolve the task mode first: assessment-only work reports findings without source, test, or repository-document edits; authorized remediation applies only in-scope fixes. Release, production, and destructive operations retain their separate authority requirements.

  1. Identify frontend framework and UI conventions.
  2. Identify critical user flows.
  3. Inspect components, pages, forms, route transitions, and state handling.
  4. Classify findings as Blocker, High, Medium, or Low.
  5. Prioritize issues that block task completion.
  6. Apply safe in-scope fixes only when remediation is authorized; assessment-only requests report recommendations:
    • missing labels
    • missing validation text
    • loading states
    • empty states
    • focus and keyboard improvements
    • broken links
    • clearer error messages
  7. Avoid redesigning the product.
  8. Include relevant manual QA checks in the requested deliverable; edit a project checklist only when authorized.

Severity guidance

Classify as Blocker when users cannot complete a critical flow.

Classify as High when UX or accessibility issues materially harm critical production usage.

Classify as Medium when improvements are important but not release-blocking.

Classify as Low for polish, consistency, or optional accessibility improvements.

Guardrails

  • Do not introduce a new design system.
  • Do not make broad visual changes without approval.
  • Do not reduce accessibility for visual polish.
  • Do not hide validation errors.
  • Preserve existing visual conventions where reasonable.
  • Do not remove content or functionality to simplify the UI.

Deliverables

Include the following in the requested assessment response or report. Update repository readiness files only when those artifacts are requested or part of authorized remediation:

  • UX readiness summary
  • Accessibility findings
  • Safe frontend fixes
  • Manual QA recommendations
  • Remaining UX risks
  • Files changed and reasons

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.

Reviews can't be read right now.

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