wp-audit-ux-standards skillA
wp-audit-ux-standards is agent-read markdown (skill) from yojahny55/claude-wp-builder: Usability criteria for a WordPress site — forms and data entry, navigation and task flow, links, interactive feedback, legibility and visual identity. Holds the UX-NNN catalog, the page-level vs site-level split, the applicability rules that keep a score honest, and which owner each fix belongs to. Read by the wp-audit-ux agent and by /wp-audit when it scores..
Indexed from public GitHub and served as immutable, content-addressed versions. Install it pinned to an exact SHA-256 with the mdr CLI, and every file is verified against the hash recorded here before it reaches your agent. The deterministic audit below grades the latest version, and the same file always earns the same grade.
What the file says
# Usability standards Six auditors cover security, SEO, accessibility, performance, WordPress standards and GEO. Between them they answer whether the code is safe, findable, compliant, fast, idiomatic and legible to an agent. None of them answers whether a person can use the site. That is not a gap in one of them. A form that marks no field as required is valid HTML, escapes correctly, loads fast and passes WCAG; the site is simply harder to use than it needs to be, and nothing in the audit says so. These are the criteria that say so. ## What this is not - **Not accessibility.** Contrast, focus order, ARIA, keyboard traps and target size belong to `wp-audit-a11y` and stay there. Where the two touch — a link that is distinguishable only by colour is both — the accessibility code wins and the usability catalog does not restate it. Two codes for one defect inflate every count. - **Not performance.** Core Web Vitals, budgets and Lighthouse belong to `wp-audit-performance`. - **Not an opinion about taste.** Every criterion below has a pass condition somebody else could check and reach the same answer. "The hero could be stronger" is not a finding. ## The catalog …
Read the whole file at its exact version.
How to install
mdr add yojahny55/claude-wp-builder/wp-audit-ux-standards@git:20260922.000c3bcmdr add yojahny55/claude-wp-builder/wp-audit-ux-standards@sha256:83b0b0e3ff9977f7Pin to a label to follow the author's releases, or to a sha256 to freeze the exact bytes forever. Either way the resolved hash is written to mdr.lock, and mdr install reproduces it on any machine.
[](https://markdownregistry.com/a/art_jnnpwo4klor6oiwj)
1 badge views in 30 days
Versions
| version | committed | commit | size | audit | |
|---|---|---|---|---|---|
| git:20260922.000c3bc latest | 2026-09-22 | 000c3bc | 14,485 B | A | view · diff |
| git:20260920.b38aed8 | 2026-09-20 | b38aed8 | 14,439 B | A | view |
Audit of the latest version
- pass: Frontmatter block present
- pass: Frontmatter declares a name
- pass: Frontmatter declares a description
- pass: Size between 200 bytes and 200 KB (14485 bytes)
- pass: No zero-width or bidi control characters
- pass: No instruction hidden inside an HTML comment
- pass: No link to an exfiltration or paste host
- pass: No credential-shaped string
- pass: No instruction to send local credentials anywhere
- pass: No text hidden with inline styles
- pass: No prompt-injection phrasing
- pass: No curl or wget piped into a shell
- pass: No recursive delete of root, home or parent
- pass: No instruction to read or print local credentials
- pass: No base64 blob over 200 characters
- pass: No link to a raw IP address
- pass: No script tag
Source
yojahny55/claude-wp-builder · 6 stars · license MIT · pushed 2026-09-23 · branch main
API
GET https://markdownregistry.com/api/v1/artifacts/art_jnnpwo4klor6oiwj GET https://markdownregistry.com/api/v1/resolve?ref=yojahny55/claude-wp-builder/wp-audit-ux-standards GET https://markdownregistry.com/api/v1/blob/83b0b0e3ff9977f7836dbedf2c15cb617aa159b2e894bb62ca7e85823abcbf29
Your agent does the legwork. You hear about the deals worth your word. Hand yours the standing instructions at modelranch.com and it joins the network that reads files like this one.