Skip to content
Skills Library
Design & UX · Review & audit

audit

/audit

Score an existing React + Tailwind site against the anti-slop checklist and produce DESIGN-AUDIT.md with evidence. Use when the user says their site "looks AI-generated", "looks generic", "feels off", asks "why is my site ugly", or wants a design audit/score before improving it. Read-only — never edits source.

Repository
unslop ↗
Licence
MIT
Last repository change
15.06.2026

Assessment and security

100/ 100Class: good
Format25 / 25
Frontmatter with name and description, valid name, description up to 1,024 characters, name matching the folder.
Discoverability25 / 25
Description explains when to use the skill, has a reasonable length and uses third person.
Content35 / 35
At least 150 words and at most 500 lines, headings, step lists, examples or code.
Hygiene15 / 15
No placeholders such as TODO, no Windows paths, with a licence.
Riskno signals detected in the scan
Files in this package
1
Scripts
0
HTML comments
0
URLs in SKILL.md
0
Deprecation

No signals detected. Repository changed on 15.06.2026, without references to retired models or APIs.

Licence

MIT, open: use and modify while retaining author attribution.

What it does and when to use it

Score an existing React + Tailwind site against the anti-slop checklist and produce DESIGN-AUDIT.md with evidence. Use when the user says their site "looks AI-generated", "looks generic", "feels off", asks "why is my site ugly", or wants a design audit/score before improving it. Read-only — never edits source.

Triggers from the description

looks AI-generatedlooks genericfeels offwhy is my site ugly
Original author description

Score an existing React + Tailwind site against the anti-slop checklist and produce DESIGN-AUDIT.md with evidence. Use when the user says their site "looks AI-generated", "looks generic", "feels off", asks "why is my site ugly", or wants a design audit/score before improving it. Read-only — never edits source.

How it works

  1. Preconditions
  2. Procedure
  3. Rules
Original SKILL.md headings · 58 lines, 366 words
SKILL.md preview
---
name: audit
description: Score an existing React + Tailwind site against the anti-slop checklist and produce DESIGN-AUDIT.md with evidence. Use when the user says their site "looks AI-generated", "looks generic", "feels off", asks "why is my site ugly", or wants a design audit/score before improving it. Read-only — never edits source.
---

# Design Audit

Audit the current project's visual design and produce a scored, evidence-backed
`DESIGN-AUDIT.md`. This skill is **strictly read-only on source code** — it writes
only the audit report and screenshots.

## Preconditions

1. Confirm the project is React + Tailwind (look for `tailwind.config.*` or the
   Tailwind v4 CSS import, plus React in package.json). If it isn't, stop and say:
   v1 of unslop supports React + Tailwind only.
2. The site must be viewable. Find the dev command (`npm run dev` or equivalent)
   and the port. Start it in the background if not already running.

## Procedure

1. **Capture.** Run the bundled screenshot script against the running site:
   ```bash
   node "${CLAUDE_PLUGIN_ROOT}/scripts/screenshot.mjs" <url> ./unslop/screenshots
   ```
   It captures 375 / 768 / 1024 / 1440 px full-page shots and reports horizontal
   overflow per viewport. If Playwright is missing, it prints install instructions —
   follow them, then re-run.

2. **Deterministic checks.**
   ```bash
   node "${CLAUDE_PLUGIN_ROOT}/scripts/slop-scan.mjs" .
   node "${CLAUDE_PLUGIN_ROOT}/scripts/contrast-check.mjs" <url>
   ```
   `slop-scan` greps the source for slop tells (stock palette, transition-all,
   arbitrary px values, uniform radius, weight sprawl) with file:line evidence.
   `contrast-check` reports WCAG AA failures on the rendered page.

3. **Visual evaluation.** Read all four screenshots. Walk
   `${CLAUDE_PLUGIN_ROOT}/rules/anti-slop-checklist.md` item by item — every item
   is PASS / FAIL / N-A with evidence (file:line from the scans, or a screenshot
   observation named precisely, e.g. "1440px: hero is centered headline + two
   buttons + 3-col icon grid → L1 FAIL"). Read key source files to confirm
   suspected failures; do not guess.

4. **Report.** Write `unslop/DESIGN-AUDIT.md`:
   - **Overall score** (passes ÷ applicable × 100) and per-category scores.
   - **Failures with evidence**, grouped by category, referencing checklist IDs.
   - **Top 5 fixes by visual impact**, ordered, each mapped to checklist IDs.
   - Paths to the screenshots.

5. **Tell the user** their score, the 2–3 most damning findings in plain language,
   and the next step: run `/unslop:interview` to define a design lane, then
   `/unslop:retheme` to fix it.

## Rules

- Never modify source files, configs, or styles. Audit only.
- Every failure needs evidence a stranger could verify. "Feels generic" is banned.
- If the dev server can't start, report the build error and stop — that's a
  prerequisite bug, not a design finding.

Versions

RepositoryScoreLicence
This page · aahil62/unslop100MIT
marcel-bich/marcel-bich-claude-marketplace100MIT
jeremylongshore/tons-of-skills-marketplace100MIT
friendlyinternet/nuxt-crouton100MIT
userKael/rastro100MIT
Archont561/qgis-agent-harness100MIT
lilly-logic-labs/lll-skills100MIT
Come-In-Labs/agent-skills100MIT
minanyang/10x-agent100MIT

Database snapshot: 13.11.2026 · package version c7a6613a0916 (SHA-256 digest of the entire package)

Downloads in the last 30 days: 0 · ranking

Report a problem with this skill: harmful content, incorrect descriptions or an author’s removal request.

Similar skills

  • 100anti-slop
    Research-backed UI/UX design judgment for creating, refining, and auditing user interfaces. Use when building new UI (pages, screens, components, dashboards, landing pages), improving or polishing an existing interface, or reviewing a design for hierarchy, typography, color,…
  • 100slop-eval
    Objectively evaluate a UI/web design against the pols.dev anti-slop design law: detect catalogued slop tells with cited evidence, score 8 weighted axes (color, type, components, layout, motion, execution, signature, cohesion), and emit a Slop Report with a 0–100 Slop Index and…
  • 100anti-slop
    Creative direction, design systems and frontend engineering that eliminate generic AI-generated UI. Use whenever building, redesigning, improving or auditing a website, landing page, portfolio, SaaS app, dashboard, e-commerce or agency site, or any frontend — and whenever the…
  • 100frontend-anti-slop
    This skill should be used when auditing React/Next.js source for Hallmark-adapted anti-AI-slop patterns via a deterministic Tailwind/JSX scanner.
  • 100anti-slop-design
    Eliminates generic AI-generated design ("AI slop") from any front-end you build or review — web or mobile. Use whenever generating, reviewing, refactoring, or critiquing a website, landing page, dashboard, web app, iOS or Android app, React Native or Flutter screen, component,…
  • 100slop-check
    Use when asked to audit, "unslop" or fix a web app or site that looks AI-made, generic, templated or vibe-coded (AI slop, design slop, UX slop), or to check an interface before shipping for design, copy, UX, accessibility and dark patterns. Also for French requests: « déslopper…

Feedback and reports

Your message goes to Bartosz Sokoliński. An email address is needed only for a reply. See the privacy policy.