Repository navigation
docs: re-cut the demo so a human can actually read it - #59
Merged
Merged
Conversation
The old cut ran 15.9s and asked the viewer to read 322 characters of
terminal output in a 4.5s window. That is 72 characters per second;
comfortable technical reading is 10-15, because file paths and rule
messages are parsed character by character rather than skimmed. The only
way to follow it was to pause and step through frames.
Output lines now land 32 frames apart instead of 15, the finished screen
holds 120 frames instead of 60, and the claim cards get 95 instead of 75.
Chapter one drops from 72 to 37 characters per second, chapter two from
35 to 18.
Chapter one also showed two violations whose messages read almost
identically ("Database client imported directly in an API route handler"
and "... in a page or layout component"), spending the viewer's reading
time twice for one idea. The props builder now skips a rule whose message
repeats one already picked, so the sample is a critical and a warning of
different kinds. props-dark.json still rebuilds from the raw capture.
Runtime 15.9s -> 24.1s. The poster is now the settled check result rather
than a black card.
Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_015e3bqn8QmG1H2fgHL15RoH
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
Levironexe
added a commit
that referenced
this pull request
Oct 23, 2026
docs: re-cut the demo so a human can actually read it
This branch was successfully deployed
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
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.
The problem, measured
The old cut ran 15.9s. Measuring the reading window against the content volume:
Comfortable technical reading is 10-15 characters per second. Terminal output is parsed character by character, not skimmed like prose, because file paths and rule ids have no word shape. At 72 the only way to follow the first beat was to pause and step through frames.
What changed
Pacing only. No claim about the tool changed, and the numbers on screen are still the real output of a real run.
Chapter one also spent the viewer's time twice on one idea:
direct_db_in_routeanddirect_db_in_pageare different rules that read almost identically on screen ("Database client imported directly in an API route handler" / "... in a page or layout component"). The props builder now skips a rule whose message repeats one already picked, so the sample is one critical and one warning of genuinely different kinds.Runtime goes 15.9s to 24.1s. Longer, but legible at speed instead of needing a pause.
The poster frame is now the settled check result rather than a black title card, so the video reads as a terminal before it is played.
Verified
node scripts/verify-props.mjs captures/architectpasses, soprops-dark.jsonstill rebuilds from the raw capture and no number was hand-edited.pnpm run buildpasses. Frames inspected at the settled point of both terminal beats.🤖 Generated with Claude Code
https://claude.ai/code/session_015e3bqn8QmG1H2fgHL15RoH