deck-design-pack
AGENTS.md0 starsChanged 2 months agoMITView on GitHub
This repo is dual-host: Claude Code and Codex. CLAUDE.md owns standing repository conventions. Route selection belongs to .claude/skills/ppt-master/workflows/routing.md. After routing, the selected skill or workflow owns execution and gates. The rules below add Codex-side enforcement; they never override the selected owner. - .claude/skills/ is canonical (ppt-master, ppt-template-fill, native-enhance-pptx, diagram-design, codex-image). .codex/skills/ holds generated discovery stubs — same name/description frontmatter plus a redirect body — regenerated by python3 .claude/skills/ppt-master/scripts/sync_codex_stubs.py. - Never hand-edit .codex/skills/. Edit the .claude tree, then re-run the sync…
Where files are headingNew AGENTS.md files have more rules about keeping secrets out of the code, and fewer about code style.
Of the AGENTS.md files we read, the 31,700 first seen in the last six months, against the older ones: the kind of rule that gained most share, and the kind that lost most. About files like this in general, not this one, and an estimate, since a kind is a pattern in the words.
In this repository6 other files it gives its agents.
- CLAUDE.mdCLAUDE.md
- codex-imageSkill
- diagram-designSkill
- native-enhance-pptxSkill
- ppt-masterSkill
- ppt-template-fillSkill
The file
We split this AGENTS.md into the rules it gives an agent
9 rules. About 0 are common, 4 are distinctive, and 5 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈4
Distinctive · estimate
This author's own choices. Worth a look.
5
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 6
After routing, the selected skill or workflow owns execution and gates.
- Distinctive: line 18
Before reading any full presentation skill or workflow, read the routing dispatcher and select the route.
- Very specific: line 29
When the user asks for a presentation ("PPT 만들어줘", "make slides", "生成PPT", a deck from a document/topic/template):
- Very specific: line 32
Route before full-load: Read .claude/skills/ppt-master/workflows/routing.md first.
- Distinctive: line 50
Return to routing when intent changes: Do not keep executing the old owner after the request changes route family.
- Distinctive: line 55
Only when routing selected the main SVG family (or a workflow explicitly handed off to its shared SVG steps), execute the main skill …
- Very specific: line 59
Keep phases serial. Do not batch pages, generate page SVGs by script, delegate SVG authoring, hand-build the PPTX outside svg_to_pptx.py, …
- Very specific: line 62
After project init, run main preflight.py (--needs-images when applicable) and stop on failure.
- Very specific: line 76
Never replace finalize with a copy or use -s final for release.
≈ “Common” is an estimate: at least 1 in 5 of the 40,246 AGENTS.md files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
AGENTS.md — Codex execution rules for slide-master
This repo is dual-host: Claude Code and Codex. CLAUDE.md owns
standing repository conventions. Route selection belongs to
.claude/skills/ppt-master/workflows/routing.md.
After routing, the selected skill or workflow owns execution and gates. The rules
below add Codex-side enforcement; they never override the selected owner.
Skill source (generated pointer stubs)
.claude/skills/is canonical (ppt-master,ppt-template-fill,native-enhance-pptx,diagram-design,codex-image)..codex/skills/holds generated discovery stubs — samename/descriptionfrontmatter plus a redirect body — regenerated bypython3 .claude/skills/ppt-master/scripts/sync_codex_stubs.py.- Never hand-edit
.codex/skills/. Edit the.claudetree, then re-run the sync script.preflight.pyhard-fails when stubs are stale. - Before reading any full presentation skill or workflow, read the routing dispatcher and select the route. Then read only the selected canonical owner(s) in full. A broad presentation discovery signal does not authorize preloading the main SVG skill for a direct-PPTX route.
- Path resolution:
${SKILL_DIR}and bare relative paths (references/...,workflows/...,scripts/...,templates/...) resolve against the canonical skill directory. Run all commands from the repository root. Ifpython3is missing (common on Windows), rerun the same command withpython.
PPT requests — MANDATORY procedure
When the user asks for a presentation ("PPT 만들어줘", "make slides", "生成PPT", a deck from a document/topic/template):
- Route before full-load. Read
.claude/skills/ppt-master/workflows/routing.mdfirst. Use its one discriminator question only for the ambiguity it defines; do not load competing full owners before the answer. Load the selected owner(s) in full. The router owns the complete matrix; this table is a compact Codex handoff summary:
Selected family Full runtime owner(s) Main SVG generation / PPTX re-architecture Main ppt-master/SKILL.mdStrict 1:1 SVG beautify beautify-pptx.md, then mainSKILL.mdonly at its explicit shared-SVG handoffRaw PPTX template fill ppt-template-fill/SKILL.mdonlyFinished-PPTX native enhancement native-enhance-pptx/SKILL.md, then its required execution workflowAnother standalone route The selected workflow; load the next owner only at an explicit handoff - Apply only owner-defined gates. Confirmations, preflight, validation, recovery, export, and completion checks come from the selected owner. Sharing scripts does not import main SVG gates into a direct-PPTX route.
- Return to routing when intent changes. Do not keep executing the old owner after the request changes route family.
Main SVG discipline
Only when routing selected the main SVG family (or a workflow explicitly handed off to its shared SVG steps), execute the main skill exactly as written. The following Codex enforcement remains mandatory for that route only:
- Keep phases serial. Do not batch pages, generate page SVGs by script, delegate
SVG authoring, hand-build the PPTX outside
svg_to_pptx.py, or substitute placeholder/solid-color images. Usefailure-recovery.mdon tool failure. - After project init, run main
preflight.py(--needs-imageswhen applicable) and stop on failure. Every blocking confirmation is a hard stop; use the Confirm UI and only its documented staged-chat fallback. - Immediately run
validate_spec.pyondesign_spec.mdplusspec_lock.mdand fix every error before SVG generation. Re-readspec_lock.mdat P01/P05/P09 and after context compaction. Run the page-1 SVG quality gate before page 2 and the full quality gate after the last page; fix every error. - Honor the confirmed image source and exact §VIII targets. The default
codexAI path uses Codex built-inimage_gen; legacyhost-nativereads asauto. On acquisition failure, retry once, markNeeds-Manual, report, and continue without substitution. - Post-process in separate ordered calls:
total_md_split.pyonly when notes were requested,finalize_svg.pyonly when a self-contained SVG preview is requested or a workflow explicitly needssvg_final/, thensvg_to_pptx.py. Never replace finalize with a copy or use-s finalfor release. Requireverify_deck.py <project>exit 0 before declaring completion, then Read the_pptx_render/<stem>-grid.pngcontact sheet it renders as a single sanity scan.--no-renderis allowed only while re-exporting during iteration; the final pre-hand-off run must render. That lightweight scan is notverify-pptx-export: on a suspected issue, report it and recommend the workflow, but never enter it without explicit user approval.
Direct-PPTX routes use only their own native validation loops and preserve their
source fonts. Pretendard applies to SVG-authoring routes. docs/rules/ style
rules, Markdown language consistency, and the workflow-package boundary remain
standing repository conventions from CLAUDE.md.
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

