Worked examples sokoon.xyz
Is sokoon.xyz vibe coded?
Ours. Scanned with the same detectors as everything else. We fetched the homepage on 29 August 2026 and ran all 86 detectors over the raw HTML — the same scan you get from the box on the front page, frozen here so the numbers can be argued with.
sokoon.xyz
Hand-written
Somebody sat down and made decisions. Several of them were opinions.
- Vibe tells
- 4
- Craft tells
- 5
- Confidence
- high
Plenty of signal to work with.
Where the score came from
- Platform fingerprints1 hit
Artefacts of the tool, not of taste
- Colour, type and surface1 hit
The visual defaults, applied unedited
- Layout and architecturenone
The shape a page takes when nobody asks what it needs to say
- Copy tells1 hit
How the words were written
- Leftoversnone
Scaffolding never cleaned up
- Source and build1 hit
What is visible in the shipped code
- How it behavesnone
Weight, mobile, accessibility, SEO — where the money leaks
- Human craft5 hits
Evidence of deliberate decisions
Evidence
9 findings- +12
Lucide icon set
30 Lucide icon references — the house icon set of every AI builder.
- +9
The typeface nobody chose
None of these are bad faces. The tell is that they arrive as the default — the page reads as though nobody made a typography decision.
- space grotesk
- −9
Deliberate social preview
Open Graph title and image were both authored.
- +8
Dependency sprawl
6 third-party asset hosts and 9 script files. Each sub-problem got whatever library was most popular in the training data, and nothing was ever consolidated.
- www.googletagmanager.com
- fonts.googleapis.com
- fonts.gstatic.com
- t.contentsquare.net
- us-assets.i.posthog.com
- cdn.jsdelivr.net
- −7
Hand-written ARIA
11 explicit accessibility attributes.
- +6
The rule-of-three cadence
7 triplet lists and 0 “not just X — it's Y” constructions. Rhythm borrowed from marketing prose, with none of the content.
What we read
- title
- sokoon — AI Mental Health Support | For the things you can't say out loud
- generator
- —
- server
- Vercel
- status
- 200
- html
- 82.8 KB
- words
- 3,522
- fetched in
- 252 ms
Reading this score
sokoon.xyz landed on 12/100, which puts it in the hand-written band. That number is not a percentage and not a probability — it is strength of evidence: 26 points of tells, damped by craft, less 32 points of deliberate decisions, mapped through one logistic curve.
What pushed it up
- Lucide icon set +12 — 30 Lucide icon references — the house icon set of every AI builder.
- The typeface nobody chose +9 — None of these are bad faces. The tell is that they arrive as the default — the page reads as though nobody made a typography decision.
- Dependency sprawl +8 — 6 third-party asset hosts and 9 script files. Each sub-problem got whatever library was most popular in the training data, and nothing was ever consolidated.
- The rule-of-three cadence +6 — 7 triplet lists and 0 “not just X — it's Y” constructions. Rhythm borrowed from marketing prose, with none of the content.
What pulled it down
- Deliberate social preview −9 — Open Graph title and image were both authored.
- Hand-written ARIA −7 — 11 explicit accessibility attributes.
- Structured data −6 — JSON-LD is present — somebody thought about search.
- Semantic landmarks −6 — 4 landmark elements instead of a pile of divs.
- Canonical URL −4 — Canonical link is set.
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.
- Skip-to-content link
- prefers-reduced-motion honoured
- Self-hosted typography
- CSS custom property system
- Hand-authored stylesheet
- No utility-class soup
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.