emdash/fair-teeth-fold-5h9sd - #450
Conversation
The two link-dense paragraphs under the hero ("Two ways in…" / "Already
building…") became a 3-row `.start-router` table, which Paul rejected on
sight. A four-critic panel (ICP-reader, CRO, visual-design, IA) plus a
Codex refutation pass converged on the diagnosis: the block was a
navigation menu sitting in a persuasion slot.
- the hero already owns "Start Lesson 1.1"; restating it as one of three
options demoted an unconditional instruction into a conditional one
- "Ready to start" / "Prefer a map first" asked the reader to
self-classify before the page had earned anything
- three rows carried six exits, offered before the "Why this course
exists" argument, and hairline rows on a soft-card page read as a
spec sheet
- at 390px the minority "already building" row rendered taller than the
primary path
What ships instead: `.start-note`, one asymmetric callout carrying only
the route the hero does not cover (already building / paying a shop ->
the Lesson 4.2 ownership audit). 79px desktop, 130px mobile, down from
~200px - the first mistake card now lands at y~643 instead of ~760.
How This Course Works + FAQ move to the module-map intro, where the
reader is actually choosing a route; they were the page's only links to
those two pages, so relocating beat deleting. The syllabus anchor and
the side-path meta-link are dropped as duplicates.
Gates: bin/hugo-build 8/8 validators green; bin/qtest --changed green
(5 screenshots compared, no baseline drift); zero console errors at
1280x800 and 390x844.
Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
The UI-gatekeeper rule was followed to the letter on the course-landing entry block - screenshot taken, read, judged "much better than before" - and the component was still rejected on sight, later scoring 3/10 from a design critic. Two blind spots the implementer cannot self-detect: - wrong anchor: "better than the thing I just replaced" is worthless when the before was also bad - solving the symptom: a link-density complaint that was really "this element does not belong in this slot"; a prettier wrong element still fails Rule: a tweak to an existing pattern may be self-reviewed; a pattern NEW to the page needs one cold-eyes critic on the render before handback. Cheapest form is rendering 2-3 variants and letting the owner pick from screenshots - that took ~6 minutes and ended the debate. Lands as item 7 of the existing Design-quality pass (same section as the 2026-07-12 taste lesson) rather than a new doc, with the OKF concept and log synced in the same commit. Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
|
Warning Review limit reached
Next review available in: 5 minutes You've used all free OSS reviews for now. Wait for the free limit to reset to keep reviewing this public repository. How can I continue?After more reviews become available, a review can be triggered using the To avoid repeated limits, reduce automatic review volume by pausing incremental auto-reviews earlier, using label-based review opt-in, excluding WIP or generated PR titles, or requesting reviews manually when the PR is ready. If your team needs uninterrupted high-volume reviews, an organization admin can enable usage-based reviews. How do review limits work?CodeRabbit enforces per-developer PR review limits for each organization. Most developers receive the normal plan review availability. For paid Pro and Pro+ PR reviews, CodeRabbit uses adaptive limits for sustained high-volume activity. When a developer's recent PR review activity reaches the 95th percentile or higher among CodeRabbit users, additional reviews become available more gradually as earlier reviews age out of the rolling window. Please refer docs for additional details. Review details⚙️ Run configurationConfiguration used: Path: .coderabbit.yaml Review profile: CHILL Plan: Pro Plus Run ID: 📒 Files selected for processing (7)
Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out. Comment |
1 participant
No description provided.