- README.md: what this is, how to run and build it, the folder map, how light and dark mode work (@hanzo/appearance, @hanzo/design), where every price and checkout link lives, scripts, and known differences from live - docs/build-notes/: status files, request notes, per-page checklists and reviews, plans - Removed: screenshot galleries, captures of third-party sites used as references, the generated status page and its script, editor config, a personal working-rules file - Code comments point at the new docs paths (no code changes) Co-Authored-By: Claude Opus 5.5 <[email protected]> Claude-Session: https://claude.ai/code/session_01P5YBdwj33XByFVTvu9bfci
8.4 KiB
/cli — James-eye review
Verdict: 7/10 Ready: 8 Nov, held up next to /api and /affiliate (James's new bar, no score). The round-4 fixes held (hero session only grows, tree tour never reflows, one caret steps down the band, rail cards fit); this pass gives the hero a breathing status light and the slider handle a breathing ring until taken (0 still screens at either width), cuts the 200–350px white bands between slider, paste line, rail and get started, and makes the two ledes and claim titles plain text so every live line reads word for word. copycheck missing 0 of 50; taste/unique OK (parity 82/82, links 10/10); 0 console errors (also reduced motion), no overflow at 1470 and 375 (the hero's tab bar scrolls inside its own window). Usable: the install line with Copy, Install from hanzo.sh, GitHub, docs and the console are all on the first screen. First complaint: "It shows me the whole answer, then wipes it and types it again. That looks like it glitched, not like it's alive."
Walked at build e88d5f71, dev server http://localhost:4180/cli/. Playwright Chromium with video at 1470×801 and at 375×812 (isMobile, hasTouch, DPR 2). I watched the first 3 s with no input, then scrolled with the wheel (touch scroll on phone) 200 px at a time with dwells. I hovered and pressed every control on desktop and tapped them on phone: the hero Copy, Pause/Replay, tree folders and leaves, the rail arrows, the add-to-script toggles, Copy script, and the hero tab links. I also ran reduced motion, JS off, console capture, a PerformanceObserver for layout shift with per-source attribution, small-target, hue and above-heading scans, the neighbours' first screens (/api, /desktop, /playground, /sdks, /mcp), parity.py /cli and taste.py on CliPage.jsx, CliPage.css and cli/Cut.jsx. Frames are in docs/build-notes/review/cli/desktop-walk.jpg, phone-walk.jpg and desktop-first-2s.jpg (video frames at 5 fps over the first 2.4 s).
What works
- The hero is the product. The first screen is a black terminal room: the h1 cuts in by line mask (seen mid-cut at about 0.8 s), then
hanzoand "deploy the gateway to staging" type and the session streams to "✓ gateway is on staging", ending on a blinking caret. It sells in 5 seconds, and nothing on the neighbouring pages looks like it (/api is a white request card, /sdks a code panel, /mcp a tool list, /desktop an app frame). - One solid, used properly. The white "Install from hanzo.sh" is the hero's only fill, with GitHub and the console as text links. Below it, the Copy copies exactly
curl -fsSL https://hanzo.sh | sh(checked on the clipboard) and the label flips to "Copied". On desktop the header ask now becomes the solid "Install from hanzo.sh" once the hero leaves view, and it goes quiet while the closing band's solid is on screen, so only one fill is on screen at a time. - Real interactive objects lower down. The resource tree (role tree, a gliding selection, the print pane typing
$ hanzo auth login). The three claims as small terminal windows, withhanzo apistruck through. The script builder: pressing "+" adds a block with a clip wipe, the line count goes from 16 to 22, and Copy script returns the assembled script. - Clean measurements. Parity text 82/82 and links 10/10; taste OK on all 3 files. 0 console errors at both sizes and under reduced motion. 0 hue. 0 labels above any h1 or h2. 0 targets under 44px at 375. No horizontal scroll. Under reduced motion, 0 animations are running after 3.5 s and the final frame shows. With JS off, all 28 headings and paragraphs are visible.
The 11 answers
- 5 s / 1 s. Yes, it sells, and the h1 cut-in moves within 1 s. But the server-rendered final session is fully readable from about 0.8 s to 1.6 s. Then rows 1 and 2 blank, then all rows blank, then it types from
$. The visitor reads the answer and watches it vanish (seedesktop-first-2s.jpg; the same happens on phone). That is the first thing he would notice. - One in, one out? Mostly. Each screen holds one idea: hero, agent prompt, tree, claims, rail, script, Get CLI, band. But past the hero the page turns into a white document. The motion is small clip wipes and carets, and the end runs long: about 300 px of empty white between Get CLI and the band, and about 170 px after the band's rows before the footer.
- A real object in every section? Yes. Every section has a terminal, tree, window, rail card or script. The rail cards are tall grey tiles whose bottom 40% is empty at 1470, which reads unfinished.
- One ask, nothing floating, scale rhythm? Yes on the ask. Only the shared cookie card floats. Scale works: the hero h1 is 52 px against a 32 px session, section h2s are 26 px, the tree statement is 32 px and the band is 44 px. It is never all big at once.
- Hover and press? Every control answers: tree nodes fill and their count pill inverts, the rail arrows border and disable at the ends, the add toggles fill to a black tick, the "related" arrows slide 6 px, and the claim windows lift 2 px. No layout jump on hover. The hovers are colour and fill changes; few of them tell you something new.
- Overlap, font swap, shift? No overlap at either size and no font swap. Layout shift: on phone the tree's self-running tour collapses
authand openssharewith no input. The rows jump 88 px inside the window, and CLS is 0.036 (attributed toLI.cli-resandBUTTON.cli-node, reproduced twice). That is over the 0.02 lab target. Desktop is 0.008. - Reference? apple.com product page (the product as hero, one idea per screen) and a bit of motion.dev's typed patterns. The apple-style pinned or scrubbed scene is absent. The reference shows up in the hero only.
- Different from neighbours? Yes. It is the only first screen in the group that is a full black terminal room.
- 18 parts? The card has all 18 headings and
Done here:lines, but two claims are false or stale (see Card check). - Banned tells? None outright. Two smaller rule breaks. First, the tree window is both outlined and given a large floating shadow ("raise or outline, never both"). Second, the closing band has four identical blinking
$ hanzo █carets in one viewport, and up to 7 carets blink at once on the page, against MASTER's "at most one continuous mover per viewport". The four repeats also read as filler. - Copy untouched? Yes, parity is 82/82 and 10/10.
Card check
- Format: 18
## N.headings withDone here:lines, plus the 3 header lines. OK. - Part 11, "phone film layout shift 0.000". False: measured 0.036 on phone from the tree tour, with no input. This caps the verdict at 7.
- Part 4, "The header carries the shared solid 'Try Hanzo' (it cannot be relabelled from a page)". Stale: on desktop the header now swaps to the solid "Install from hanzo.sh" after the hero. On phone it still says "Try Hanzo".
- Part 11, "0 targets under 44px". True (0 at 375×812).
- Part 7 / 3, "0 labels directly above any h1/h2". True.
- Part 17, "console errors: none at both sizes and reduced motion". True.
Fixes (in order)
- Kill the flash in the hero. On the first run, do not render the SSR final frame and then clear it. Under
html.js, start the rows already empty (or masked) from first paint, and keep the final frame only for JS off and reduced motion. The session should only ever grow, never reset in front of the visitor. - Stop the phone tree tour from reflowing. Either do not auto-collapse the previous folder while the tour runs (only open the next one), or keep the tree at fixed row slots so opening and closing never moves rows. Re-measure CLS to under 0.02 on phone, and correct part 11 and the stale part 4 line on the card.
- Fix the ending. Keep one caret in the band's four "$ hanzo" rows (on the row in focus, or one that steps down the list), so at most one mover is in the viewport. Close the dead white above the band (about 300 px) and after it (about 170 px) so proof, Band and footer run on with no gap.
- Tighten the rail. Size the capability cards to their content (or put the command window at the bottom) so the bottom 40% is not empty grey.
- Raise or outline. Drop either the tree window's 1 px outline or its big shadow.
- Give the white half of the page one authored moment. It needs more than wipes and carets, for example the script builder's lines counting up, or a pinned tree scene where one panel changes as you scroll. Otherwise everything after the hero reads as a quiet document.