Repository navigation
Conversation
…at runs one CLAUDE.md rule 8 says a render gate with no browser prints SKIPPED and exits 0, and that the agent must set DS_REQUIRE_BROWSER=1 to trust a single gate. On a plugin install the kit's CLAUDE.md is not in the user's context, so the skill is the only instruction the agent reads before it runs the gate. design-screen carries the rule; nine other skills name render gates and did not. - The same three-line note after the Step 0 block in a11y-audit, critique, data-dashboard, design-code, design-component, design-qa, gate, image-to-code and ship. - A guard test: every SKILL.md that names a browser gate must mention DS_REQUIRE_BROWSER. It lists all nine skills on main and passes with the fix. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Owner
|
Thanks for this. The problem is real, and the next release fixes it in a different place: instead of a note in each skill, |
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.
CLAUDE.md rule 8 (from #16) says a render gate with no browser prints SKIPPED and exits 0, and that the agent must set
DS_REQUIRE_BROWSER=1to trust a single gate. On a plugin install the kit's CLAUDE.md is not in the user's context, so the skill is the only instruction the agent reads before it runs the gate.design-screencarries the rule; nine other skills name render gates and did not.Found while vendoring
a11y-auditinto a project on its own: the skill told the agent to runmeasure_render.mjsandverify_states.mjs, and nothing in what it read said a SKIPPED exit 0 is not a pass.Change
a11y-audit,critique,data-dashboard,design-code,design-component,design-qa,gate,image-to-codeandship. No script default changes.tests/meta/guards.test.mjs: every SKILL.md that names a browser gate (the sameBROWSER_GATESlist the file already derives) must mentionDS_REQUIRE_BROWSER.Output
On
main(skills unchanged, test added):With the fix,
node --test tests/meta/guards.test.mjsunderPYTHONUTF8=1:PYTHONUTF8=1is needed only because two existing guards fail on a Korean-locale Windows machine; that is a separate fix, sent as its own PR.scripts/check_no_emoji.pypasses. I did not runaccuracy_report.mjs: this machine has no Playwright browser, and the change touches no gate.🤖 Generated with Claude Code