Gesso Anti-Slop plugin

A deterministic HTML and CSS check for 73 tells of generated UI, with auto-fixes and the /gesso-critique command.

  • 94 ★ on the repository
  • Last commit
  • MIT
Plugin

Extended access

Why this level

  • The agent runs `npx` and applies auto-fixes that edit HTML and CSS in the project
All reasons and checks

gesso-build/skills

Install

In your terminal, with SkillFoxx CLI

npx skillfoxx add plugins/gesso-anti-slop

Detects the agents on your machine, shows the access level and pins the version.

Other ways to install

Access and checks

How we review

Extended accessThe tool runs code or makes network calls and only reads external data.

  • The agent runs `npx` and applies auto-fixes that edit HTML and CSS in the project

This is third-party code. Review the repository files before installing.

What it does

Gesso Anti-Slop reads `.html` files including inline styles and `style` blocks and looks for 73 tells of generated UI: a gradient-clipped headline, an unchosen indigo accent, puffy stacked shadows, emoji standing in for icons, a row of equal dots faking a chart, an em dash mid-sentence, a raw `$1,842,000` figure. Each tell is a documented detector with an exact threshold, and most have an idempotent auto-fix that preserves the design intent. Simple tells are found with regular expressions, structural ones by parsing the markup without executing it. The `/gesso-critique page.html` command prints a verdict with evidence, applies fixes on request and then gives a separate second opinion. The installed skill runs the check on its own before the agent shows or commits HTML and CSS. The CLI works in CI as well: `npx -y @gessobuild/anti-slop check dist/ --json`.

Who it is for. Designers and developers who ship agent-built interfaces and want to filter template tells before showing and committing.

Good fit when

  • An agent built a landing page and before showing the client a list of obvious generation tells is needed.
  • A static export or prototype must be checked in CI with JSON output and an exit code.
  • Safe auto-fixes for money typography and shadows are needed that a rerun will not break.
  • You want a second opinion on a screen after the deterministic verdict.

Not a fit when

  • The code is JSX or TSX: the detector parses only HTML, so export the page first.
  • You need a full design audit with accessibility and performance: the set checks only the listed tells.
  • The brand deliberately uses flagged devices such as a gradient headline.

Example request

Check page.html for generated-design tells and apply the auto-fixes.

Limitations

The detector reads only `.html` including inline styles and `style` blocks. JSX and TSX sources must be rendered or exported first. Checks are deterministic and rest on thresholds in `skills/anti-slop/references/rules.md`: they find tells but do not judge composition or meaning. Auto-fixes are idempotent, yet should be applied under version control. Installation copies the skill and command into the project `.claude/`, with `--global` into `~/.claude/`. In the plugin the command is `/gesso:critique`, other agents have no slash command and the check is requested by asking. For one-off checks `npx` is enough.

How to disable. Delete the skill and command from the project `.claude/` or `~/.claude/` and uninstall the plugin with `/plugin uninstall gesso@gesso`.

FAQ

How many rules does the check have?

73 tells of generated UI, each with an exact threshold, described in detail in `rules.md`.

How do I check without installing?

With `npx -y @gessobuild/anti-slop check page.html`, which exits with 1 on slop. For a folder add `--json`.

How do I install for Codex or Cursor?

Through `npx skills add Gesso-Build/skills`; there is no `/gesso-critique` command there, so ask for the check in words.

Does the check execute my code?

No, structural tells are found by parsing the markup and nothing is executed.

How do I install the Claude Code plugin?

`/plugin marketplace add Gesso-Build/skills`, then `/plugin install gesso@gesso`. The command is `/gesso:critique`.

Discussion

No questions or reviews yet.

Plugins

A 147-rule design check that finds AI-interface tells, fixes the mechanical ones and hands the rest to an agent skill

CLIExtended access247Repository stars

A skill for interfaces without the generic AI look: typography, color, motion, component states and a critique of the result.

SkillMinimal access95Repository stars

A rule set for coding agents that filters out generic AI look in UI, copy and code comments

SkillExtended access9.1KRepository stars

The /taste skill turns a URL into design tokens and trade-off principles, with ready rules for Cursor and Claude Code

SkillExtended access462Repository stars

Finds AI-look tells in generated frontend, from purple gradients to cream and terracotta, and rewrites the interface

SkillExtended access161Repository stars

An MCP server and skill for interfaces: 31 design systems for shadcn/ui, UI and UX principles and accessibility review for agent-written code

MCP serverExtended access576Repository stars

README in short

The README lists the typical tells, install options for Claude Code and other agents, the critique command and the CLI mode for CI. All installed files are committed word for word.

README badge

Report a problem