CLAUDE.md

This file is the project entry point for Claude Code. The ppt-master skill lives at .claude/skills/ppt-master/ and is auto-discovered by Claude Code.

Cross-harness (dual-host): AGENTS.md is the Codex-side execution-rules layer — it references this file as SSOT and only adds enforcement, so content edits here do not need mirroring there. .codex/skills/ holds generated Codex discovery stubs: after editing any .claude/skills/<name>/SKILL.md frontmatter, run python3 .claude/skills/ppt-master/scripts/sync_codex_stubs.py (never hand-edit stubs; preflight.py fails while they are stale). Skill content itself lives only in .claude/skills/.

Route before full-load (mandatory): for a presentation request, first read .claude/skills/ppt-master/workflows/routing.md. Select the route there, then read only the selected execution owner(s) in full. Do not preload the main SVG skill for a direct-PPTX route. For a repository edit, read the owner of the contract being changed; the main skill is authoritative only for the main SVG family and the shared SVG steps that explicitly invoke it.

Project Overview

PPT Master is a presentation workflow package with SVG-authoring and direct-PPTX route families. The main SVG family uses Strategist → Image_Generator → Executor to convert source documents into editable DrawingML. Direct-PPTX routes preserve an existing PowerPoint package and use their own execution gates.

Main SVG Pipeline: Source Document → Create Project → [Template] → Strategist confirmation stage → [Image_Generator] → Executor Live Preview → Quality Check → Post-processing → Export PPTX

Route selection authority: .claude/skills/ppt-master/workflows/routing.md owns the complete matrix and wins over every summary below.

An ambiguous PPTX optimization request stays in the router until its one discriminator question resolves whether the deck is 1:1 beautify or re-architectable source. Do not load either full owner before that answer.

Execution Ownership

• The selected skill or workflow owns its confirmations, preflight, validation, recovery, export, and completion gates. This root file adds none.
• Shared scripts do not transfer gate ownership between SVG and direct-PPTX families.
• Topic research, template creation, and post-route workflows load the next owner only when their own procedure declares a handoff.

Font Policy (install-local, standing preference)

• Every SVG-authored deck uses Pretendard as the fixed font family — do not propose or pick other families unless the user explicitly asks in the current conversation. Hierarchy comes from weight/size, not family switching. Direct-PPTX routes preserve source fonts unless their selected owner says otherwise. Full contract: strategist.md §g install-local font lock.
• Stack: Pretendard, "Malgun Gothic", sans-serif; intermediate weights use installed family names ("Pretendard Medium", "Pretendard SemiBold", etc.).
• Font files are bundled at .claude/skills/ppt-master/assets/fonts/Pretendard/ (SIL OFL) and installed user-level on this machine. PPTX does not embed fonts — decks shared to other machines need Pretendard installed there.

Required Conventions

• Repo-wide style rules — when editing prompt files under .claude/skills/ppt-master/references/, Python under .claude/skills/ppt-master/scripts/, or any other code/prose in the repo, follow the matching style rule in docs/rules/.
• Markdown language consistency — Markdown files under .claude/skills/ppt-master/workflows/, .claude/skills/ppt-master/references/, and docs/ are currently single-language per directory. New files mirror the language of their siblings; do not mix English scaffolding with Chinese paragraphs (or vice versa) inside one file. Chat replies are unaffected.

Compatibility Boundary

• This repository is a workflow/skill package, not an app or service scaffold.
• Do NOT assume generic-project conventions like .worktrees/, tests/, or mandatory branch setup unless the user explicitly requests them.
• On conflict with a generic coding skill, prioritize the selected repo-local execution owner. The main ppt-master/SKILL.md has that role only when routing selected the main SVG family or an explicit shared-SVG handoff.

Execution Pointers

Commands and defaults belong to the selected owner; use these pointers instead of treating a root-level command list as a gate checklist.

Core Directories

• .claude/skills/ppt-master/SKILL.md — main SVG workflow authority.
• .claude/skills/ppt-template-fill/SKILL.md — raw-template direct-PPTX authority.
• .claude/skills/native-enhance-pptx/SKILL.md — finished-PPTX enhancement entry owner.
• .claude/skills/ppt-master/references/ — role definitions and technical specifications.
• .claude/skills/ppt-master/scripts/ — runnable tool scripts.
• .claude/skills/ppt-master/scripts/docs/ — topic-focused script docs.
• .claude/skills/ppt-master/templates/ — layout templates, chart templates, icon library, brand presets.
• .claude/skills/ppt-master/workflows/ — standalone workflow files.
• docs/ — user-facing documentation (FAQ, installation, technical design, templates guide, audio narration).
• docs/rules/ — repo-wide style rules.
• projects/ — user project workspace.

This repository: deck-design-pack

This is humanist96/deck-design-pack — the ppt-master workflow above, vendored from byungjunjang/slide-master (MIT, © 2025-2026 Hugo He; see THIRD_PARTY_NOTICES.md), with seven additional deck templates already installed and registered.

• Seven pack templates live alongside the bundled ones in .claude/skills/ppt-master/templates/decks/: midnight-panel, polarity, gradient-mesh, warm-doc, open-road, signal-green, koscom-chevron. Each is a 10-page roster — 1 Master + 9 Layouts, the two chart pages sharing chart_linear. Matching identity-only presets sit in templates/brands/.
• The templates are the source of truth in place. There is no separate decks/ or brands/ directory at the repository root; editing a template means editing it under .claude/skills/ppt-master/templates/.
• After changing a template's design_spec.md frontmatter, re-run python3 install.py <some-other-workspace> --dry-run only if you are exporting; the in-repo index entries are maintained by hand or by re-running the installer against a scratch workspace. Never re-register these ids with register_template.py — it drops the defaults anchor block the Confirm UI reads.
• install.py exports this pack into a different ppt-master workspace. It refuses to target this repository.
• Authoring rules for the pack's own 10-page spine: docs/authoring.md. Per-template detail: docs/gallery.md.