메뉴
Deck Master compatibility entry for the full PPT Master backend used by deck-builder. Use only to inspect or hand back production render results through Deck Master.
Codex 또는 Claude로 설치 이 Prompt를 복사해 Codex, Claude 또는 다른 어시스턴트에 붙여 넣으면 Skill 페이지를 검토하고 설치를 진행할 수 있습니다.
SOC 직업 분류 기준
Deck Master workflow autopilot for advancing a run across init, brief, planning, sourcing, production, build, quality, review, and delivery checkpoints.
Deck Master learning entry for delivery outcomes, reusable asset feedback, benchmark results, and workspace learning packs.
Professional Solution Deck Run OS for turning customer context, briefs, historical deck assets, sourcing decisions, product capability handbacks, quality gates, Review Desk state, benchmark runs, and delivery feedback into auditable solution deck workflows. Use when Codex needs to create or resume a Deck Master run, generate a preview from a brief, inspect next steps, run deck quality gates, import narrative advice or review findings, manage PPT Library, PPT Master, PPT Deck Pro Max, or PPT Quality Gate handbacks, export approved page queues, validate benchmark cases, or operate the local Deck Master CLI and Review Desk.
Deck Master sourcing entry for deciding which pages need historical assets, new production, evidence screenshots, or project-specific reference material.
Deck Master build entry for producing delivery-oriented HTML, PDF, PNG, PPTX, artifact manifest, render result, and editability metadata through the PPT Master backend.
Deck Master project workspace initialization entry for creating customer material, reference material, AI process, delivery, quality, and .deck-master metadata directories.
| name | ppt-master |
| description | Deck Master compatibility entry for the full PPT Master backend used by deck-builder. Use only to inspect or hand back production render results through Deck Master. |
| triggers | ["render deck preview","build html render artifact","import render result","check render status","ppt master"] |
PPT Master is the full production backend used by deck-builder. This
compatibility entry is kept for existing prompts and local installs.
Use deck-builder as the public Deck Master build entry. In an active Deck
Master run, every backend output must return through Deck Master import or state
update paths.
needs_builder_backend, needs_build, or needs_render.deck_render_result.v2 handback that must be imported.deck-* skill.render --fixture-safe is available.~/.deck-master/bin/deck-master setup-status --include-suite --output json
~/.deck-master/bin/deck-master run-state --run-dir <run_dir> --run-id <run_id>
~/.deck-master/bin/deck-master suite-status --target codex --output json
~/.deck-master/bin/deck-master build status --run-dir <run_dir> --run-id <run_id>
~/.deck-master/bin/deck-master render-status --run-dir <run_dir> --run-id <run_id>
~/.deck-master/bin/deck-master import-render-result --run-dir <run_dir> --run-id <run_id> --input <render_result.json>
Fixture/dev-only contract smoke:
~/.deck-master/bin/deck-master render --run-dir <run_dir> --run-id <run_id> --format html --fixture-safe
The canonical render result is render_results/render_result.json with
schema_version: deck_render_result.v2. Legacy render result paths are accepted
only as import inputs and must be normalized into the canonical path.
Production/client export requires a certified backend result. Contract-smoke or
fixture-safe outputs are internal verification materials and must stay marked
non_client_deliverable.
Maps to public stage: deck-builder. This is a compatibility wrapper; prefer the public deck-builder skill for new runs.