Slop*Detector

SUSPICIOUSLY VIBEY — slop score 54/100

The evidence here points pretty clearly toward AI-generated design and copy, and the score reflects that without much ambiguity. The visual layer is a checklist of generated-UI defaults: glassmorphism panels, a gradient hero, untouched Inter/shadcn defaults paired with the telltale Instrument Serif accent, and the FRESH / '01 ORCHESTRATOR' kicker-headline-blurb rhythm repeated section after section. The writing has its own tells, most damning the em dash usage ('huge.log — 2.1 GB') and the flat 'Settings, not config files.' reframe, both textbook LLM punctuation and phrasing habits. None of these findings are individually fatal, pill tags and feature grids show up on plenty of hand-built sites too, but the sheer density and consistency across layout, typography, and copy is what pushes this to suspiciously vibey rather than merely templated. I'd put solid confidence behind the verdict given how many independent signals converge on the same conclusion.”}eedback stripped per instructions.} wait I need valid JSON only. Correcting below.} {

Findings

• Feature-tile grid — Equal-width card grids of 3–4 identical tiles (icon, subheader, blurb) are the signature layout block of generated landing pages.
• Pill tags — Little fully-rounded pill badges sprinkled across the page ("New", "Beta", category chips) are a default garnish of vibe-coded UI.
• Gradient backgrounds / gradient text — Large gradient washes and gradient-clipped headline text (usually blue→purple) are the default decoration of generated UI.
• Untouched shadcn/Tailwind defaults — shadcn components, lucide icons, and Inter/Geist/Space-Grotesk font stacks left at their defaults mean the model picked the design, not a person. Instrument Serif as an accent font is a separate, independently corroborated tell.
• Glassmorphism — Frosted-glass backdrop-blur panels are a recurring generated-UI decoration.
• Tiny all-caps mini header above hero — A small uppercase label 'FRESH' sits above the main headline, and later a numbered section repeats the same pattern with '01 ORCHESTRATOR' above 'Every task gets its own workspace.'
• Numbered step filler section — The '01 ORCHESTRATOR' numbering is applied to what appears to be a single feature description rather than a genuine multi-step sequence, a decorative borrowing from How-It-Works patterns.
• Kicker + headline + blurb repeated hierarchy — The page repeats a three-level rhythm of small label, large italicized headline, and short explanatory paragraph across multiple sections (hero, 'Light enough to run almost anywhere', and the orchestrator section), creating the same generated cadence even without cards.
• Italicized serif accent word in headline — Headlines mix a serif display face with italicized words for emphasis/warmth ('terminal IDE.', 'almost anywhere.', 'workspace.'), a pattern flagged when italic serif accents are dropped into headlines for stylistic effect.
• Feature tag strip styled like pill list — A horizontal marquee of plain-text feature tags (REVIEW DIFF, GIT LOG, GIT BLAME, etc.) separated by dots — this is explicitly exempted by the guide as a tag strip rather than a feature-grid, so it's noted only as a weak/non-damning observation.
• Large sections of blank dark space — Several consecutive screenshot slices show almost entirely empty near-black background with only a thin text line or faint divider, consistent with scroll-triggered reveal animations that render as blank in a static capture.
• Em dashes — Em dashes are the single most reliable punctuation tell of LLM copy. Human marketing copy almost never uses them; models reach for them constantly.
• 'X, not Y' appositive reframe — The section header 'Settings, not config files.' uses the banned contrastive reframe construction the guide flags as a default rhetorical tic.
• Em dash usage — The guide bans em dashes outright; one appears as a label separator rather than being rewritten with a comma or parenthesis.
• One-word punch sentence — A single-word fragment used for dramatic emphasis in a heading mirrors the 'Off.' 'Done.' pattern the guide calls out, though it's an isolated instance.
• Repeated rule-of-three bullet triads — Nearly every feature section (Themes, Settings, Performance, Extensible, Language Servers) lands on exactly three bullet points, a rhythmic pattern the guide flags when it recurs across a document, though this could equally be deliberate template design rather than generated prose.