Content
96%Weight 40%Scale 1-5Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
An exceptionally dense, expert-level body: every line is non-obvious project knowledge, guidance is copy-paste executable, and workflows carry explicit validation and feedback loops (especially the film-checking checklist). The only structural note is that with no bundle files, ~300 lines are inlined where the perf/power/film deep-dives could arguably live in one-level-deep references.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | Though ~300 lines, essentially every sentence carries non-inferable, project-specific knowledge (racy index entries after a copy, GPUI's stopped clock, AppKit napping after 30s, prompt fallback renderer ignoring Enter/Escape), and it assumes Claude's competence throughout with no padding or explanation of known concepts. This fits "every token earns its place" rather than the minor-trimming of the 4 anchor. | 5 / 5 |
Actionability | Fully executable throughout: `crates/but-gpui/scripts/drive.sh run script.txt`, a complete mktemp/git-init throwaway-repo snippet, concrete script-line examples (add/wait/shot/click/key/type), `control.sh "select Branches" "pick first" "files on"`, a parameterized `film` example, and profiling commands like `sample <pid> <seconds> -file out.txt`. Copy-paste ready and covering the common cases, matching the 5 anchor. | 5 / 5 |
Workflow Clarity | Multi-step flows are clearly sequenced (throwaway repo → build state → write script → run → read shots; step-at-a-time exploration; film workflow) with explicit validation checkpoints and feedback loops: "Read the shots to check them", "always `stop` it when done", "Read every FILM line. Don't grep for chosen frames", "After each fix, check everything that mustn't change", "compare means before calling a change a regression", "Say a motion is fixed only after filming the user's own steps". This matches the 5 anchor's validate-fix-retry pattern, not merely the mostly-checkpoints of 4. | 5 / 5 |
Progressive Disclosure | No bundle files exist (no references/, scripts/, or assets/), so all ~300 lines sit inline under consistently clear, well-signaled section headers that make navigation easy. However, the specialized sections (Animations/film, Measuring performance, Measuring power) are plausible candidates for separate reference files and there is no overview pointing into them — good structure with minor organization gaps, the 4 anchor rather than the appropriately-split 5. | 4 / 5 |
Total | 19 / 20 Passed |