ux-audit

Audit routed pages for non-technical resume builders using Playwright validation.

Updated Mar 19, 2026
One-click install
npx skills add https://github.com/reckerswartz/resume_builder --skill ux-audit-reckerswartz
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: ux-audit
Source: https://github.com/reckerswartz/resume_builder/tree/main/.devin/skills/ux-audit
Command: npx skills add https://github.com/reckerswartz/resume_builder --skill ux-audit-reckerswartz

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Audits routed pages to improve content quality, information density, and user-flow clarity for non-technical users building resumes.

Core Features & Use Cases

  • Continuous audit cycle: audit → score → fix → validate → re-audit across the main UI and page families.
  • Playwright-driven validation and regression tracking to ensure improvements are retained.
  • Registry-driven guidance for updating locale keys, components, and documentation.

Quick Start

Initiate an ux-audit run on the current main surface to identify usability issues and start the cycle.

Frequently Asked Questions about ux-audit

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I run a UX audit on routed pages to improve resume usability?

Run a UX audit by initiating a cycle that evaluates routed pages, scores usability issues, fixes them, and validates the results. This continuous audit process improves content quality and user-flow clarity for non-technical resume builders.

Can I use Playwright to validate usability fixes on a Rails application?

Yes, Playwright is used for validation and regression tracking throughout the audit cycle. It ensures that usability improvements applied to routed pages are retained and functioning correctly across the main UI and page families.

What is a registry-driven UX audit workflow?

A registry-driven UX audit workflow uses a central registry to guide updates to locale keys, components, and documentation. It maintains a continuous cycle of auditing, scoring, fixing, validating, and re-auditing routed pages for usability.

How do I audit content density and user-flow clarity for non-technical users?

Audit content density and user-flow clarity by running an audit cycle on routed pages. The process identifies usability issues, scores them, and guides fixes to improve the experience for non-technical users building resumes.

Does the UX audit cycle update UI guidelines and documentation?

Yes, the UX audit cycle updates UI guidelines and documentation accordingly. The registry-driven workflow ensures that changes to locale keys and components are tracked and documented throughout the continuous audit process.

What's the best way to continuously track UX regressions on resume builder pages?

Track UX regressions by running a continuous audit cycle using Playwright-driven validation. This approach maintains a registry of usability scores and validates fixes across page families to ensure improvements are retained over time.