docs: sync DESIGN.md and CLAUDE.md to what actually ships - #46
Merged
Conversation
The landing redesign (#44) left both docs describing a page that no longer exists: pure white, left-aligned 720px, memo-as-hero, traffic lights on the prompt block, an accent-coloured word in the headline. That is the same drift that bit an earlier audit, where the doc was trusted and produced a confidently wrong finding about the live site. Restructured around the fact that there are now two systems, not one: - New §0 states the split up front — landing vs app chrome — with a table and the rule for telling them apart (.l* / body.landing is landing only; every unprefixed rule still reaches /verify and the viewer). - §1 keeps "document, not a marketing site" for the app chrome and explains why the landing stopped following it, including that fixing it by subtraction made it worse. Austerity is not professionalism. - §3 adds the radius scale and syntax tokens, the landing tokens, and names the only two gradients that exist and why each is load-bearing rather than decorative. - §5 documents what shipped: the landing nav, the action block, the primary CTA, the works-with strip, the evidence frame, the onboard block. §5.2 records why the memo left the landing — to:/from:/re: are RFC 5322 email headers, not HTTP, so the component built to signal protocol-seriousness was showing invented ones. - §6 carries both page anatomies, the four questions a fold must answer, the footer margin-collapse trap, and the note that headless Chrome clamps to 500px so a 360px screenshot lies. - §7 generalises "no fake mac chrome" to "no fake output of any kind", and adds the don'ts learned the hard way: no accent word in a headline, no empty imported slots, no status indicator without variance, no approximated third-party logos. - New §9 Copy. The doc had no copy section at all, which is how the fold shipped with no call to action on it. Records the voice, the word budgets measured off Vercel/Linear/Resend, and the rule that claims have to be checkable. - New §13 Known drift, with every claim verified against the code rather than remembered. Two corrections found while writing it, both by checking instead of trusting my own notes: - I first wrote that the live-pulse was retired. It is not: it still animates on /verify and the viewer via pageHead(). It only left the landing because the landing stopped using that component. §7 now says so, with a table of what actually animates where. - I first wrote that "open source" is claimed in the nav and footer. The redesign happened to remove it from both. It survives in /llms.txt, and there is still no LICENSE file, so the claim is still unbacked — just not where I said it was. CLAUDE.md's design one-liner and landing-content notes are rewritten to match, and hard rule #2 drops the stale example strings it quoted. Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
🚀 Cloudflare previewURL: https://d783268b-htmlbin.utkarsh2012.workers.dev Built from commit
|
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Docs only — no code changes, so nothing to test on the preview. Worth reading rather than skimming the diff, since the structure changed.
Why
The landing redesign (#44) left both docs describing a page that no longer exists: pure white, left-aligned 720px, memo-as-hero, traffic lights on the prompt block, an accent-coloured word in the headline.
That's the same drift that bit us before — during the slop audit I trusted DESIGN.md, concluded "the status-dot pulse is stale, no such animation exists," and shipped that wrong claim in a PR description. The doc had described a feature that hadn't landed yet.
What changed
The doc is now organised around the fact that there are two systems, not one:
.l*/body.landingis landing-only; every unprefixed rule still reaches/verifyand the viewer.Two corrections I caught by checking instead of trusting my notes
1. I first wrote that the live-pulse was retired. It isn't. It still animates on
/verifyand the viewer viapageHead()— it only left the landing because the landing stopped using that component. §7 now carries a table of what actually animates where, and flags this as something that should go.2. I first wrote that "open source" is claimed in the nav and footer. The redesign happened to remove it from both. It survives in
/llms.txt(discoverability.ts:156), and there's still no LICENSE file, so the claim is still unbacked — just not where I'd said it was, twice.§13 verified findings
live-pulsestill running on/verify+ viewer.hero,.prompt*,.term-*,.copy-cta, …)/llms.txt, no LICENSE anywhereSHOWCASE_SLUGhardcoded with no fallbackI checked each of the 14 CSS classes individually — no view emits any of them.
The rule I added at the end
🤖 Generated with Claude Code