How we judge
Every project gets one word: Sloppy or Not. No number is ever shown to anyone. Here is everything that goes into that word.
Measured checks
Before any opinion, we measure. Does the page load? How fast is it? Can people using screen readers get through it? Does it work on a phone? Does it send basic security headers? Does it throw errors? A site that doesn't load is Sloppy, and nothing else runs.
Six questions the agent answers from your site
| # | Question | Slop sounds like |
|---|---|---|
| A1 | Can a stranger tell what this does and who it is for from the first screen? | A hero line that could sit on any site. |
| A2 | Does it actually do the thing, or only promise it? | A landing page with a waitlist and no product. |
| A3 | Would you recognize it a week later, or does it look like a template? | Default gradients, stock icons, three identical feature cards. |
| A4 | Was the copy written by someone who cares? | Filler like "unlock the power of" and "seamless". |
| A5 | Can you reach the core action without hitting a dead end? | Broken links, lorem ipsum, buttons that go nowhere. |
| A6 | Do the claims match what is on the page? | "Trusted by thousands" on a project that is two days old. |
Nine questions only you can answer
Choose "Manually answer questions" and these count toward your verdict. Dot, our agent, never writes these answers for you. Good answers can rescue a borderline site. They cannot rescue a broken one.
| # | Question | What we listen for |
|---|---|---|
| 1 | Who is this for, and what problem are they facing? | A specific person and a real problem, not "everyone". |
| 2 | If this works perfectly, what changes for them? | A concrete outcome for that person, not "an app for X". |
| 3 | Who could this hurt or leave out, and what did you do about it? | Named risks and people left out, and what was done about them. |
| 4 | Does the way it looks and sounds fit the people it's for? | Design and tone chosen for the audience, not a default template. |
| 5 | What already exists in this space, and why isn't it enough? | Knowing the landscape. A specific gap. |
| 6 | What's the one thing here you haven't seen done before? | A fresh angle, even a small one, named plainly. |
| 7 | Who did you test it with, what did they say, and what did you change? | Real people, real feedback, and a change it caused. |
| 8 | Where did you use AI, and where did you step in and overrule it? | AI used with judgment, and a moment the builder overruled it. |
| 9 | What did you learn and take away from building this? | Something specific that changed, not "we learned a lot about APIs." |
What never touches your verdict
Swipes from other people on the Judge screen. They feed the weekly State of Slop email, not your verdict.
Roast me. It only decides whether your verdict may appear on the public board.
Resubmitting. Your first verdict for a link is saved, so submitting the same link again does not change it.
Test my project
Judge others' projects