refactor: move PPT/share guidance into references/#98
Open
lukesw55 wants to merge 1 commit into
Open
Conversation
Keep the always-loaded SKILL.md lean (380 -> 308 lines) and load conversion and share/export detail on demand, following the skill progressive-disclosure pattern. Moved content is preserved in references/ppt-conversion.md and references/share-export.md.
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
2 participants
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.
Proposal, third item from #95. This one changes how the skill is organized, so feel free to push back on structure or naming.
SKILL.md drops from 380 to 308 lines by moving two blocks of detail into on-demand files:
references/ppt-conversion.md— the detailed PPT conversion workflow and JSON interpretation guidancereferences/share-export.md— deploy/PDF gotchas, troubleshooting and delivery messagingSKILL.md keeps the core loop for each phase plus a one-line pointer to the reference file, following the same progressive-disclosure pattern the skill already uses for STYLE_PRESETS.md and the bold template pack: the always-loaded instructions stay lean, and the agent reads the detail only in the phase that needs it.
No guidance was dropped; the moved content is verbatim-or-tightened in the reference files. Two small additions while moving:
If this lands, I have a small follow-up: a stdlib-only validation script plus CI workflow that checks internal links, frontmatter, and drift between the root skill and the plugins/ copy. I'll open it separately since it depends on this structure.
Root and plugins/ copies updated together.