Skip to content

docs(conjure): capture per visual slice, guard against redesigning around a frame - #81

Merged
SunkenInTime merged 1 commit into
masterfrom
docs/conjure-render-cadence
Sep 6, 2026
Merged

SunkenInTime merged 1 commit into
masterfrom
docs/conjure-render-cadence

Conversation

@SunkenInTime

@SunkenInTime SunkenInTime commented Sep 6, 2026 •

Copy link
Copy Markdown
Collaborator

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.md at its path on master.

Changes

  1. Render loop cadence. Was "after each edit that can change pixels". Now: after the first coherent slice, after each added visual region, and after any edit that changes semantics or interaction; one pass after the last edit is enough when the user is not watching the desktop. Rationale: progressive capture tied on final quality with final-only in both models (17.25 vs 17.6 of 18, inside noise) and cost zero to 40% more wall time, while producing 7 to 11 rendered saves per widget instead of 4. That is the visible build the Live loop wants, produced honestly.
  2. The final pass is never optional, PNG opened and snapshot read. The one broken widget in twenty (letters drawn under counts) passed weaver check, both receipts, and every semantic gate with 7/10 self-confidence.
  3. Guard against redesigning around a frame. Both models' lowest-scoring capturing run saw something mid-build and changed the spec item to match: a tick meter instead of a bar, a shrunken title to match date metrics. The skill now says fix what contradicts the request or the contract, and report renderer behavior that contradicts the contract as a framework reproduction while keeping the requested design.
  4. Legibility floor. Seven of eight agents who looked raised secondary text to /45 or above. Stated at the inspection step.
  5. Invocation. weaver … on PATH after npm run link (see chore(cli): put weaver on PATH and scope the package name #82), with the caveat that npx --no-install weaver works 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.md plus 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 in experiments/render-loop-cadence/ history if you want them as a script).

🤖 Generated with Claude Code


View with [code]smith Autofix with [code]smith
Need help on this PR? Tag @codesmith-bot with what you need. Autofix is disabled.

…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-apps

greptile-apps Bot commented Sep 6, 2026 •

Copy link
Copy Markdown

Greptile Summary

This 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 npm run link, but that command is not defined in the repository and exits before the direct weaver workflow can begin. The documented capture command was verified to parse and route correctly, and capture was verified to reject incomplete output rather than reporting success without both required artifacts.

Confidence Score: 4/5

The 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 weaver on PATH. package.json is the manifest that currently lacks the documented script.

T-Rex T-Rex Logs

What T-Rex did

  • T-Rex generated proof for two posted P1 findings and linked them to their corresponding review comments.
  • T-Rex built and ran the documented weaver capture path at both the parent and current revisions, and verified the commands reached the CaptureRuntimeNotBuilt response.
  • T-Rex exercised the capture path that intentionally omitted required output artifacts, and the CLI produced an error with no PNG, snapshot, or receipt published; publication rollback tests passed.
  • T-Rex examined the weaver-link workflow logs and CLI behavior, including the before/after logs and the direct CLI path on Linux, to validate documented expectations and script declarations.
  • T-Rex ran clock capture tests before and after, plus a negative control, to show the parser fails gracefully and that the environment lacks the native runtime needed for rendering.

View all artifacts

T-Rex Ran code and verified through T-Rex

Comments Outside Diff (1)

  1. General comment

    P1 SKILL.md documents a nonexistent npm run link command

    • Bug
      • skills/conjure-widget/SKILL.md:9-12 tells users that npm run link in the Weaver repository puts weaver on PATH. From the repository root, npm run link returns npm error Missing script: "link" and exits 1. The root manifest's scripts block (package.json:13-20) contains no link entry. This prevents users from completing the documented global/direct weaver … setup step.
    • Cause
      • The documentation refers to a root npm script that is absent from the root package manifest.
    • Fix
      • Either add a root link script that performs the intended CLI linking, or replace the documented command with the repository-supported linking/install command and verify it makes weaver available on PATH.

    T-Rex Ran code and verified through T-Rex

Reviews (1): Last reviewed commit: "docs(conjure): capture per visual slice,..." | Re-trigger Greptile

Comment on lines +9 to +12
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.

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

P1 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.

T-Rex Ran code and verified through T-Rex

@SunkenInTime
SunkenInTime merged commit 4251e72 into master Sep 6, 2026
9 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant