agentleFS
divyanshu-iitiandivyanshu-iitian/agent-website-design-skills/conversion-accessibility-polish/SKILL.md

conversion-accessibility-polish

Skill2 starsChanged 4 months agoMITView on GitHub

Improve an existing website or web app's decision clarity, trust, forms, UX copy, and accessibility without dark patterns. Use when an agent must polish CTAs, navigation, pricing, onboarding, empty or error states, keyboard behavior, semantic HTML, focus, contrast, or the end-to-end conversion path.

The file

We split this skill into the rules it gives an agent

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

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈7

    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:

    Place trust information where commitment increases.

    line 24
  2. Distinctive:

    Do not add fake scarcity, hidden fees, confirmshaming, disguised ads, forced continuity, preselected consent, or obstructive cancellation.

    line 30
  3. Distinctive:

    Do not fabricate testimonials, metrics, security claims, or guarantees.

    line 31
  4. Distinctive:

    Do not trade away accessibility for a presumed conversion lift.

    line 32
  5. Distinctive:

    Do not claim WCAG conformance from automated tooling alone.

    line 33
  6. Distinctive:

    Implementation: - when changes are requested.

    line 43
  7. Distinctive:

    Read references/a11y-conversion-checks.md for a practical WCAG 2.2 AA-oriented audit and ethical conversion checklist.

    line 49

≈ “Common” is an estimate: at least 1 in 5 of the 364,980 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

Conversion and Accessibility Polish

Improve business outcomes by making the interface clearer, more trustworthy, and easier to operate. Accessibility is a product requirement, not a final visual filter.

Workflow

  1. Identify the primary user task, success event, and doubts or access barriers that block it.
  2. Walk the path from entry to success. Include navigation, forms, validation, loading, errors, confirmation, and return visits.
  3. Audit decision clarity:
    • what the user is choosing;
    • cost and commitment;
    • what happens next;
    • evidence and risk;
    • how to recover or leave.
  4. Audit semantics and interaction: landmarks, headings, names, labels, descriptions, keyboard order, focus management, announcements, and pointer alternatives.
  5. Audit visual access: contrast, text resize/reflow, focus visibility, target spacing, zoom, motion, and content hidden by sticky UI.
  6. Replace vague or inflated copy with specific outcomes, constraints, examples, and next-step language.
  7. Reduce form friction without removing necessary consent, security, or error prevention.
  8. Place trust information where commitment increases. Keep terms, privacy, cancellation, and destructive effects visible.
  9. Implement the highest-impact fixes first: blocked tasks, misleading decisions, keyboard failures, form failures, then visual polish.
  10. Re-test the complete path on mobile and with keyboard-only navigation. Use automated checks as support, not as proof of conformance.

Ethical Guardrails

  • Do not add fake scarcity, hidden fees, confirmshaming, disguised ads, forced continuity, preselected consent, or obstructive cancellation.
  • Do not fabricate testimonials, metrics, security claims, or guarantees.
  • Do not trade away accessibility for a presumed conversion lift.
  • Do not claim WCAG conformance from automated tooling alone.
  • Preserve user input after recoverable errors and make destructive actions explicit.

Delivery Contract

Provide:

  1. Primary path - entry -> decision -> action -> success.
  2. Findings - severity, affected users, evidence, and relevant standard when known.
  3. Prioritized fixes - impact versus effort.
  4. Implementation - when changes are requested.
  5. Verification - keyboard path, mobile path, form states, and automated/manual checks.
  6. Honest limits - what still requires content, legal, analytics, or assistive-technology review.

Reference

Read references/a11y-conversion-checks.md for a practical WCAG 2.2 AA-oriented audit and ethical conversion checklist.

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.