Stop the skills from producing a README alongside the deck or doc - #26
Merged
Merged
Conversation
Step 6 had the agent write or extend a shared README.md next to every deck, one section per deck in the folder. That sidecar carried no citations, so it was the one artifact check.py could not keep honest, and it drifted the first time a deck was edited by a follow-up request. What it held now goes in the final message instead: coverage, slide count, navigation keys, and how the file is structured for later edits. Adding a deck to an index the repo already keeps becomes the user's call rather than a default. Markdown mode carries the same rule, so a cited doc no longer grows an uncited neighbour either. The intake no longer asks about a folder's readme conventions, Step 0 reads an existing deck for local conventions instead of its readme, and the Step 4 cleanup rule expects nothing but the deck and an optional PDF. Co-Authored-By: Claude Opus 5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01Nyxj8LM1DHDm2i2k2MYGDs
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.
What this changes, and why
Step 6 told the agent to write or extend a shared
README.mdnext to every deck, onesection per deck in the folder. That file was the only artifact of a build that carried no
citations, so it was the one thing
check.pycould not keep honest, and it went stale thefirst time a deck was edited by a follow-up request. It also gave a build two outputs to
coordinate: the intake had to negotiate the folder's readme conventions, and Step 0 read
that readme to learn local conventions instead of reading an actual deck.
A build now leaves exactly one file behind: the deck (plus a PDF if asked for).
deck covers, slide count, navigation keys, and the paragraph on how the file is
structured for later edits) is reported in the final message instead. Adding a deck to
an index the repo already keeps becomes the user's call rather than a default.
references/markdown.md) carries the same rule, so a cited doc nolonger grows an uncited neighbour either.
and build stamp), not its folder readme.
but the deck and an optional PDF.
says the deck is the only file left behind.
Nothing about the citation mechanism, the scripts, or the templates changes.
How you know it works
The whole gate is green locally:
ruff check,ruff format --check,ty check,pytest(91 passed), and
validate.py. Both citation guards still report every citation CURRENT,on uv and on bare
python3, for the HTML deck and the Markdown doc.The demo deck edit lands on a flow box, so it needed a look rather than a checker:
rendered slide 4 at 1280x720 and viewed it. The longer label wraps to two lines inside its
box with no overflow, no clipping against the nav pill, and the row keeps its shape.
smoke_test.pyitself does not run in this environment: it deliberately keeps Chrome'ssandbox, which refuses to start as root, so CI's run is the full-deck pass.
Checks that are easy to miss
skills/slideops/scripts/. Those two files are untouched.dist/skill-demo.pdfis not in the diff..claude-plugin/plugin.jsonand the skill'smetadata.versionboth go to1.1.2, with a CHANGELOG entry.scripts/make_hero.pyoutput is unaffected.🤖 Generated with Claude Code
https://claude.ai/code/session_01Nyxj8LM1DHDm2i2k2MYGDs
Generated by Claude Code