agentleFS
humanist96humanist96/deck-design-pack/AGENTS.md

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.

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
  1. Distinctive:

    After routing, the selected skill or workflow owns execution and gates.

    line 6
  2. Distinctive:

    Before reading any full presentation skill or workflow, read the routing dispatcher and select the route.

    line 18
  3. Very specific:

    When the user asks for a presentation ("PPT 만들어줘", "make slides", "生成PPT", a deck from a document/topic/template):

    line 29
  4. Very specific:

    Route before full-load: Read .claude/skills/ppt-master/workflows/routing.md first.

    line 32
  5. Distinctive:

    Return to routing when intent changes: Do not keep executing the old owner after the request changes route family.

    line 50
  6. Distinctive:

    Only when routing selected the main SVG family (or a workflow explicitly handed off to its shared SVG steps), execute the main skill …

    line 55
  7. Very specific:

    Keep phases serial. Do not batch pages, generate page SVGs by script, delegate SVG authoring, hand-build the PPTX outside svg_to_pptx.py, …

    line 59
  8. Very specific:

    After project init, run main preflight.py (--needs-images when applicable) and stop on failure.

    line 62
  9. Very specific:

    Never replace finalize with a copy or use -s final for release.

    line 76

≈ “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.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
AGENTS.md

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 — 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 script. preflight.py hard-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. If python3 is missing (common on Windows), rerun the same command with python.

PPT requests — MANDATORY procedure

When the user asks for a presentation ("PPT 만들어줘", "make slides", "生成PPT", a deck from a document/topic/template):

  1. Route before full-load. Read .claude/skills/ppt-master/workflows/routing.md first. Use its one discriminator question only for the ambiguity it defines; do not load competing full owners before the answer.
  2. Load the selected owner(s) in full. The router owns the complete matrix; this table is a compact Codex handoff summary:

    Selected familyFull runtime owner(s)
    Main SVG generation / PPTX re-architectureMain ppt-master/SKILL.md
    Strict 1:1 SVG beautifybeautify-pptx.md, then main SKILL.md only at its explicit shared-SVG handoff
    Raw PPTX template fillppt-template-fill/SKILL.md only
    Finished-PPTX native enhancementnative-enhance-pptx/SKILL.md, then its required execution workflow
    Another standalone routeThe selected workflow; load the next owner only at an explicit handoff
  3. 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.
  4. 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. Use failure-recovery.md on tool failure.
  • After project init, run main preflight.py (--needs-images when 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.py on design_spec.md plus spec_lock.md and fix every error before SVG generation. Re-read spec_lock.md at 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 codex AI path uses Codex built-in image_gen; legacy host-native reads as auto. On acquisition failure, retry once, mark Needs-Manual, report, and continue without substitution.
  • Post-process in separate ordered calls: total_md_split.py only when notes were requested, finalize_svg.py only when a self-contained SVG preview is requested or a workflow explicitly needs svg_final/, then svg_to_pptx.py. Never replace finalize with a copy or use -s final for release. Require verify_deck.py <project> exit 0 before declaring completion, then Read the _pptx_render/<stem>-grid.png contact sheet it renders as a single sanity scan. --no-render is allowed only while re-exporting during iteration; the final pre-hand-off run must render. That lightweight scan is not verify-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.

Download now (ZIP)

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
What did you use it for? e.g. Reviewing pull requests in a Rails app

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.