Antislop
A guide your AI reads before it designs or writes anything, so the result is not one everybody has already seen.
It is six Markdown files. There is nothing to install, and it works with any AI tool.
The same model built each pair from the same one-line request. The left column had no guide. The right column had this one. All twenty pages are in evals/out/sonnet.
Use it
Paste this into ChatGPT, Claude, Cursor, Codex, Gemini, or any AI tool that can open a link, before you ask for a UI:
Before you design or build any UI, fetch this file and follow it:
https://raw.githubusercontent.com/richyrach/antislop/main/GUIDE.md
If your tool cannot open links, paste in the contents of GUIDE.md.
To keep a copy in your project:
curl -fsSL https://raw.githubusercontent.com/richyrach/antislop/main/GUIDE.md -o DESIGN.md
Then add one line to CLAUDE.md, AGENTS.md or your Cursor rules: Before any UI work, read DESIGN.md and follow it.
To install it as an agent skill, with the reference files included:
npx skills add richyrach/antislop
What it measured
Ten short requests, such as "I need a website for my family's bakery in Lisbon", were each sent to Claude Sonnet twice: once alone, once with the guide. A script then counted 27 known marks of AI-built pages in each result.
| Without the guide | With the guide |
|---|
| Marks per page, average | 4.4 | 1.3 |
| Pages with 4 or more marks | 7 of 10 | 0 of 10 |
| Pages with 0 or 1 marks | 1 of 10 | 5 of 10 |
| Pages with invented proof (reviews, founding dates, counts) | 3 of 10 | 0 of 10 |
| Pages using only the default sans-serif | 8 of 10 | 0 of 10 |
Read this with care:
- It is small. Ten requests, one page each way, one model. It has not been run on GPT or Gemini.
- The guide and the counting script have the same author, and the script counts the marks the guide names. Part of the gap is the guide teaching to its own test.
- A count of marks does not say a page is good. Look at all ten pairs and judge for yourself.
- Some marks survive. Five of the ten guided pages still had small labels in spaced capitals, and two used cream paper with a serif.
- The guide was revised once after a first run, because its pages scored well and looked bare. Those pages are kept in
evals/history.
The method, the per-page results and how to rerun it are in evals/.
What is in it
| File | What it tells the AI |
|---|
| GUIDE.md | The core. Get the real material, take the design from the subject, meet a standard, never invent content. About 2,100 words. |
| reference/visual-design.md | Composition, hierarchy, colour, space, finish, and a self-review. |
| reference/type.md | How to choose a typeface, how to self-host one, which fonts are already on each device, and other scripts. |
| reference/images.md | Where to find real pictures, how licences work, and what to do when there are none. |
| reference/writing.md | How AI text gives itself away, in punctuation, structure, vocabulary and tone, and how to write instead. |
| reference/product-ui.md | Dashboards, tables, forms, settings, and every state a screen can be in. |
The core guide tells the AI which reference files to read for the task in front of it.
Why it is not a list of bans
Ask an AI for a web page and you get one of a few pages. The field guide shows the four most common kinds and the marks that give each away.
The second and third kinds exist because people told their AI to avoid the first. A model that is only told what to avoid moves to its next most likely answer, and that answer is the same for everyone.
This repo did it too. Its first "good" example was a cream page with a serif, a red accent and a line of facts joined by dots. That is the second kind, and it is now plate 2. Its first guide then produced pages that avoided every mark and had nothing on them.
So the guide gives the AI a way to work and a standard to meet:
- Find the real material first, pictures included, and ask for what is missing.
- Write down what belongs to the subject's world, and take colour, type and layout from that.
- Borrow the layout the subject already uses: a menu, a timetable, a receipt, a spec sheet.
- Swap in a competitor's name. If the design still fits, start again.
- Meet the standard: a composed first screen, one place the eye lands, type chosen for a reason, something worth looking at.
- Never invent a customer, a figure, a review or a logo. Leave a marked slot for the owner instead.
- Write plainly, with no sentence a competitor could print unchanged.
- Pass a craft floor: contrast, keyboard, phone widths, right-to-left, and no third-party hosts.
Two things it stresses that the larger tools' READMEs do not mention:
- Blocked networks. The page must render with every third-party host unreachable. A blocking request to a font CDN is a blank page for people on filtered networks.
- Right-to-left and non-Latin scripts. Logical properties, a typeface drawn for the script, no letter-spacing or italics on Arabic-script text.
How it compares
There are larger projects for this, and they do more. This table is from their READMEs in November 2026.
여기까지가 README 앞부분입니다. 나머지는 원문에서 읽을 수 있습니다. README 전문 보기 ↗
