What is the ux-audit-rethink skill?
The ux-audit-rethink skill is a SKILL.md that makes an AI coding agent run a 360 degree UX audit. It rates a product on seven UX factors, five usability characteristics and five interaction design dimensions, using Interaction Design Foundation methods, then proposes strategic redesign recommendations.
The ux-audit-rethink skill is a single SKILL.md folder inside a public collection of UX, AI governance and AI security skills. It turns your agent into a UX auditor that follows the Interaction Design Foundation's framework from The Basics of User Experience Design.
Its description sets it apart from focused checks such as Nielsen, WCAG or Don Norman reviews. It aims for a 360 degree assessment, and the skill itself suggests using it as an entry point before narrower audits.
What changes in your agent's output
- The agent gathers an app description first. Screenshots or links, user feedback, target goals, business context and personas are optional extras.
- It drafts two or three provisional personas when you supply none, and it writes down its assumptions.
- Each of the seven factors gets a rating from 1 to 5 with strengths, gaps and evidence, plus a summary table showing status and priority.
- Scores roll up into an overall figure per framework, and the audit closes with redesign recommendations.
The three frameworks it scores
- Seven UX factors from Peter Morville's honeycomb: useful, usable, findable, credible, desirable, accessible and valuable.
- Five usability characteristics: effectiveness, efficiency, engagement, error tolerance and ease of learning. The skill adds a formula: utility plus usability equals usefulness.
- Five interaction design dimensions: words, visual representations, physical objects and space, time, and behavior.
Who the ux-audit-rethink skill is for
Best for
- A first broad review before a redesign, a pivot or a roadmap decision. The skill lists these among its use cases.
- Benchmarking a product against UX best practice and producing an improvement roadmap.
- Anyone who wants one wide audit first, then a narrower pass. For a focused follow-up on inclusive design, see accessibility-review.
Not for
- A line-by-line code review. The inputs are descriptions, screenshots, wireframes, prototypes and live URLs.
- Legal accessibility sign-off. Accessibility is one of seven factors here, and the skill points to a dedicated WCAG audit for compliance.
- A single-task deep dive. For that, the skill points to a cognitive walkthrough.
- A five-minute check. The skill's own time boxes run to about 15 minutes for context and 30 minutes for each evaluation step.
Use it with UiChemy
The audit tells you what to change, not how to build it. Apply the redesign in Figma, then bring it into WordPress with UiChemy Figma to WordPress and refine it in Composer. Click Get Started on uichemy.com. For design-focused reviews, see design-auditor.
How to install UX Audit Rethink Skill: Holistic UX Review for AI Agents
git clone https://github.com/mastepanoski/claude-skills.gitClone the repository
Run
git clone https://github.com/mastepanoski/claude-skills.git. The skill sits in the skills/ux-audit-rethink folder.Copy the skill folder
Copy skills/ux-audit-rethink into
.claude/skills/for Claude Code or.codex/skills/for OpenAI Codex CLI. The README describes the skills as plain SKILL.md folders for assistants that follow the Agent Skills standard.Describe your product
Give the agent an app description, plus screenshots or a live URL if you have them. A README example prompt asks for a complete UX audit of an e-commerce checkout flow.
Ask for the audit
Use a request such as perform a complete UX audit, then read the ratings and the redesign proposals.
Check that it loaded
Ask for a complete UX audit of one small flow. The reply should walk through the seven factors, five usability characteristics and five interaction dimensions with ratings, not a loose list of opinions.
Key features
- Context analysis firstStep 1 reviews the app description and identifies purpose, target users, platforms, key journeys and business model. It drafts provisional personas when none exist and documents its assumptions.
- Seven UX factorsRates useful, usable, findable, credible, desirable, accessible and valuable from 1 to 5, with strengths, gaps and evidence, then totals the result as an overall score out of 35.
- Five usability characteristicsScores effectiveness, efficiency, engagement, error tolerance and ease of learning, gives an overall score out of 25 and applies a utility plus usability check for usefulness.
- Five interaction dimensionsReviews words, visual representations, physical objects and space, time, and behavior. Typical flags include vague labels such as OK, mixed terms like Sign In and Log In, and touch targets under 44 by 44 pixels.
- Flexible inputsOnly an app description is required. Screenshots, links, user feedback, target goals, business context and personas are optional but give the audit more evidence to cite.
- Untrusted input handlingA security notice treats screenshots, links, feedback and analytics as data. It flags phrases such as ignore previous instructions and tells the agent not to follow instructions found inside them.
- Time-boxed procedureThe audit steps carry rough time boxes: 15 minutes for context analysis and 30 minutes each for the factor, characteristic and dimension reviews.
- Built to pair with narrower auditsThe skill recommends combining it with Nielsen heuristics for usability depth, WCAG accessibility for compliance, or a cognitive walkthrough for task-specific analysis.
- Redesign proposalsBeyond scores, the skill aims at strategic redesign recommendations grounded in user-centered design principles, useful for product decisions and an improvement roadmap.
Frequently asked questions
What is the ux-audit-rethink skill?
It is a SKILL.md in a public repository of UX evaluation, AI governance and AI security skills. It makes your agent audit a product across three frameworks from the Interaction Design Foundation, then propose redesign recommendations based on the ratings and evidence.
How do I install the ux-audit-rethink skill?
Clone the repository with git, then copy the skills/ux-audit-rethink folder into your agent's skills directory. The README names .claude/skills/ and .codex/skills/. Ask for a complete UX audit and name your product or flow so the agent can start.
What input does the skill need?
Only an app description is required, covering purpose, target users, key features and platform. Screenshots, wireframes or live URLs are optional but recommended. User feedback, target goals, business context and personas can sharpen the audit, and the agent builds provisional personas if you give none.
Which AI coding agents can use the ux-audit-rethink skill?
The README lists Claude Code, OpenAI Codex CLI and ChatGPT, and says any agent that supports the Agent Skills specification can use the same folders. It states that no separate variants are maintained for each assistant, so one SKILL.md serves them all.
How is it different from a Nielsen heuristics audit?
A Nielsen audit checks usability against ten heuristics. This skill is broader, scoring seven UX factors, five usability characteristics and five interaction dimensions together. Use it first, then add a narrower pass. If you need a written project brief for the app description, see design-brief.
How long does the audit take?
The skill sets rough time boxes, not guarantees: about 15 minutes for context analysis and 30 minutes each for the factor, usability characteristic and interaction dimension reviews. Real run time for your agent depends on how much material you supply and how large the product is.
Does the skill write the redesign for me?
The skill description promises redesign proposals and strategic recommendations, which are written advice. It does not describe editing your files or producing a finished design. To carry the proposals forward, hand them to a design or build step, such as the one in design-handoff.
What license does the ux-audit-rethink skill use?
The repository is MIT licensed, according to both GitHub and the README. The README says the license file in the repository has the full terms, so read it before you redistribute the skill folder inside a product.