Is tailwindcss.com vibe coded?

Reading this score

tailwindcss.com landed on 75/100, which puts it in the shipped straight from the chat window band. That number is not a percentage and not a probability — it is strength of evidence: 103 points of tells, damped by craft, less 22 points of deliberate decisions, mapped through one logistic curve.

What pushed it up

• The indigo-to-violet gradient +15 — The loudest tell of 2026, fully deployed. It descends from Tailwind's indigo-500 and from Notion/Vercel-era marketing, which taught the models that innovative software is purple.
• shadcn/ui class signatures +12 — 2 shadcn/ui utility signatures in the markup.
• Accessibility gaps +12 — 2 images with no alt, 1 icon-only buttons with no accessible name. Adding these requires knowing why they matter.
• Copy that never says who it is for +9 — 1266 words, and still no price, no contact route and no named audience. The page describes a category, not a business.
• No way to actually make contact +9 — The page asks for the sale and then offers no phone number, no address, no email and no form. For a local business site this is the whole failure.
• rounded-2xl, soft shadow, 1px grey border — on everything +8 — 33 extra-rounded cards, 7 oversized shadows and 0 hairline borders — the untouched shadcn card, applied to content of wildly different importance.
• Glowing orbs behind a permanently dark page +8 — 24 glow surfaces over a permanently dark ground. Learned from crypto and AI launch pages, where it was atmosphere. Here it decorates nothing.
• Cards inside cards +8 — 14 card surfaces sitting inside other card surfaces. Everything gets a box, everything gets equal emphasis, and nothing reads as primary.

What pulled it down

• Deliberate social preview −9 — Open Graph title and image were both authored.
• Hand-written ARIA −7 — 69 explicit accessibility attributes.
• CSS custom property system −6 — 319 CSS custom properties — a real token layer.

Craft we looked for and did not find

These are the actionable half of the report. None of them are hard, and every one of them would have moved the number.

• Structured data
• Skip-to-content link
• prefers-reduced-motion honoured
• Semantic landmarks
• Self-hosted typography
• Hand-authored stylesheet
• No utility-class soup
• Canonical URL

What this scan cannot see

One request, no JavaScript executed. So everything below is invisible to us, and a page can be excellent or awful at all of it without moving the score:

• Domain registration age — needs WHOIS.
• Whether the nav's /about and /pricing actually resolve — needs a crawl, not one fetch.
• package.json dependency count, orphaned code, clashing abstractions, test coverage — needs the repo.
• Backend security shortcuts: string-built SQL, verify=False, missing auth on endpoints — needs the source.
• Whether row-level security or Firebase rules are actually switched on — needs the project.
• Console errors, hydration warnings and runtime 404s — needs a browser executing the page.
• Real Lighthouse numbers and horizontal scroll at 375px — needs a rendered viewport.
• Whether a JS-handled form posts anywhere — needs a submitted request.