Ux States Audit

Ux States Audit is a Quality skill for Claude Code, published by markmdev in meridian.

183 stars22 forkson markmdev/meridianAdded 2026/09/06+1% in starsRepository updated 2026/03/11

ai-agentsanthropicautomationclaudeclaude-codedeveloper-toolsdeveloper-workflownextjsnodejsopen-sourceproductivitysoftware-engineeringtask-runnertddtypescriptworkflow-automationzero-config

Install in seconds

Install Ux States Audit

Copy Ux States Audit into your Claude Code skills folder. Run the command in your terminal, or review the source on GitHub before installing.

terminal

npx degit https://github.com/markmdev/meridian/tree/main/skills/ux-states-audit ~/.claude/skills/ux-states-audit

Requires Node.js. Downloads this skill only — not the rest of the repository — into your Claude Code skills folder.

Without Node.js

git clone https://github.com/markmdev/meridian.git

Clones the whole repository, then copy the skill’s own directory into your skills folder yourself.

In this catalog

Source file: skills/ux-states-audit/SKILL.md in markmdev/meridian
Installs to: ~/.claude/skills/ux-states-audit
Collection: One of 6 skills cataloged from this repository
Category: Quality — 1745 skills

What Ux States Audit does

Ux States Audit finds UI components that fetch data or run async work without loading, empty, or error states. Use it to fill those gaps with the app's existing patterns.

Ux States Audit is cataloged under Quality on DirSkills. Ux States Audit comes from a repository tagged ai-agents, anthropic, automation, claude and claude-code.

Documentation

README

Excerpt

UX States Audit

Every piece of UI that fetches data or triggers async work has three states beyond the happy path: loading, empty, and error. LLMs implement the happy path and leave the rest blank. This skill finds and fills those gaps.

This is distinct from error-audit: error-audit finds errors that are suppressed. This finds states that were never implemented.

Step 0: Understand existing patterns

Before touching anything, read the codebase to understand how it currently handles these states:

What components or primitives exist for loading (skeletons, spinners, shimmer)?
What does an empty state look like — is there a shared component, or inline?
How are errors shown to users — toast, inline message, error boundary?

This is the opening of the README. Read the full README on GitHub.

Frequently asked about Ux States Audit

What else does markmdev publish alongside Ux States Audit?
Ux States Audit is one of 6 skills that DirSkills catalogs from markmdev/meridian, the repository it ships in. Its siblings there include Add Frontmatter, Create Docs and Error Audit. Each one is a separate skill with its own page in this directory, installs the same way Ux States Audit does, and is maintained by markmdev in that same repository. The rest of the collection is listed on the markmdev/meridian page.
How does Ux States Audit compare to other Quality skills?
Ux States Audit ranks #1664 by stars among the 1745 Quality skills in this catalog. The most-starred ones next to it are Benchmark, Benchmark Optimization Loop and API Design Patterns. DirSkills ranks by the star count of the repository each skill ships in, so that order reflects how popular those repositories are rather than any review of Ux States Audit against them. Open each page to compare what they document and how they install.