Skip to content
Back to search

frontend-design-audit

This is a claude skill to audit the front end based on established usability heuristrics and systematically improve your website.

Safety scan

A static text scan, not a guarantee. Select the badge to see what was scanned and every finding.

Checked today
Badge for your README
findsafeskills safety rating

Markdown

[![findsafeskills safety rating](/api/listings/mistyhx--frontend-design-audit/badge.svg)](/listings/mistyhx--frontend-design-audit)

HTML

<a href="/listings/mistyhx--frontend-design-audit"><img src="/api/listings/mistyhx--frontend-design-audit/badge.svg" alt="findsafeskills safety rating" /></a>

Install

i

Install instructions from the README

As written by the repo's author. findsafeskills has not verified these steps.

Recommended: Plugin Marketplace (one-time setup, works across all projects)

1. Start Claude Code in any project:

cd your-project
claude

2. Add the marketplace:

/plugin marketplace add mistyhx/frontend-design-audit

3. Open the plugin menu:

/plugin menu

4. Select and install `frontend-design-audit` from the list.

5. Restart Claude Code.

Alternative: Load Directly (per-session)

Clone this repo, then start Claude Code from your project with a relative path to the plugin:

git clone https://github.com/mistyhx/frontend-design-audit.git ~/plugins/frontend-design-audit
cd your-project
claude --plugin-dir ../plugins/frontend-design-audit

Or use an absolute path:

claude --plugin-dir ~/plugins/frontend-design-audit

What was scanned

The files the safety scan read, as written by the repository's author and shown as plain text. Lines with a finding are marked.

.claude-plugin/marketplace.json · Manifest · 20 lines

