Generate a WCAG 2.2 accessibility audit checklist and remediation suggestions for any UI or design. Use when asked to audit for accessibility, check WCAG com...
Browser
Ux Usability Auditor
Try itAutomated UX/usability audit for web applications. Use when the user wants to evaluate usability, accessibility, or UI consistency of a web app; mentions "us...
What it does
Automated UX/usability audit for web applications. Use when the user wants to evaluate usability, accessibility, or UI consistency of a web app; mentions "usability audit", "UX review", "UI inspection", "易用性巡检", "体验巡检", or wants to generate a structured usability report. Works by navigating through target app pages via Playwright, capturing screenshots and UI metadata, then evaluating against a configurable checklist. Supports both Chinese and English usability standards.
The skill document
UX Usability Auditor
Automated usability and UX inspection for web applications. Navigates target app pages, captures screenshots and UI element metadata, then generates a structured audit report mapped to a usability checklist.
Quick Start
Minimal workflow — 4 steps:
- Prepare config — create a
config.json(see Configuration) - Run inspection —
node scripts/inspect.js config.json - Review results — check
results/inspection_results.jsonand screenshots - Generate report —
node scripts/generate_report.js config.json
Configuration
Create a config.json in the working directory:
{
"name": "My App Usability Audit",
"targetUrl": "https://example.com/#/login",
"login": {
"username": "admin",
"password": "123456",
"usernameSelector": "input[type='text'], input[placeholder*='账号'], input[placeholder*='用户名']",
"passwordSelector": "input[type='password'], input[placeholder*='密码']",
"submitSelector": "button:has-text('登录'), button:has-text('Login'), .login-btn"
},
"pages": [],
"checklist": "references/checklist-default.md",
"outputDir": "./results",
"screenshotDir": "./results/screenshots",
"headless": false
}
pages field (auto-discovery if empty):
[]— auto-discover pages by clicking through sidebar/menu after login- explicit list — provide known page URLs:
{
"pages": [
{ "name": "Dashboard", "url": "/#/dashboard" },
{ "name": "User List", "url": "/#/users" }
]
}
Login selectors — customize if the target app uses non-standard login form. Default works for most Element UI / Ant Design apps.
Scripts
scripts/inspect.js — Main Inspection Runner
Navigates pages, captures screenshots and UI metadata.
node scripts/inspect.js path/to/config.json
Output: results/inspection_results.json + results/screenshots/*.png
The script:
- Launches Chromium via Playwright
- Logs in using credentials from config
- Discovers pages (auto from sidebar, or from config)
- For each page: waits for load, screenshots, extracts UI stats (button/input/table counts, empty states, breadcrumbs, action buttons)
- Writes results to JSON
scripts/generate_report.js — Report Generator
Generates a markdown audit report from inspection results + checklist.
node scripts/generate_report.js path/to/config.json
Output: results/usability_audit_report.md
The script:
- Loads
inspection_results.json - Parses the checklist (markdown file, supports the standard 6-category format)
- Evaluates each checklist item against inspection data
- Generates a structured report with: summary table, detailed findings per category, evidence screenshots, priority-ranked issue list
Checklist Format
The default checklist is at references/checklist-default.md. It follows this format (compatible with the 易用性专项检查项清单 Excel):
# Usability Checklist
## Category 1: Navigation & Layout
### 1.1 Menu Hierarchy
- **Standard**: menu depth ≤ 3 levels, high-frequency entries prioritized
- **Applicable to**: All modules
To use a custom checklist, point checklist in config.json to your own markdown file, or pass a path to generate_report.js:
node scripts/generate_report.js config.json --checklist my_checklist.md
Advanced: Tuning Page Discovery
If auto-discovery misses pages, manually list them in config.json pages field. The inspector will navigate to each URL and capture data.
For single-page apps (SPA) with hash routing (like the one we audited), make sure URLs include the #/ fragment.
Output Structure
results/
├── inspection_results.json # Raw inspection data per page
├── usability_audit_report.md # Final report (markdown)
├── screenshots/
│ ├── 01_dashboard.png
│ ├── 02_user_list.png
│ └── ...
└── report_assets/ # Copied screenshots for report embedding
Notes
- Playwright required:
npm install playwrightbefore first run - Chromium bundled: Playwright downloads its own Chromium; no local Chrome needed
- Headless mode: Set
"headless": truein config for CI/batch runs - Chinese UI: Default selectors and checklist support Chinese enterprise web apps (Element UI, Ant Design)
- SPA support: Handles hash-based routing (
#/) and pushState routing
Related skills
Audit a design system for consistency, coverage, and quality. Use when asked to audit a design system, review a component library, assess design token covera...
Use when the user asks to "audit on-page SEO" or "diagnose why a single page dropped"; scores titles, meta, header structure, keyword placement, links, and i...
依据中国工信部《互联网网站适老化通用设计规范》和《移动互联网应用(APP)适老化通用设计规范》,对项目代码进行适老化合规检测,生成问题报告、修改建议,并支持自动修复。
Crawl and analyze a website's visual design system from a given URL, identifying design style, color system, typography, component styles, and UI patterns.
Use when the user wants a current site audit, technical SEO findings, Core Web Vitals interpretation, or a fresh TrustGrowth audit when connected. Supports connected, imported, and public/local evidence.