← ClaudeAtlas

vawe-critiquelisted

Review and fix a video made from an HTML page. Look at a rendered page film and say what is wrong, as a fresh session that did not write it: the phone, strip and loop views, bin/vawe critique, page-check, the default-reject judge that names shot, frame and fix, the top five, and re-rendering only the affected seconds. Load after any draft render, before any fix.
vawe-hq/skills · ★ 0 · Code & Development · score 75
Install: claude install-skill vawe-hq/skills
# vawe-critique: how to look When you talk to the person, use plain words: describe what the viewer sees, not the harness terms (map: harness/lib/plain-words.mjs). Run this skill inside a vawe checkout: `AGENTS.md`, `taste/` and `bin/vawe` live there. With no checkout, get one: `git clone https://github.com/vawe-hq/vawe.git && cd vawe && npm install && bin/vawe-dev doctor`. The author never grades its own film. Run this in a session that has not seen the authoring, or let `bin/vawe critique <page> --fresh` start one (a headless critic with the prompt below; it writes `out/<film>.critique-<n>.md`). Default verdict is REJECT; the film passes only when you cannot find a reason to reject it. Grade what is on screen, not what the film meant. ## The views, in this order ```bash bin/vawe critique films/<name>/page.html [--ref quality/refs/<ref>/source.mp4] ``` It writes the sheet, the strip, the phone view and the loop pair, and runs the page checks. Then look, and write one line per finding under each view: 1. **Sheet**: every frame. Is the focal point obvious in under a second? Is anything cramped, overlapping or unreadable? Producing a sheet is not looking at one: one line per frame. 2. **Strip**: both sides of every cut. Does the cut land on its beat? Does the eye know where to go after it? Does any exit run slower than its entrance? 3. **Phone**: the 9:16 render, or 16:9 at one third size. Can you read every string? Is the accent still one colour? 4. **Loop or en