mdpr-skill
Purpose
Use this skill as the optional Codex companion for MDPR. MDPR remains the deterministic presentation runtime; this skill provides semantic hints, review findings, and rule/config improvement guidance around MDPR outputs and intermediate representations.
Core Boundary
- When the local CLI is available, start by reading branch-local guidance with
node bin/mdpr-skill.js docs bootstrap --dense and then the narrow topic
for the task, such as docs boundaries --dense, docs template-fill --dense,
docs media --dense, docs preflight --dense, or docs review --dense. This mirrors the
agent-ready CLI-docs pattern used by Astryx while keeping MDPR-specific
runtime ownership intact.
- Let MDPR own parsing, slide splitting, recipes, layout, coordinates, geometry, typography, colors, z-order, arrows, effects, exact icon assets, renderer object IDs, and final PPTX objects.
- Keep agent output weak, semantic, evidence-based, and schema-valid.
- Express fixes as Markdown cleanup, MDPR rulebook changes, config changes, deterministic policy changes, or approval-bound proposals.
- Preserve the ability to build the same deck with all agent hints disabled.
- Do not mutate source Markdown unless the user explicitly asks for a cleaned source draft.
- Treat media policy as a hard handoff boundary:
imageUse: "no-image" means no
generated-image candidates, and iconUse: "no-new-icons" means no icon
keyword candidates. If conflicting candidates appear, emit preflight warnings
and rely on MDPR runtime diagnostics as the authoritative accept/ignore
result.
- Treat all runtime-owned fields as forbidden in hints and review artifacts:
coordinates, geometry, crop/cropRect, raw colors, typography, z-order,
exact icons, final image paths, renderer objects, recipe/variant/layout IDs,
and copied PowerPoint object IDs.
MDPR Runtime Sync Boundary
Use the local MDPR checkout as the source of truth when this skill is being
updated for a revised MDPR runtime.
- Treat MDPR schemas as mirrored contracts, not skill-owned inventions. Before
claiming compatibility with a revised MDPR checkout, run the schema-sync gate
against the target MDPR path.
- Record the MDPR checkout path, commit hash or version, schema-sync command,
and validation timestamp in review notes or artifacts before claiming
compatibility with a revised MDPR runtime. Do not treat
.cache/mdpr or any
specific commit as a permanent assumption.
- Treat MDPR's
validation.polish manifest field as the deterministic
post-AI PPT polish gate. LLM notes may explain or triage polish concerns, but
MDPR owns the pass/fail result for font hierarchy, layout composition,
highlight pages, cover treatment, detail QA, and theme-gallery evidence.
- Treat MDPR's
job-state validate/status and generated-assets validate
commands as runtime mirror checks for the same contracts that mdpr-skill
can create or inspect.
- Keep
mdpr-skill changes compatible with MDPR's no-agent runtime: all
generated hints, edit intents, change requests, and review artifacts must be
optional inputs or review evidence.
Useful local commands:
git -C <mdpr-path> rev-parse HEAD
node bin/mdpr-skill.js gate validate-schema-sync --mdpr-path <mdpr-path>
node <mdpr-path>/packages/cli/dist/index.js job-state validate <job-state.json> --json
node <mdpr-path>/packages/cli/dist/index.js generated-assets validate <generated-assets.json> --json
Substitute the actual MDPR checkout and artifact paths, and verify referenced
files exist before treating results as compatibility evidence.
LLM-Assisted PPTX Review Boundary
Use LLM judgment only for semantic, narrative, evidence, and review-note
assistance. It must not override MDPR validation or replace deterministic
overflow, text clipping, overline, coherence, spacing, type, radius, shadow,
raw-hex, editability, or renderer gates.
When an LLM review mentions these issues, ground the note in an MDPR report
finding, rendered evidence path, manifest field, or explicit source excerpt.
Treat the LLM note as triage or explanation only; MDPR validation remains the
source of truth for pass/fail status and release gating.
When reviewing revised-MDPR outputs, explicitly check whether the build manifest
records validation.polish. Missing, stale, and failing status must come from
MDPR build/validate output, MDPR manifest metadata, or MDPR-reported source
hash/build metadata, not from LLM judgment. If validation.polish is missing,
stale, or failing according to those MDPR-owned signals, recommend an MDPR
runtime or validation-policy fix rather than presenting the LLM review as a
release gate substitute.
The review command mirrors a positive
validation.polish.requiredFailureCount as an error finding with type
MDPR_POLISH_GATE_FAILED, the failed required chapter names, and
runtimeOwner: MDPR. Do not emit that finding when the required failure count
is zero.
Example MDPR-owned check after the runtime has built or validated a deck:
node <mdpr-path>/packages/cli/dist/index.js validate <deck.md> --visual --coherence --json
Main Workflows
Semantic Hints
Use when a deck, Slide Element IR, Presentation IR, or ambiguous Markdown would benefit from compact semantic guidance.
- Suggest intent, grouping, importance, evidence-bound icon-search keywords as
structured icon keyword candidates, key-message priority, content split,
readability, template-use, and media-policy semantics.
- When a user provides or references an existing PPTX/POTX/theme and does not
explicitly ask for a new visual system, default to
template-fill: preserve
master slides, placeholders, and the existing theme frame. Do not add new
cards, surfaces, icons, images, or style systems in this mode.
- In
template-fill, treat the supplied PPTX/POTX slide master as the primary
visual system. Do not pass --theme-style, --theme-color,
--theme-harmony, --theme-gallery, --design, theme packs, or
source-neutral DESIGN imports unless the user explicitly asks to transform the
visual system. For the current mdpresent CLI, the safe default is
mdpresent build deck.md --to pptx --out dist --template master.pptx plus
validation; adding MDPR theme flags is a duplicate-theme risk.
- In
template-fill, do not synthesize slide-bottom "key message", "caution",
"takeaway", or similar callout bands unless the source deck or template has
an explicit placeholder for them. Keep safety notes as normal body content,
presenter notes, or review notes instead of adding a new visual layer.
- In
template-fill, do not override template typography or text colors. Avoid
explicit font-family, font-color, raw RGB/hex, decorative fills, or custom
line colors in agent-created PowerPoint bridge output; use the existing
placeholder defaults, slide master, and PowerPoint theme bindings.
- If
template-fill or explicit media policy sets imageUse: "no-image" or
iconUse: "no-new-icons", remove conflicting generated-image or icon keyword
candidates before handoff; keep only a preflight warning if the conflict is
useful review evidence.
- Suggest generated-image candidates only when the source contains image
evidence or the user explicitly requests a generated asset. A large or
ambiguous icon is not enough by itself. Positive permission requires
generated-asset workflow intent,
imageSearch: "explicit-request-only", and
request/instruction evidence bound to the candidate.
- Default image search to disabled. Use source-image-only guidance when source
images exist, and explicit-request-only guidance when the user asks for image
generation or search.
- Default icon use to no-new-icons in template-fill workflows. Icon keyword
candidates are allowed only as semantic search terms when the workflow permits
icons, and each candidate must carry element/source evidence rather than an
exact icon name, file path, placement, or style.
- For dense or wordy content, prefer semantic
contentSplitCandidates and
readabilityCandidates before visual decoration.
- In review and comparison evidence, do not synthesize a one-line subtitle that
repeats the title, an automatic title underline, an isolated bottom rule, or
a takeaway band unless the source or template assigns it a real content role.
Keep structural card borders and data separators only when they clarify an
actual group or comparison.
- Judge lines by semantic role and repetition, not by presence alone. Do not
flag a card border or data separator that carries grouping meaning. Flag a
continuous rail that duplicates per-item accents, an unassigned title/bottom
rule, or deck-wide separator repetition only with rendered before/after evidence
showing that removal improves hierarchy without losing grouping.
- Revalidate the rendered PPTX visually instead of inferring quality from the
source or manifest alone. Inspect every exported slide for clipping, sparse
continuation pages, repeated numbering, misleading decoration, and stale or
partial export frames; record remaining weaknesses instead of styling them
away in the evidence deck.
- For sparse continuation pages, distinguish wrong topology from disproportionate
region height. Verify the current rendered topology first; when a short
source-backed row already exists, recommend content-measured runtime sizing
rather than another layout, extra copy, or decoration. MDPR owns the sizing
rule, while mdpr-skill records before/after evidence and source preservation.
- Preserve heading and list ancestry in comparison corpora and review evidence.
Promote content to paired columns or a native table only when two source
groups are explicit siblings under comparison-bearing ancestry such as
current/improved or before/after. A flat peer list is not enough evidence for
A/B accents. Keep a negative control so hierarchy detection cannot turn two
unrelated sections into a semantic comparison.
- Verify the semantic block and selected preset before writing a sparse-page
regression. Pipeline diagram nodes are not list items: when their rendered
cards are oversized, test the
diagram block and pipeline region, preserve
node/edge mappings, and re-export PowerPoint. Reject a passing unit fixture if
the current rendered slide does not change; that is a validator false positive.
- Treat
16pt as the current MDPR generated-text visual floor, including list
and diagram number badges. Apply it to text-bearing regions, including code,
captions, tables, charts, and diagrams; image-only and empty decorative
regions do not emit glyphs and must not create a font-floor finding. Verify
the runtime manifest and actual PPTX runs; do not assume code or caption needs
a smaller exception, and do not prescribe an exact replacement size from the
skill side.
- When MDPR exposes
validation.fontEnvironment, distinguish a proven missing
family from FONT_ENVIRONMENT_UNAVAILABLE, and cite the recorded probe source.
A passing host catalog check is evidence for that export host only. When
embedding.performed is false, do not claim portability. When it is true,
require MDPR-owned EOT part paths, source hashes, fsType, and complete
family/style coverage before describing the PPTX as portable. Treat the font
EULA as an external responsibility even when fsType permits embedding.
When MDPR exposes embedding.licenseEvidence, distinguish exact post-render
SHA-256 binding from legal sufficiency: require complete: true before
describing a distribution workflow as evidence-complete, and preserve
legalDetermination: external. Do not create license evidence, do not
reinterpret its license terms, select font files, embed them from the skill,
or duplicate
MDPR's --require-font-installed, --require-font-embedded,
--font-license-evidence, or --require-font-license-evidence pass/fail
decisions.
- For Korean decks and mixed Korean/English decks, prevent awkward wrapping as
source cleanup: shorten claim titles, replace long inline tool names with a
shorter label plus detail in notes, split long bullets into label/detail
pairs, and move secondary evidence to speaker notes or a follow-up slide. Do
not prescribe exact manual line breaks, font sizes, or coordinates; MDPR owns
final typography and wrapping.
- Treat paragraph marker handling as MDPR-owned runtime behavior. Current MDPR
normalizes dash and bullet-like lines such as
-item, •, ·, –, —,
−, ㆍ, and ▪ into stable list structure while preserving --- slide
breaks, pipeline arrows, negative-number prose, year-leading prose such as
2026. Roadmap, fenced code, indented code, and raw <pre> blocks. Real
ordered lists keep source numbering through MDPR splitting. mdpr-skill may
suggest source cleanup or readability notes around these markers, and may
consume MDPR source-cleanup diagnostics when available, but must not encode
marker-specific layout or rendering decisions.
- Keep hints compatible with
agent-hint.json-style weak semantic input.
- Validate that hints do not encode final rendering choices.
- Prefer minimal hints over broad restatement of the source.
- Run a preflight mindset inspired by reference skills such as
taste-skill:
one primary key message per slide by default, no broad restatement of every
source block, no contradictory template-fill media/icon candidates, and no
decorative hints that MDPR can already derive deterministically. For recursive
Pro/RDD loops, reject duplicate or vague TODO proposals before import unless
they name concrete files, acceptance checks, validation, and new evidence.
- Ground primary key-message candidates with
evidenceRefs or claimRef when
available. Treat ungrounded primary emphasis as a preflight warning, not as a
final slide design instruction.
- Require explicit user/request/approval evidence before using
style-transform. Existing PPTX/POTX/theme workflows stay template-fill
unless the user asks to change the visual system.
Useful local commands when the repo CLI is available:
node bin/mdpr-skill.js hint --source-sha256 <64hex> --out .mdpresent/proposals/agent-hint.json
node bin/mdpr-skill.js hint --selection-context .mdpresent/ppt/selection-context.json --markdown deck.md --out .mdpresent/proposals/agent-hint.json
Review Reports
Use when reviewing generated MDPR artifacts, manifests, preview images, review reports, or handoff artifacts.
- Report visual concerns with evidence paths.
- Flag template-fill risks such as master-theme evidence missing, placeholder
preservation evidence missing, slide-scoped placeholder mismatches,
rasterized template-fill output, images without source/request, generated
assets whose provenance is not bound to the asset or slide, undeclared image
search, new icon substitution, dense content, overly long copy, duplicate
theme application from MDPR theme flags, and awkward Korean/English wrapping
visible in rendered previews.
- Distinguish source Markdown problems from MDPR runtime/rulebook problems.
- Turn repeated visual issues into deterministic MDPR rule or config recommendations.
- Keep the output actionable for MDPR maintainers.
- Reference MDPR manifest
validation.polish when discussing post-AI PPT polish
quality, and keep that manifest field as the release gate.
Useful local command:
node bin/mdpr-skill.js review --manifest dist/mdpresent-manifest.json --out .mdpresent/review/review-report.json
Narrative Spine Review
Use when source Markdown needs content-level review before MDPR renders or
rebuilds a deck.
- Read Markdown, optional MDPR manifest summaries, and optional source notes.
- Emit claim-title and section-flow suggestions only.
- Include provenance such as source path, manifest slide count, heading text,
or source-note excerpt.
- Do not emit layout IDs, placeholder IDs, coordinates, colors, typography,
renderer object IDs, or pass/fail validation decisions.
Useful local command:
node bin/mdpr-skill.js narrative --markdown deck.md --manifest dist/mdpresent-manifest.json --source-notes notes.md --out .mdpresent/review/narrative-review.json
Template Layout Intent Review
Use when a PPTX template has been summarized as a layout catalog and the deck
needs semantic layout-intent hints before MDPR chooses any actual layout.
- Read layout names and placeholder roles from a layout catalog or template
summary.
- Emit semantic intents such as comparison, chart-focus, evidence, or
section-divider.
- Treat existing PowerPoint master slides as the theme source when the workflow
is
template-fill. Ask for preservation evidence; do not transform the
master, copy exact placeholder IDs, or choose final layouts.
- Include provenance through the catalog path, layout label, and placeholder
roles.
- Do not emit placeholder coordinates, placeholder IDs, layout IDs, layout
selection decisions, colors, typography, or renderer object IDs.
Useful local command:
node bin/mdpr-skill.js layout-intent --layout-catalog template-layout-catalog.json --out .mdpresent/review/layout-intent.json
LLM-Assisted Content Review Helpers
Use when the source needs semantic or editorial review before MDPR renders, or
when MDPR-rendered evidence needs a human-readable review artifact.
speaker-notes: draft presenter notes and reviewer comments from Markdown
and optional source notes.
citations: flag missing citations, stale sources, and unsupported claims
from source metadata.
rendered-preview: consume MDPR-generated PNG/contact-sheet paths and emit
visual concern notes only. Validate these artifacts with
validateRenderedPreviewCritiqueBoundary when available; the notes may cite
slide labels, rendered image paths, contact sheets, and MDPR finding IDs, but
must not prescribe exact coordinates, fonts, colors, icons, image paths,
crops, copied master/layout IDs, z-order, or renderer object IDs.
accessibility: draft alt text, plain-language, acronym expansion, and
audience-fit suggestions.
evidence-ledger: map slide claims to source metadata and MDPR evidence IDs.
- For readability and Korean decks, recommend shorter claim titles, fewer
bullets, and moving detail to notes as content suggestions only. Do not pick
font sizes or exact line breaks.
- Prefer MDPR-provided source-cleanup diagnostics over re-deriving parser
heuristics. Use raw Markdown marker heuristics only as a conservative fallback
when no MDPR cleanup diagnostics were supplied.
These helpers may cite source paths, headings, rendered image paths, MDPR
finding IDs, source IDs, and evidence IDs. They must not emit coordinates,
colors, typography, z-order, geometry, renderer object IDs, or pass/fail
validation decisions.
For source-neutral style references, prefer DESIGN.md frontmatter
sourceNeutral: true with semantic tone, density, layout intent, decoration,
and image-policy sections only. Do not include literal hex colors, exact fonts,
copied PowerPoint master/layout IDs, exact icons, image paths, crops, or
renderer object IDs; MDPR owns final theme binding and template preservation.
Useful local commands:
node bin/mdpr-skill.js speaker-notes --markdown deck.md --source-notes notes.md --out .mdpresent/review/speaker-notes.json
node bin/mdpr-skill.js citations --markdown deck.md --sources sources.json --as-of 2026-06-27 --out .mdpresent/review/citation-review.json
node bin/mdpr-skill.js rendered-preview --images rendered-images.json --out .mdpresent/review/rendered-preview-review.json
node bin/mdpr-skill.js accessibility --markdown deck.md --audience "executive review" --out .mdpresent/review/accessibility-review.json
node bin/mdpr-skill.js evidence-ledger --markdown deck.md --sources sources.json --mdpr-evidence mdpr-evidence.json --out .mdpresent/review/evidence-ledger.json
Change Requests And Override Proposals
Use when an agent or PowerPoint bridge flow needs to record a proposed change
without applying it directly to MDPR runtime output.
- Emit
mdpr-change-request-v1 proposals for agent hints, edit intents, policy
suggestions, pack candidates, or user-override candidates.
- Keep change requests in
proposed state until the user explicitly approves
or rejects them.
- Require approval metadata before any pack or override candidate is treated as
a runtime input.
- Use
edit override-candidate only for bounded split preferences such as
splitBy, forceSingleSlide, or maxDensity. It must not encode
coordinates, colors, recipes, variants, or final layout decisions.
- Prefer
ppt propose --markdown when a PowerPoint selection context is tied
to Markdown; this rejects stale source hashes before creating hints or change
requests.
Useful local commands:
node bin/mdpr-skill.js edit override-candidate --source-sha256 <64hex> --slide-ref slide-3 --instruction "split dense evidence into smaller slides" --split-by h3 --out .mdpresent/proposals/split.override.json
node bin/mdpr-skill.js ppt propose --selection-context .mdpresent/ppt/selection-context.json --markdown deck.md --out .mdpresent/proposals/ppt-selection.change-request.json --hints-out .mdpresent/proposals/ppt-selection.agent-hint.json
node bin/mdpr-skill.js change approve .mdpresent/proposals/ppt-selection.change-request.json --approved-by <user-or-reviewer-id> --approved-at <ISO-8601> --out .mdpresent/proposals/ppt-selection.approved.change-request.json
node bin/mdpr-skill.js change reject .mdpresent/proposals/ppt-selection.change-request.json --out .mdpresent/proposals/ppt-selection.rejected.change-request.json
Production Override And PDF Boundary
Use when a revised MDPR runtime supports production override application or PDF
output paths.
mdpr-skill may propose user-approved override candidates and review
resulting artifacts.
- MDPR owns applying production overrides, PDF output, renderer behavior,
validation, and pass/fail decisions.
- Do not encode final layout, coordinates, colors, recipes, variants, renderer
object IDs, or PDF rendering decisions in skill output.
Generator Comparison Boundary
PptxGenJS, python-pptx, and other PPTX generators are comparison points only.
Use them to describe capability vocabulary or benchmark context; do not add
them as dependencies, fallback renderers, or alternate runtimes. MDPR remains
the deterministic runtime.
Codex PPT Compatibility Mapping
Use when a user asks to support or match codex-ppt-skill capabilities in
MDPR or mdpr-skill.
- Treat
codex-ppt as an image-based workflow reference, not as an alternate
MDPR renderer.
- Map each feature to an MDPR-native rail: runtime, proposal, review,
orchestration, bridge, or generated visual asset rail.
- Keep
coverage.unmappedFeatureCount at 0 before claiming implementation
coverage.
- Preserve the output-model distinction:
codex-ppt produces full-slide image
PPTX; MDPR defaults to editable PPTX/HTML/PDF.
- Use the compatibility map to create MDPR runtime TODOs for missing surfaces
such as theme-pack registries, generated-asset provider metadata, slide task
packets, and job-state tracking.
- Use
codex-ppt slide-tasks when a user needs codex-ppt-style per-slide jobs
around an MDPR build. These packets are for single-slide review or repair
proposals and must remain free of geometry, renderer object ids, exact colors,
z-order, and final layout decisions.
- Use
codex-ppt job-state after task packet export when a workflow needs
long-running slide review/repair state. recorded and accepted updates
require artifact/report evidence, and blocked updates require a blocker
reason; never treat chat text alone as completion evidence.
- Use
codex-ppt generated-assets validate for generated visual asset provider
and quality metadata. The manifest records provider id, model, prompt hash,
source input hashes, size, quality, background, transparency policy, and
output provenance without secrets and without becoming a full-slide renderer.
- Cross-check MDPR's mirrored validators for
mdpr-job-state-v1 and
mdpr-generated-assets-v1 when the revised MDPR runtime is available.
- Do not copy codex-ppt's full-slide image generation as a default MDPR path.
Useful local command:
node bin/mdpr-skill.js codex-ppt compat --source-ref ningzimu/codex-ppt-skill@93c1e013965a3b42f272252030b2e1a5abede710 --out artifacts/codex-ppt-compat/codex-ppt-compat.json
node bin/mdpr-skill.js codex-ppt slide-tasks --manifest artifacts/external-markdown-visual-eval/iteration-05/build/mdpresent-manifest.json --markdown artifacts/external-markdown-visual-eval/iteration-05/corpus.md --rendered-images artifacts/codex-ppt-slide-tasks/iteration-05/rendered-images.json --out artifacts/codex-ppt-slide-tasks/iteration-05/tasks
node bin/mdpr-skill.js codex-ppt job-state init --tasks artifacts/codex-ppt-slide-tasks/iteration-05/tasks/slide-task-packets.json --manifest artifacts/external-markdown-visual-eval/iteration-05/build/mdpresent-manifest.json --out artifacts/codex-ppt-slide-tasks/iteration-05/mdpr-job-state.json
node bin/mdpr-skill.js codex-ppt generated-assets validate --manifest artifacts/codex-ppt-generated-assets/sample.generated-assets.json
node <mdpr-path>/packages/cli/dist/index.js job-state status <job-state.json> --json
node <mdpr-path>/packages/cli/dist/index.js generated-assets validate <generated-assets.json> --json
Design Components Boundary
Use when working with MDPR's built-in design component runtime or related IR.
- Read Slide Element IR or Presentation IR as the content contract.
- Suggest only semantic hints around intent, grouping, importance, and icon keywords.
- For icon requests that are too large or semantically ambiguous, suggest a
generated-image candidate only when source image evidence exists or the user
explicitly approves generated assets; otherwise keep the finding as semantic
review guidance.
- Explain design review findings in terms of MDPR rulebook/config changes.
- Do not choose recipes, variants, coordinates, shape sizes, typography, colors, z-order, arrows, effects, or exact icon assets.
- Do not duplicate MDPR renderer behavior in the skill.
Reusable Theme And Style Pack Proposals
Use when a user wants more theme variety, a reusable visual style, a new deck
theme, or a style inspired by another PPT/PDF/image while preserving MDPR as
the final renderer.
- Treat the source as a visual system, not as slide content to copy.
- Extract reusable tokens, semantic layout blueprints, decoration grammar,
best-fit scenarios, and MDPR registration targets.
- For theme-specific usage, include proposal-only
visualLanguage,
imagePolicy, and styleSystem.decorationRules guidance when available:
design dials may describe variance, motion, and density, but they must stay
bounded selection evidence rather than renderer instructions.
- Emit an approval-bound
mdpr-theme-candidate-v1, not agent-hint.json.
- Use
registration.targets to distinguish mdpr-theme-pack, mdpr-profile,
mdpr-rulebook, and deck-local-style-pack follow-up work.
- Keep generated image and reference-board guidance under
imagePolicy.generatedAssetBoundary = "semantic-reference-only". Use it to
describe when images support a theme, how imagery should be treated, and when
generated imagery is forbidden, not to request exact image assets or
full-slide image rendering.
- Write decoration guidance as update rules such as downshifting dense slides,
preferring rule lines over decorative blobs, or using image frames only when
a source image exists.
- Keep
constraints.mdprOwnsFinalLayout,
constraints.mdprOwnsFinalThemeBinding, constraints.noRawUseInAgentHints,
and constraints.requiresDesignLockUpdate set to true.
- Do not include source-private content, exact slide copy, copied layouts,
final coordinates, exact colors in hints, renderer object IDs, or exact
icon/assets choices.
- If a candidate should become built-in, route it through MDPR approval/import
gates before saying it is available as an MDPR runtime theme.
Useful local command:
node bin/mdpr-skill.js design import references/custom.DESIGN.md --out .mdpresent/proposals/custom.theme-candidate.json
Design Coherence Audit
Use when auditing Design Components Styled Deck IR before rendering or release.
Check for:
- raw hex in PPT theme mode
- mixed radius family
- mixed shadow family
- mixed spacing scale
- mixed type scale
- excessive accent use
- excessive decorative effects
- dense slides using expressive effects
- repeated layout rhythm
- non-editable PPTX primary text plans
Return JSON-style findings when the caller needs CI output, or a concise human-readable fix list when working interactively. Findings may explain why an issue exists, but fixes must stay at the MDPR rulebook/config or deterministic policy level.
PowerPoint Bridge Boundary
When working with mdpr-ppt or PowerPoint selection context:
hint rail: emit weak agent-hint.json semantics only.
review rail: emit review-report.json findings only.
edit-intent rail: record page or decoration change requests as safe proposals.
approved override / pack rail: require user approval before MDPR validates and applies override or pack candidates.
- Prefer
--markdown deck.md with selection-context commands so stale source
hashes are rejected before hints or proposals are handed to MDPR.
Never emit final PowerPoint geometry, object IDs, z-order, exact colors, or exact icon assets from a selection context.
Validation
Prefer the repo's existing commands when the mdpr-skill checkout is available:
node bin/mdpr-skill.js gate validate-schema-sync --mdpr-path <mdpr-path>
npm run validate
npm run check:mdpr
npm run check:mdpr-pandoc
For focused artifact work, validate the exact JSON schema or report contract
touched by the task before presenting findings as release-ready. For revised
MDPR compatibility work, include the schema-sync gate and any mirrored MDPR
validator that corresponds to the artifact under review.
1---2name: mdpr-skill3description: Use when Codex should help with MDPR presentation workflows, including semantic agent hints, icon-keyword ideas, Markdown cleanup, visual review notes, Design Components boundary checks, and Styled Deck IR design coherence audits. Triggers include MDPR, mdpresent, Markdown-to-PPTX, PPTX review, agent-hint.json, review-report.json, design component hints, raw hex/theme violations, spacing/type/radius/shadow consistency, and MDPR rulebook or config fixes.4metadata:5 source: https://skillmd.com/skills/ch040602/mdpr-skill6---78# mdpr-skill910## Purpose1112Use this skill as the optional Codex companion for MDPR. MDPR remains the deterministic presentation runtime; this skill provides semantic hints, review findings, and rule/config improvement guidance around MDPR outputs and intermediate representations.1314## Core Boundary1516- When the local CLI is available, start by reading branch-local guidance with17 `node bin/mdpr-skill.js docs bootstrap --dense` and then the narrow topic18 for the task, such as `docs boundaries --dense`, `docs template-fill --dense`,19 `docs media --dense`, `docs preflight --dense`, or `docs review --dense`. This mirrors the20 agent-ready CLI-docs pattern used by Astryx while keeping MDPR-specific21 runtime ownership intact.22- Let MDPR own parsing, slide splitting, recipes, layout, coordinates, geometry, typography, colors, z-order, arrows, effects, exact icon assets, renderer object IDs, and final PPTX objects.23- Keep agent output weak, semantic, evidence-based, and schema-valid.24- Express fixes as Markdown cleanup, MDPR rulebook changes, config changes, deterministic policy changes, or approval-bound proposals.25- Preserve the ability to build the same deck with all agent hints disabled.26- Do not mutate source Markdown unless the user explicitly asks for a cleaned source draft.27- Treat media policy as a hard handoff boundary: `imageUse: "no-image"` means no28 generated-image candidates, and `iconUse: "no-new-icons"` means no icon29 keyword candidates. If conflicting candidates appear, emit preflight warnings30 and rely on MDPR runtime diagnostics as the authoritative accept/ignore31 result.32- Treat all runtime-owned fields as forbidden in hints and review artifacts:33 coordinates, geometry, crop/cropRect, raw colors, typography, z-order,34 exact icons, final image paths, renderer objects, recipe/variant/layout IDs,35 and copied PowerPoint object IDs.3637## MDPR Runtime Sync Boundary3839Use the local MDPR checkout as the source of truth when this skill is being40updated for a revised MDPR runtime.4142- Treat MDPR schemas as mirrored contracts, not skill-owned inventions. Before43 claiming compatibility with a revised MDPR checkout, run the schema-sync gate44 against the target MDPR path.45- Record the MDPR checkout path, commit hash or version, schema-sync command,46 and validation timestamp in review notes or artifacts before claiming47 compatibility with a revised MDPR runtime. Do not treat `.cache/mdpr` or any48 specific commit as a permanent assumption.49- Treat MDPR's `validation.polish` manifest field as the deterministic50 post-AI PPT polish gate. LLM notes may explain or triage polish concerns, but51 MDPR owns the pass/fail result for font hierarchy, layout composition,52 highlight pages, cover treatment, detail QA, and theme-gallery evidence.53- Treat MDPR's `job-state validate/status` and `generated-assets validate`54 commands as runtime mirror checks for the same contracts that `mdpr-skill`55 can create or inspect.56- Keep `mdpr-skill` changes compatible with MDPR's no-agent runtime: all57 generated hints, edit intents, change requests, and review artifacts must be58 optional inputs or review evidence.5960Useful local commands:6162```bash63git -C <mdpr-path> rev-parse HEAD64node bin/mdpr-skill.js gate validate-schema-sync --mdpr-path <mdpr-path>65node <mdpr-path>/packages/cli/dist/index.js job-state validate <job-state.json> --json66node <mdpr-path>/packages/cli/dist/index.js generated-assets validate <generated-assets.json> --json67```6869Substitute the actual MDPR checkout and artifact paths, and verify referenced70files exist before treating results as compatibility evidence.7172## LLM-Assisted PPTX Review Boundary7374Use LLM judgment only for semantic, narrative, evidence, and review-note75assistance. It must not override MDPR validation or replace deterministic76overflow, text clipping, overline, coherence, spacing, type, radius, shadow,77raw-hex, editability, or renderer gates.7879When an LLM review mentions these issues, ground the note in an MDPR report80finding, rendered evidence path, manifest field, or explicit source excerpt.81Treat the LLM note as triage or explanation only; MDPR validation remains the82source of truth for pass/fail status and release gating.8384When reviewing revised-MDPR outputs, explicitly check whether the build manifest85records `validation.polish`. Missing, stale, and failing status must come from86MDPR build/validate output, MDPR manifest metadata, or MDPR-reported source87hash/build metadata, not from LLM judgment. If `validation.polish` is missing,88stale, or failing according to those MDPR-owned signals, recommend an MDPR89runtime or validation-policy fix rather than presenting the LLM review as a90release gate substitute.9192The `review` command mirrors a positive93`validation.polish.requiredFailureCount` as an error finding with type94`MDPR_POLISH_GATE_FAILED`, the failed required chapter names, and95`runtimeOwner: MDPR`. Do not emit that finding when the required failure count96is zero.9798Example MDPR-owned check after the runtime has built or validated a deck:99100```bash101node <mdpr-path>/packages/cli/dist/index.js validate <deck.md> --visual --coherence --json102```103104## Main Workflows105106### Semantic Hints107108Use when a deck, Slide Element IR, Presentation IR, or ambiguous Markdown would benefit from compact semantic guidance.109110- Suggest intent, grouping, importance, evidence-bound icon-search keywords as111 structured icon keyword candidates, key-message priority, content split,112 readability, template-use, and media-policy semantics.113- When a user provides or references an existing PPTX/POTX/theme and does not114 explicitly ask for a new visual system, default to `template-fill`: preserve115 master slides, placeholders, and the existing theme frame. Do not add new116 cards, surfaces, icons, images, or style systems in this mode.117- In `template-fill`, treat the supplied PPTX/POTX slide master as the primary118 visual system. Do not pass `--theme-style`, `--theme-color`,119 `--theme-harmony`, `--theme-gallery`, `--design`, theme packs, or120 source-neutral DESIGN imports unless the user explicitly asks to transform the121 visual system. For the current `mdpresent` CLI, the safe default is122 `mdpresent build deck.md --to pptx --out dist --template master.pptx` plus123 validation; adding MDPR theme flags is a duplicate-theme risk.124- In `template-fill`, do not synthesize slide-bottom "key message", "caution",125 "takeaway", or similar callout bands unless the source deck or template has126 an explicit placeholder for them. Keep safety notes as normal body content,127 presenter notes, or review notes instead of adding a new visual layer.128- In `template-fill`, do not override template typography or text colors. Avoid129 explicit font-family, font-color, raw RGB/hex, decorative fills, or custom130 line colors in agent-created PowerPoint bridge output; use the existing131 placeholder defaults, slide master, and PowerPoint theme bindings.132- If `template-fill` or explicit media policy sets `imageUse: "no-image"` or133 `iconUse: "no-new-icons"`, remove conflicting generated-image or icon keyword134 candidates before handoff; keep only a preflight warning if the conflict is135 useful review evidence.136- Suggest generated-image candidates only when the source contains image137 evidence or the user explicitly requests a generated asset. A large or138 ambiguous icon is not enough by itself. Positive permission requires139 generated-asset workflow intent, `imageSearch: "explicit-request-only"`, and140 request/instruction evidence bound to the candidate.141- Default image search to disabled. Use source-image-only guidance when source142 images exist, and explicit-request-only guidance when the user asks for image143 generation or search.144- Default icon use to no-new-icons in template-fill workflows. Icon keyword145 candidates are allowed only as semantic search terms when the workflow permits146 icons, and each candidate must carry element/source evidence rather than an147 exact icon name, file path, placement, or style.148- For dense or wordy content, prefer semantic `contentSplitCandidates` and149 `readabilityCandidates` before visual decoration.150- In review and comparison evidence, do not synthesize a one-line subtitle that151 repeats the title, an automatic title underline, an isolated bottom rule, or152 a takeaway band unless the source or template assigns it a real content role.153 Keep structural card borders and data separators only when they clarify an154 actual group or comparison.155- Judge lines by semantic role and repetition, not by presence alone. Do not156 flag a card border or data separator that carries grouping meaning. Flag a157 continuous rail that duplicates per-item accents, an unassigned title/bottom158 rule, or deck-wide separator repetition only with rendered before/after evidence159 showing that removal improves hierarchy without losing grouping.160- Revalidate the rendered PPTX visually instead of inferring quality from the161 source or manifest alone. Inspect every exported slide for clipping, sparse162 continuation pages, repeated numbering, misleading decoration, and stale or163 partial export frames; record remaining weaknesses instead of styling them164 away in the evidence deck.165- For sparse continuation pages, distinguish wrong topology from disproportionate166 region height. Verify the current rendered topology first; when a short167 source-backed row already exists, recommend content-measured runtime sizing168 rather than another layout, extra copy, or decoration. MDPR owns the sizing169 rule, while mdpr-skill records before/after evidence and source preservation.170- Preserve heading and list ancestry in comparison corpora and review evidence.171 Promote content to paired columns or a native table only when two source172 groups are explicit siblings under comparison-bearing ancestry such as173 current/improved or before/after. A flat peer list is not enough evidence for174 A/B accents. Keep a negative control so hierarchy detection cannot turn two175 unrelated sections into a semantic comparison.176- Verify the semantic block and selected preset before writing a sparse-page177 regression. Pipeline diagram nodes are not list items: when their rendered178 cards are oversized, test the `diagram` block and `pipeline` region, preserve179 node/edge mappings, and re-export PowerPoint. Reject a passing unit fixture if180 the current rendered slide does not change; that is a validator false positive.181- Treat `16pt` as the current MDPR generated-text visual floor, including list182 and diagram number badges. Apply it to text-bearing regions, including code,183 captions, tables, charts, and diagrams; image-only and empty decorative184 regions do not emit glyphs and must not create a font-floor finding. Verify185 the runtime manifest and actual PPTX runs; do not assume code or caption needs186 a smaller exception, and do not prescribe an exact replacement size from the187 skill side.188- When MDPR exposes `validation.fontEnvironment`, distinguish a proven missing189 family from `FONT_ENVIRONMENT_UNAVAILABLE`, and cite the recorded probe source.190 A passing host catalog check is evidence for that export host only. When191 `embedding.performed` is false, do not claim portability. When it is true,192 require MDPR-owned EOT part paths, source hashes, `fsType`, and complete193 family/style coverage before describing the PPTX as portable. Treat the font194 EULA as an external responsibility even when `fsType` permits embedding.195 When MDPR exposes `embedding.licenseEvidence`, distinguish exact post-render196 SHA-256 binding from legal sufficiency: require `complete: true` before197 describing a distribution workflow as evidence-complete, and preserve198 `legalDetermination: external`. Do not create license evidence, do not199 reinterpret its license terms, select font files, embed them from the skill,200 or duplicate201 MDPR's `--require-font-installed`, `--require-font-embedded`,202 `--font-license-evidence`, or `--require-font-license-evidence` pass/fail203 decisions.204- For Korean decks and mixed Korean/English decks, prevent awkward wrapping as205 source cleanup: shorten claim titles, replace long inline tool names with a206 shorter label plus detail in notes, split long bullets into label/detail207 pairs, and move secondary evidence to speaker notes or a follow-up slide. Do208 not prescribe exact manual line breaks, font sizes, or coordinates; MDPR owns209 final typography and wrapping.210- Treat paragraph marker handling as MDPR-owned runtime behavior. Current MDPR211 normalizes dash and bullet-like lines such as `-item`, `•`, `·`, `–`, `—`,212 `−`, `ㆍ`, and `▪` into stable list structure while preserving `---` slide213 breaks, pipeline arrows, negative-number prose, year-leading prose such as214 `2026. Roadmap`, fenced code, indented code, and raw `<pre>` blocks. Real215 ordered lists keep source numbering through MDPR splitting. mdpr-skill may216 suggest source cleanup or readability notes around these markers, and may217 consume MDPR source-cleanup diagnostics when available, but must not encode218 marker-specific layout or rendering decisions.219- Keep hints compatible with `agent-hint.json`-style weak semantic input.220- Validate that hints do not encode final rendering choices.221- Prefer minimal hints over broad restatement of the source.222- Run a preflight mindset inspired by reference skills such as `taste-skill`:223 one primary key message per slide by default, no broad restatement of every224 source block, no contradictory template-fill media/icon candidates, and no225 decorative hints that MDPR can already derive deterministically. For recursive226 Pro/RDD loops, reject duplicate or vague TODO proposals before import unless227 they name concrete files, acceptance checks, validation, and new evidence.228- Ground primary key-message candidates with `evidenceRefs` or `claimRef` when229 available. Treat ungrounded primary emphasis as a preflight warning, not as a230 final slide design instruction.231- Require explicit user/request/approval evidence before using232 `style-transform`. Existing PPTX/POTX/theme workflows stay `template-fill`233 unless the user asks to change the visual system.234235Useful local commands when the repo CLI is available:236237```bash238node bin/mdpr-skill.js hint --source-sha256 <64hex> --out .mdpresent/proposals/agent-hint.json239node bin/mdpr-skill.js hint --selection-context .mdpresent/ppt/selection-context.json --markdown deck.md --out .mdpresent/proposals/agent-hint.json240```241242### Review Reports243244Use when reviewing generated MDPR artifacts, manifests, preview images, review reports, or handoff artifacts.245246- Report visual concerns with evidence paths.247- Flag template-fill risks such as master-theme evidence missing, placeholder248 preservation evidence missing, slide-scoped placeholder mismatches,249 rasterized template-fill output, images without source/request, generated250 assets whose provenance is not bound to the asset or slide, undeclared image251 search, new icon substitution, dense content, overly long copy, duplicate252 theme application from MDPR theme flags, and awkward Korean/English wrapping253 visible in rendered previews.254- Distinguish source Markdown problems from MDPR runtime/rulebook problems.255- Turn repeated visual issues into deterministic MDPR rule or config recommendations.256- Keep the output actionable for MDPR maintainers.257- Reference MDPR manifest `validation.polish` when discussing post-AI PPT polish258 quality, and keep that manifest field as the release gate.259260Useful local command:261262```bash263node bin/mdpr-skill.js review --manifest dist/mdpresent-manifest.json --out .mdpresent/review/review-report.json264```265266### Narrative Spine Review267268Use when source Markdown needs content-level review before MDPR renders or269rebuilds a deck.270271- Read Markdown, optional MDPR manifest summaries, and optional source notes.272- Emit claim-title and section-flow suggestions only.273- Include provenance such as source path, manifest slide count, heading text,274 or source-note excerpt.275- Do not emit layout IDs, placeholder IDs, coordinates, colors, typography,276 renderer object IDs, or pass/fail validation decisions.277278Useful local command:279280```bash281node bin/mdpr-skill.js narrative --markdown deck.md --manifest dist/mdpresent-manifest.json --source-notes notes.md --out .mdpresent/review/narrative-review.json282```283284### Template Layout Intent Review285286Use when a PPTX template has been summarized as a layout catalog and the deck287needs semantic layout-intent hints before MDPR chooses any actual layout.288289- Read layout names and placeholder roles from a layout catalog or template290 summary.291- Emit semantic intents such as comparison, chart-focus, evidence, or292 section-divider.293- Treat existing PowerPoint master slides as the theme source when the workflow294 is `template-fill`. Ask for preservation evidence; do not transform the295 master, copy exact placeholder IDs, or choose final layouts.296- Include provenance through the catalog path, layout label, and placeholder297 roles.298- Do not emit placeholder coordinates, placeholder IDs, layout IDs, layout299 selection decisions, colors, typography, or renderer object IDs.300301Useful local command:302303```bash304node bin/mdpr-skill.js layout-intent --layout-catalog template-layout-catalog.json --out .mdpresent/review/layout-intent.json305```306307### LLM-Assisted Content Review Helpers308309Use when the source needs semantic or editorial review before MDPR renders, or310when MDPR-rendered evidence needs a human-readable review artifact.311312- `speaker-notes`: draft presenter notes and reviewer comments from Markdown313 and optional source notes.314- `citations`: flag missing citations, stale sources, and unsupported claims315 from source metadata.316- `rendered-preview`: consume MDPR-generated PNG/contact-sheet paths and emit317 visual concern notes only. Validate these artifacts with318 `validateRenderedPreviewCritiqueBoundary` when available; the notes may cite319 slide labels, rendered image paths, contact sheets, and MDPR finding IDs, but320 must not prescribe exact coordinates, fonts, colors, icons, image paths,321 crops, copied master/layout IDs, z-order, or renderer object IDs.322- `accessibility`: draft alt text, plain-language, acronym expansion, and323 audience-fit suggestions.324- `evidence-ledger`: map slide claims to source metadata and MDPR evidence IDs.325- For readability and Korean decks, recommend shorter claim titles, fewer326 bullets, and moving detail to notes as content suggestions only. Do not pick327 font sizes or exact line breaks.328- Prefer MDPR-provided source-cleanup diagnostics over re-deriving parser329 heuristics. Use raw Markdown marker heuristics only as a conservative fallback330 when no MDPR cleanup diagnostics were supplied.331332These helpers may cite source paths, headings, rendered image paths, MDPR333finding IDs, source IDs, and evidence IDs. They must not emit coordinates,334colors, typography, z-order, geometry, renderer object IDs, or pass/fail335validation decisions.336337For source-neutral style references, prefer `DESIGN.md` frontmatter338`sourceNeutral: true` with semantic tone, density, layout intent, decoration,339and image-policy sections only. Do not include literal hex colors, exact fonts,340copied PowerPoint master/layout IDs, exact icons, image paths, crops, or341renderer object IDs; MDPR owns final theme binding and template preservation.342343Useful local commands:344345```bash346node bin/mdpr-skill.js speaker-notes --markdown deck.md --source-notes notes.md --out .mdpresent/review/speaker-notes.json347node bin/mdpr-skill.js citations --markdown deck.md --sources sources.json --as-of 2026-06-27 --out .mdpresent/review/citation-review.json348node bin/mdpr-skill.js rendered-preview --images rendered-images.json --out .mdpresent/review/rendered-preview-review.json349node bin/mdpr-skill.js accessibility --markdown deck.md --audience "executive review" --out .mdpresent/review/accessibility-review.json350node bin/mdpr-skill.js evidence-ledger --markdown deck.md --sources sources.json --mdpr-evidence mdpr-evidence.json --out .mdpresent/review/evidence-ledger.json351```352353### Change Requests And Override Proposals354355Use when an agent or PowerPoint bridge flow needs to record a proposed change356without applying it directly to MDPR runtime output.357358- Emit `mdpr-change-request-v1` proposals for agent hints, edit intents, policy359 suggestions, pack candidates, or user-override candidates.360- Keep change requests in `proposed` state until the user explicitly approves361 or rejects them.362- Require approval metadata before any pack or override candidate is treated as363 a runtime input.364- Use `edit override-candidate` only for bounded split preferences such as365 `splitBy`, `forceSingleSlide`, or `maxDensity`. It must not encode366 coordinates, colors, recipes, variants, or final layout decisions.367- Prefer `ppt propose --markdown` when a PowerPoint selection context is tied368 to Markdown; this rejects stale source hashes before creating hints or change369 requests.370371Useful local commands:372373```bash374node bin/mdpr-skill.js edit override-candidate --source-sha256 <64hex> --slide-ref slide-3 --instruction "split dense evidence into smaller slides" --split-by h3 --out .mdpresent/proposals/split.override.json375node bin/mdpr-skill.js ppt propose --selection-context .mdpresent/ppt/selection-context.json --markdown deck.md --out .mdpresent/proposals/ppt-selection.change-request.json --hints-out .mdpresent/proposals/ppt-selection.agent-hint.json376node bin/mdpr-skill.js change approve .mdpresent/proposals/ppt-selection.change-request.json --approved-by <user-or-reviewer-id> --approved-at <ISO-8601> --out .mdpresent/proposals/ppt-selection.approved.change-request.json377node bin/mdpr-skill.js change reject .mdpresent/proposals/ppt-selection.change-request.json --out .mdpresent/proposals/ppt-selection.rejected.change-request.json378```379380### Production Override And PDF Boundary381382Use when a revised MDPR runtime supports production override application or PDF383output paths.384385- `mdpr-skill` may propose user-approved override candidates and review386 resulting artifacts.387- MDPR owns applying production overrides, PDF output, renderer behavior,388 validation, and pass/fail decisions.389- Do not encode final layout, coordinates, colors, recipes, variants, renderer390 object IDs, or PDF rendering decisions in skill output.391392### Generator Comparison Boundary393394PptxGenJS, python-pptx, and other PPTX generators are comparison points only.395Use them to describe capability vocabulary or benchmark context; do not add396them as dependencies, fallback renderers, or alternate runtimes. MDPR remains397the deterministic runtime.398399### Codex PPT Compatibility Mapping400401Use when a user asks to support or match `codex-ppt-skill` capabilities in402MDPR or `mdpr-skill`.403404- Treat `codex-ppt` as an image-based workflow reference, not as an alternate405 MDPR renderer.406- Map each feature to an MDPR-native rail: runtime, proposal, review,407 orchestration, bridge, or generated visual asset rail.408- Keep `coverage.unmappedFeatureCount` at `0` before claiming implementation409 coverage.410- Preserve the output-model distinction: `codex-ppt` produces full-slide image411 PPTX; MDPR defaults to editable PPTX/HTML/PDF.412- Use the compatibility map to create MDPR runtime TODOs for missing surfaces413 such as theme-pack registries, generated-asset provider metadata, slide task414 packets, and job-state tracking.415- Use `codex-ppt slide-tasks` when a user needs codex-ppt-style per-slide jobs416 around an MDPR build. These packets are for single-slide review or repair417 proposals and must remain free of geometry, renderer object ids, exact colors,418 z-order, and final layout decisions.419- Use `codex-ppt job-state` after task packet export when a workflow needs420 long-running slide review/repair state. `recorded` and `accepted` updates421 require artifact/report evidence, and `blocked` updates require a blocker422 reason; never treat chat text alone as completion evidence.423- Use `codex-ppt generated-assets validate` for generated visual asset provider424 and quality metadata. The manifest records provider id, model, prompt hash,425 source input hashes, size, quality, background, transparency policy, and426 output provenance without secrets and without becoming a full-slide renderer.427- Cross-check MDPR's mirrored validators for `mdpr-job-state-v1` and428 `mdpr-generated-assets-v1` when the revised MDPR runtime is available.429- Do not copy codex-ppt's full-slide image generation as a default MDPR path.430431Useful local command:432433```bash434node bin/mdpr-skill.js codex-ppt compat --source-ref ningzimu/codex-ppt-skill@93c1e013965a3b42f272252030b2e1a5abede710 --out artifacts/codex-ppt-compat/codex-ppt-compat.json435node bin/mdpr-skill.js codex-ppt slide-tasks --manifest artifacts/external-markdown-visual-eval/iteration-05/build/mdpresent-manifest.json --markdown artifacts/external-markdown-visual-eval/iteration-05/corpus.md --rendered-images artifacts/codex-ppt-slide-tasks/iteration-05/rendered-images.json --out artifacts/codex-ppt-slide-tasks/iteration-05/tasks436node bin/mdpr-skill.js codex-ppt job-state init --tasks artifacts/codex-ppt-slide-tasks/iteration-05/tasks/slide-task-packets.json --manifest artifacts/external-markdown-visual-eval/iteration-05/build/mdpresent-manifest.json --out artifacts/codex-ppt-slide-tasks/iteration-05/mdpr-job-state.json437node bin/mdpr-skill.js codex-ppt generated-assets validate --manifest artifacts/codex-ppt-generated-assets/sample.generated-assets.json438node <mdpr-path>/packages/cli/dist/index.js job-state status <job-state.json> --json439node <mdpr-path>/packages/cli/dist/index.js generated-assets validate <generated-assets.json> --json440```441442### Design Components Boundary443444Use when working with MDPR's built-in design component runtime or related IR.445446- Read Slide Element IR or Presentation IR as the content contract.447- Suggest only semantic hints around intent, grouping, importance, and icon keywords.448- For icon requests that are too large or semantically ambiguous, suggest a449 generated-image candidate only when source image evidence exists or the user450 explicitly approves generated assets; otherwise keep the finding as semantic451 review guidance.452- Explain design review findings in terms of MDPR rulebook/config changes.453- Do not choose recipes, variants, coordinates, shape sizes, typography, colors, z-order, arrows, effects, or exact icon assets.454- Do not duplicate MDPR renderer behavior in the skill.455456### Reusable Theme And Style Pack Proposals457458Use when a user wants more theme variety, a reusable visual style, a new deck459theme, or a style inspired by another PPT/PDF/image while preserving MDPR as460the final renderer.461462- Treat the source as a visual system, not as slide content to copy.463- Extract reusable tokens, semantic layout blueprints, decoration grammar,464 best-fit scenarios, and MDPR registration targets.465- For theme-specific usage, include proposal-only `visualLanguage`,466 `imagePolicy`, and `styleSystem.decorationRules` guidance when available:467 design dials may describe variance, motion, and density, but they must stay468 bounded selection evidence rather than renderer instructions.469- Emit an approval-bound `mdpr-theme-candidate-v1`, not `agent-hint.json`.470- Use `registration.targets` to distinguish `mdpr-theme-pack`, `mdpr-profile`,471 `mdpr-rulebook`, and `deck-local-style-pack` follow-up work.472- Keep generated image and reference-board guidance under473 `imagePolicy.generatedAssetBoundary = "semantic-reference-only"`. Use it to474 describe when images support a theme, how imagery should be treated, and when475 generated imagery is forbidden, not to request exact image assets or476 full-slide image rendering.477- Write decoration guidance as update rules such as downshifting dense slides,478 preferring rule lines over decorative blobs, or using image frames only when479 a source image exists.480- Keep `constraints.mdprOwnsFinalLayout`,481 `constraints.mdprOwnsFinalThemeBinding`, `constraints.noRawUseInAgentHints`,482 and `constraints.requiresDesignLockUpdate` set to `true`.483- Do not include source-private content, exact slide copy, copied layouts,484 final coordinates, exact colors in hints, renderer object IDs, or exact485 icon/assets choices.486- If a candidate should become built-in, route it through MDPR approval/import487 gates before saying it is available as an MDPR runtime theme.488489Useful local command:490491```bash492node bin/mdpr-skill.js design import references/custom.DESIGN.md --out .mdpresent/proposals/custom.theme-candidate.json493```494495### Design Coherence Audit496497Use when auditing Design Components Styled Deck IR before rendering or release.498499Check for:500501- raw hex in PPT theme mode502- mixed radius family503- mixed shadow family504- mixed spacing scale505- mixed type scale506- excessive accent use507- excessive decorative effects508- dense slides using expressive effects509- repeated layout rhythm510- non-editable PPTX primary text plans511512Return JSON-style findings when the caller needs CI output, or a concise human-readable fix list when working interactively. Findings may explain why an issue exists, but fixes must stay at the MDPR rulebook/config or deterministic policy level.513514## PowerPoint Bridge Boundary515516When working with `mdpr-ppt` or PowerPoint selection context:517518- `hint rail`: emit weak `agent-hint.json` semantics only.519- `review rail`: emit `review-report.json` findings only.520- `edit-intent rail`: record page or decoration change requests as safe proposals.521- `approved override / pack rail`: require user approval before MDPR validates and applies override or pack candidates.522- Prefer `--markdown deck.md` with selection-context commands so stale source523 hashes are rejected before hints or proposals are handed to MDPR.524525Never emit final PowerPoint geometry, object IDs, z-order, exact colors, or exact icon assets from a selection context.526527## Validation528529Prefer the repo's existing commands when the `mdpr-skill` checkout is available:530531```bash532node bin/mdpr-skill.js gate validate-schema-sync --mdpr-path <mdpr-path>533npm run validate534npm run check:mdpr535npm run check:mdpr-pandoc536```537538For focused artifact work, validate the exact JSON schema or report contract539touched by the task before presenting findings as release-ready. For revised540MDPR compatibility work, include the schema-sync gate and any mirrored MDPR541validator that corresponds to the artifact under review.