View this file on GitHub (read at the repository's current version: the scan did not record which commit it read)

  1. {
  2. "$schema": "https://anthropic.com/claude-code/marketplace.schema.json",
  3. "name": "frontend-design-audit",
  4. "owner": {
  5. "name": "mistyhx"
  6. },
  7. "plugins": [
  8. {
  9. "name": "frontend-design-audit",
  10. "source": "./",
  11. "description": "Audit and improve front-end usability using 15 established design principles. Acts as a Senior UX designer/engineer reviewing your interface end-to-end.",
  12. "version": "1.0.0",
  13. "author": {
  14. "name": "mistyhx"
  15. },
  16. "homepage": "https://github.com/mistyhx/frontend-design-audit",
  17. "tags": ["ux", "usability", "audit", "design", "accessibility", "frontend", "heuristics"]
  18. }
  19. ]
  20. }
README.md · README · 170 lines

View this file on GitHub (read at the repository's current version: the scan did not record which commit it read)

  1. # Frontend Design Audit
  2. A Claude Code skill that audits and improves the usability of existing front-end interfaces. It evaluates your UI code against 15 established design principles, identifies problems, rates severity, and helps fix what it finds.
  3. ## What It Does
  4. Think of it as a Senior UX Engineer/Designer reviewing your interface end-to-end. It inspects HTML, CSS, JavaScript, React, Vue, Svelte — any front-end code — and produces a structured audit report with:
  5. - **Findings** rated on a 0–4 severity scale (catastrophe → cosmetic)
  6. - **Principle references** linking each issue to established usability research
  7. - **Concrete fixes** with code-level detail, not vague suggestions
  8. - **Strengths** — what your interface already does well
  9. Then it implements the fixes: accessibility attributes, semantic HTML, visual hierarchy improvements, design system extraction, interaction patterns, and more.
  10. ## The 15 Principles
  11. | # | Principle | Examples of What It Catches |
  12. |---|-----------|----------------|
  13. | 1 | Visibility of System Status | Missing loading states, no feedback on actions |
  14. | 2 | Match Between System and Real World | Jargon, unintuitive labels, wrong mental models |
  15. | 3 | User Control and Freedom | No undo, no escape, no back button |
  16. | 4 | Consistency and Standards | Inconsistent patterns across pages |
  17. | 5 | Error Prevention | Missing validation, no confirmation for destructive actions |
  18. | 6 | Recognition Over Recall | Empty states, missing breadcrumbs, hidden options |
  19. | 7 | Flexibility and Efficiency | No keyboard shortcuts, no power-user paths |
  20. | 8 | Aesthetic and Minimalist Design | Flat typography, poor spacing, visual clutter |
  21. | 9 | Error Recovery | Unhelpful error messages, no recovery guidance |
  22. | 10 | Help and Documentation | Missing onboarding, no contextual help |
  23. | 11 | Affordances and Signifiers | Unclear clickability, flat button hierarchy |
  24. | 12 | Structure | Poor grouping, weak section boundaries |
  25. | 13 | Accessibility | Missing alt text, no focus indicators, poor contrast |
  26. | 14 | Perceptibility | Low contrast, invisible state changes |
  27. | 15 | Tolerance and Forgiveness | Data loss on error, inflexible inputs |
  28. ## Installation
  29. ### Recommended: Plugin Marketplace (one-time setup, works across all projects)
  30. 1. Start Claude Code in any project:
  31. ```bash
  32. cd your-project
  33. claude
  34. ```
  35. 2. Add the marketplace:
  36. ```
  37. /plugin marketplace add mistyhx/frontend-design-audit
  38. ```
  39. 3. Open the plugin menu:
  40. ```
  41. /plugin menu
  42. ```
  43. 4. Select and install `frontend-design-audit` from the list.
  44. 5. Restart Claude Code.
  45. ### Alternative: Load Directly (per-session)
  46. Clone this repo, then start Claude Code from your project with a relative path to the plugin:
  47. ```bash
  48. git clone https://github.com/mistyhx/frontend-design-audit.git ~/plugins/frontend-design-audit
  49. cd your-project
  50. claude --plugin-dir ../plugins/frontend-design-audit
  51. ```
  52. Or use an absolute path:
  53. ```bash
  54. claude --plugin-dir ~/plugins/frontend-design-audit
  55. ```
  56. ## Usage
  57. ### Full Audit (default)
  58. Evaluates your UI, presents a report, discusses findings with you, then implements fixes:
  59. ```
  60. /frontend-design-audit
  61. ```
  62. ### Evaluate Only
  63. Produces the audit report without implementing changes:
  64. ```
  65. /frontend-design-audit:evaluate
  66. /frontend-design-audit:evaluate src/pages/
  67. /frontend-design-audit:evaluate App.tsx
  68. ```
  69. ### Improve
  70. Implements fixes from a previous evaluation, discussing each change:
  71. ```
  72. /frontend-design-audit:improve
  73. ```
  74. ### Quick Mode
  75. Auto-evaluates and fixes without discussion — good for rapid iteration:
  76. ```
  77. /frontend-design-audit:quick
  78. /frontend-design-audit:quick src/components/Dashboard.tsx
  79. ```
  80. ### Live Website Audit
  81. Pass a URL to audit a live site (report only — no code changes):
  82. ```
  83. /frontend-design-audit https://example.com
  84. ```
  85. ## Example
  86. Here's a task management dashboard before and after the audit — the skill identified and fixed issues with visual hierarchy, spacing, accessibility, and consistency:
  87. **Before**
  88. ![Task dashboard before audit](examples/screenshots/task-dashboard-before.png)
  89. **After**
  90. ![Task dashboard after audit](examples/screenshots/task-dashboard-after.png)
  91. ### What Changed
  92. The original dashboard had solid bones — working drag-and-drop, a modal with focus trapping, responsive layout. But the audit found 22 issues across accessibility, visual hierarchy, and interaction design. Key improvements:
  93. **Design system extraction** — Replaced 40+ hardcoded values (colors, spacing, font sizes) with CSS custom properties. One spacing scale, one type scale, one color palette used consistently across every component.
  94. **Visual hierarchy** — Stat card numbers grew from `2rem` to `2.5rem` with labels shrunk to micro-size uppercase, creating a clear "big number, small label" dashboard pattern. Column headers differentiated from task titles via uppercase + letter-spacing. Section spacing went from uniform 1-2rem to a deliberate hierarchy (tight within cards, generous between sections).
  95. **Accessibility** — Added skip navigation, `aria-current="page"` on active nav with visible highlight, `aria-label` on sidebar nav lists, keyboard-navigable dropdown menus (Arrow keys, Escape), keyboard task movement between columns (not just drag-and-drop), inline form validation with `aria-invalid`, and proper `<time>` elements.
  96. **Interaction polish** — Buttons gained `:active` pressed states and `:disabled` styling. Activity feed dots replaced with distinct icons (checkmark, arrow, speech bubble) so category isn't color-only. Completed tasks use a CSS class instead of inline `opacity`.
  97. The `examples/` directory contains more before/after pairs:
  98. | Site | Before | After | Report |
  99. |------|--------|-------|--------|
  100. | Coffee shop landing page | `coffee-shop.html` | `coffee-shop-improved.html` | `reports/coffee-shop-report.md` |
  101. | SaaS pricing page | `saas-pricing.html` | `saas-pricing-improved.html` | `reports/saas-pricing-report.md` |
  102. | Task dashboard | `task-dashboard.html` | `task-dashboard-improved.html` | `reports/task-dashboard-report.md` |
  103. Open any pair in a browser to see the difference.
  104. ## How It Works
  105. The skill follows a structured workflow:
  106. 1. **Discover** — Reads your front-end code and identifies the interface type, tech stack, and user flows
  107. 2. **Evaluate** — Systematically inspects against all 15 principles, checking component-level, system-level, and visual design issues
  108. 3. **Report** — Presents findings in a structured format with severity ratings, principle references, and actionable fixes
  109. 4. **Implement** — Establishes a design foundation (CSS tokens), applies fixes through that system, then runs a coherence pass to ensure everything holds together
  110. 5. **Verify** — Post-implementation review to catch issues that fixes introduced
  111. ## License
  112. MIT

Ratings and comments

Sign in to rate this skill.

Sign in

Free to use. If it’s helped, pass it on.