跳至正文
OpenAgentSkill
浏览已开放 · 目录记录日期 2026-11-21 · 自动更新和账户服务暂时关闭。
设计与 UI

anti-slop-frontend

A mechanical, countable anti-slop checklist for AI-generated frontend. Catches the specific signatures an undirected model defaults to: AI-purple glows, Inter-everywhere, em-dashes, div-based fake screenshots, eyebrow-on-every-section, beige+brass \"premium\" palettes, generic Jane Doe / Acme data. Advisory layer that pairs with frontend-mockup-loop (which owns the cite-a-source loop plus WCAG gates) but works standalone in any React/Tailwind/HTML project. Triggers: \"does this look AI-generated\", \"anti-slop pass\", \"remove the AI tells\", \"why does this look templated\", \"design review for slop\".

BlackBeltTechnology · 已有 AI 审核记录

安装与使用

运行命令前先阅读来源与依赖说明。复制命令不会自动安装或执行。

npx skills add BlackBeltTechnology/pi-agent-dashboard --skill anti-slop-frontend

技能说明


name: anti-slop-frontend description: "A mechanical, countable anti-slop checklist for AI-generated frontend. Catches the specific signatures an undirected model defaults to: AI-purple glows, Inter-everywhere, em-dashes, div-based fake screenshots, eyebrow-on-every-section, beige+brass "premium" palettes, generic Jane Doe / Acme data. Advisory layer that pairs with frontend-mockup-loop (which owns the cite-a-source loop plus WCAG gates) but works standalone in any React/Tailwind/HTML project. Triggers: "does this look AI-generated", "anti-slop pass", "remove the AI tells", "why does this look templated", "design review for slop"." license: MIT metadata: author: blackbelt-technology version: "0.1" adapted_from: "Leonxlnx/taste-skill (design-taste-frontend, MIT) - countable rules distilled, stack-coupling removed, scoped universal vs marketing-only."

anti-slop-frontend

A flat, mechanical checklist of the concrete signatures an undirected model emits when it tries to "look designed." Every rule here is countable or binary - you can mechanically verify pass/fail, not argue taste. That is the whole point: "it looks better" is not a check; "eyebrow count > ceil(sections/3)" is.

What this is, and is NOT

  • IS an advisory catalog of AI-tells, scoped by surface kind.
  • IS standalone - works with no tooling, in any React/Tailwind/HTML project.
  • IS NOT a design philosophy, a loop, or a gate. It scores; it never blocks.

Relationship to frontend-mockup-loop

Different jobs, intentionally separate:

frontend-mockup-loopanti-slop-frontend (this)
Shapeground→contract→mockup→test→fix→learn loopflat checklist
Basiscite an external public rule (Nielsen, WCAG, Laws of UX)codified AI-tell catalog
Authorityowns the hard gates (WCAG-AA, severity-4)advisory only, drives the fix list
Domainproduct UI, dashboards, flowsuniversal tells + marketing-surface tells

When both are present: the loop's a11y floor and cite-a-source rule win. This skill feeds concrete failing items into the loop's FIX step. It never overrides a gate, and a tell here is never a reason to violate a cited rule.

Honesty note: these rules are curated taste, hardened into countable form. They are good defaults, not laws of nature. Every rule has an override path: when the brief explicitly asks for the "banned" thing, it is allowed - execute it with intent, not by accident.


The three dials (set once, up front)

State these before reviewing or generating. They gate which rules fire and how hard.

  • VARIANCE (1-10) - 1 = perfect symmetry, 10 = artsy chaos
  • MOTION (1-10) - 1 = static, 10 = cinematic/physics
  • DENSITY (1-10) - 1 = art-gallery airy, 10 = cockpit/packed-data

Infer from the brief; don't silently use a baseline. Dashboards/data UI live high on DENSITY and low on VARIANCE/MOTION. Landing/portfolio live the opposite.


PART A - Universal tells (apply to EVERY surface, dashboards included)

These fire regardless of surface kind. A dense admin panel is just as guilty of AI-purple and Inter-everywhere as a landing page.

A1. Color

  • No AI-purple/blue glow as default. No automatic violet button glows, no random neon gradients ("the Lila tell"). Neutral base (Zinc/Slate/Stone) + ONE high-contrast accent. Override: brand literally is purple.
  • Max 1 accent color, saturation < 80% default. Lock it: the same accent on the whole page. A warm-grey UI does not grow a blue CTA in section 7.
  • One neutral temperature per project. Don't drift warm-grey ↔ cool-grey.
  • No pure #000000 / pure #ffffff. Off-black (zinc-950) and off-white; pure values kill depth.

A2. Typography

  • Inter is discouraged as the default. Reach past it (Geist, Outfit, Cabinet Grotesk, Satoshi) unless the brief wants neutral/Linear-style or is accessibility-first. Override exists.
  • Serif is very discouraged as default. "Feels premium/creative" is not a reason. Specifically banned as defaults: Fraunces, Instrument Serif. Serif only when the brief names one or the family is genuinely editorial/luxury/heritage.
  • Emphasis = italic/bold of the SAME family. Never inject a random serif word into a sans headline for "visual interest."
  • One corner-radius scale per page (all-sharp / all-soft / all-pill), or a documented rule followed everywhere.

A3. The em-dash ban (the #1 tell)

  • Zero — and zero –-as-separator anywhere visible. Headlines, labels, pills, body, quotes, attribution, captions, buttons, alt text. No "sparingly." Replace with a period, comma, colon, parentheses, line break, or a spaced hyphen -. Ranges use a plain hyphen (2018-2026, €40-80k).
  • Mechanical check: grep the rendered output for —/–. Any hit = fail.

A4. Fake data ("Jane Doe" effect)

  • No generic names. "John Doe / Sarah Chan / Jack Su" → realistic, locale-appropriate names.
  • No generic brand names. "Acme / Nexus / SmartFlow / Cloudly" → contextual names that sound real.
  • No fake-perfect numbers. 99.99%, 50%, 1234567 → organic values (47.2%, real-looking phone formats). Fake-precise engineering specs (5.8mm, 4.1×) are banned unless from real data or labeled mock.
  • No filler verbs. "Elevate / Seamless / Unleash / Next-Gen / Revolutionize" → concrete verbs.
  • No generic avatars (SVG "egg", default user glyph) → believable placeholders.

A5. Assets & icons

  • No div-based fake screenshots. Building a fake dashboard/terminal/task-list out of styled <div>s is the single biggest tell. Use a real screenshot, a generated image, a real mini component preview, or nothing.
  • No hand-rolled SVG icons. Use one icon family (Phosphor / HugeIcons / Radix / Tabler), standardized stroke width. Lucide only on explicit request.
  • **No hand-rolled decorative S
阅读完整来源 ↗