docs(conjure): capture per visual slice, guard against redesigning around a frame - #81
Conversation
…ound a frame From the render-loop cadence experiment (20 agents, two models, three cadences, blind-graded): - Capturing after each added visual region ties on final quality with a single capture at the end, at zero to 40% more wall time depending on the model, and it is what makes the widget visibly take shape for a watching user. The skill now asks for the slice cadence when the user is watching and allows one final pass when they are not. The final pass, PNG opened and snapshot read, is never optional: the one broken widget in twenty passed every static and semantic gate. - Both models' weakest capturing run redesigned a spec item around a renderer surprise (a tick meter instead of a bar; a shrunken title). The skill now says: fix what contradicts the request or the contract, report renderer behavior that contradicts the contract as a framework reproduction, keep the requested design. - Seven of eight agents who looked at pixels raised secondary text opacity to /45 or above. The floor is now stated where the inspection happens. - The CLI is invoked as `weaver …`, on PATH after `npm run link`; the npx form only works inside the repository tree and several agents lost calls to it. Receipts: experiments/render-loop-cadence/SYNTHESIS.md and DECISIONS.md on Dara's machine. Co-Authored-By: Claude Fable 5.1 <noreply@anthropic.com>
Greptile SummaryThis change updates the Conjure widget-authoring guide to use direct CLI commands, capture coherent visual milestones, inspect final PNG and semantic evidence, preserve requested designs when renderer output conflicts with the contract, and improve dark-surface text legibility. Do not merge as written: the guide tells authors to run Confidence Score: 4/5The guide is not ready to merge because its required CLI setup command fails immediately. The broken command was reproduced from the repository root and the package manifest confirms that the referenced script is absent. Focused executions also confirmed that the capture command accepts the documented arguments and that incomplete capture artifacts cannot be published as success. A full native desktop capture was unavailable on Linux because the native runtime executable was not built, but the artifact-missing failure path was exercised through the CLI. Files Needing Attention: skills/conjure-widget/SKILL.md needs a supported command for exposing
What T-Rex did
|
| take shape on the desktop. Run the CLI as `weaver …`; it is on `PATH` after | ||
| `npm run link` in the Weaver repository. Without that link, `npx --no-install | ||
| weaver …` works only from inside the repository tree, and from anywhere else | ||
| fails with an unrelated npm message about a missing `weaver` package. Start the **Live loop** before the first source edit. |
There was a problem hiding this comment.
Documented setup command does not exist
The workflow says npm run link makes weaver available on PATH, but the root package.json has no link script. Running that documented command exits with Missing script: "link", so authors cannot complete the prescribed setup before using weaver init, dev, check, or capture. Document a supported linking command or add the missing script.
Skill changes that follow from the render-loop cadence experiment (20 agents, Opus and gpt-6-astra, three capture cadences, blind-graded). Edits
skills/conjure-widget/SKILL.mdat its path on master.Changes
weaver check, both receipts, and every semantic gate with 7/10 self-confidence./45or above. Stated at the inspection step.weaver …on PATH afternpm run link(see chore(cli): putweaveron PATH and scope the package name #82), with the caveat thatnpx --no-install weaverworks only inside the repository tree. Several agents lost calls to that npm error and read it as a widget problem.Note for Dara
Your working tree has an uncommitted move of this file to
.agents/skills/conjure-widget/SKILL.mdplus an added examples list. This PR edits the master path so it applies cleanly to master; when you commit the move, the same seven replacements apply to the new path (they are all string-exact and live inexperiments/render-loop-cadence/history if you want them as a script).🤖 Generated with Claude Code
Need help on this PR? Tag
@codesmith-botwith what you need. Autofix is disabled.