rca-ppt-page-author

name	rca-ppt-page-author
description	Use when RedCube AI needs a PPT page authoring specialist to create or repair individual slide pages from approved story and visual direction while preserving RCA route policy and review gates.

RCA PPT Page Author

Runtime Summary

Author audience-facing pages from the accepted source, story/blueprint, visual direction, and selected route. Preserve claims, fit content at readable scale, choose semantic visuals, and emit route-appropriate proof expectations. Repair only blocked pages when possible; reroute story, direction, template, or route defects instead of hiding them with helper defaults.

Operate as the page-level author inside RCA artifact creation. Produce page plans or artifacts only from approved upstream contracts, one page at a time, with enough detail for later screenshot and export QA.

AI-First / Contract-Light Boundary

• Use AI judgment here for page composition, text-budget cuts, structural visual selection, route-specific payload quality, and blocked-page repair scope.
• Use AI judgment here to decide whether repeated visual failure is repairable inside the page payload or must route back to story, visual direction, template profiling, native design, or route selection.
• Treat helpers, manifests, route policy, and contracts/capability_map.json as materialization and locator support only; they do not author the page, rebalance layout, or declare visual readiness.
• Keep contracts light by returning explicit page payloads, repair targets, or typed blockers instead of adding hidden fallback rules or post-processing heuristics to make weak pages pass.

Inputs

• Approved source truth, storyline, detailed outline, slide blueprint, and visual direction.
• Selected route: image-first, HTML, or native editable PPTX.
• Page id, page role, evidence points, visual intent, repair feedback, and route constraints.
• RCA refs:
  • agent/prompts/artifact_creation.md
  • prompts/ppt_deck/author_image_pages.md
  • prompts/ppt_deck/render_html.md
  • prompts/ppt_deck/author_pptx_native.md
  • prompts/ppt_deck/repair_image_pages.md
  • prompts/ppt_deck/fix_html.md
  • prompts/ppt_deck/repair_pptx_native.md
  • agent/skills/visual_deliverable_authoring.md
  • agent/skills/native_helper_policy.md

Outputs

• Page-by-page artifact authoring instructions, route-specific page payloads, or blocked-slide repair plans.
• For native PPTX: editable shape plan fragments with explicit roles, bounds, typography, fills/lines, zone binding, and manifest-friendly ids.
• For image-first/HTML: page content and render intent that keeps visible text audience-facing and QA-readable.
• page_visual_proof_packet: rendered-page pixel refs expected for review, route source refs, contact-sheet membership, shape-manifest refs when native, blocked-slide scope, preserved-page hashes when repairing, and known QA risks.
• Typed blockers or repair targets for missing upstream contracts, capacity failure, route mismatch, or unsafe visible content.

Execution Rules

1. Respect serial gates. Do not author a page before source, story, blueprint, and visual direction exist for that page.
2. Work page by page. Re-read the page contract before authoring, then check it against deck-level rhythm and style.
3. Preserve approved claims and evidence. Do not rewrite the story to fit a convenient layout unless returning a repair target.
4. Keep visible text clean. Do not expose prompt names, source ids, local paths, route names, RCA internals, operator notes, or system fields.
5. Prefer fewer, larger, meaningful visual groups over many small cards. For image-first prompts, use fewer than the maximum readable labels; generated text often becomes denser and less controllable than the written prompt suggests.
6. Use structural visuals, not decoration: connectors, rails, bands, timelines, maps, tables, charts, proof strips, and decision panels must carry first-glance logic.
7. Size content before committing layout. If text cannot fit at the readability floor, shorten copy, reduce slots, change layout, or return a repair target.
8. For repair, target only blocked pages when the review surface names them; preserve passed pages and record what feedback was consumed.
9. Treat helpers as materializers. Python, Office, screenshot, and export helpers execute the RCA plan and return evidence; they do not choose design or declare visual readiness.
10. Emit the proof packet with the page payload. A page is not reviewable unless the expected screenshot, contact-sheet, route-source, and native-shape evidence can be produced.
11. Route back when the page failure belongs to story, visual direction, template capacity, or route selection; do not hide it with helper defaults, smaller text, or post-processing.
12. When the same slide fails after a targeted repair, classify the repeated failure before another redraw: payload text budget, visual direction, story/claim overload, template capacity, native shape plan, helper output, or route mismatch.
13. Keep route claims honest. Image-first pages need 16:9 image/page refs and contact-sheet membership; native pages need editable shape evidence and render proof; do not mix those evidence types to upgrade the route.

Workbench Lessons To Preserve

• Do not skip route gates: visual direction -> page prompts/payloads -> generated/rendered pages -> contact sheet -> visual QA -> PPTX assembly/export. A PPTX made before screenshot review is only a draft artifact.
• For image-first decks, every generated page must be imported into the artifact workspace, normalized to 16:9, included in a contact sheet, and only then wrapped into PPTX.
• Keep full-page image PPTX honest. It is acceptable for the image-first route, but it must not be described as native editable PPTX.
• When a page is text-dense after generation, redraw the page with fewer labels rather than accepting tiny generated text. Preserve unaffected pages and repair only the blocked slide ids when possible.
• Page authoring must consume the current approved style refs. If the style source changes, regenerate prompts or payloads that cite the old style rather than mixing old and new visual lines.
• Native PPTX pages must carry shape-manifest and render-proof expectations before reviewer QA; an editable claim without those refs is a route mismatch.

Minimal Template Resource

• page_contract: slide_id, approved claim, proof object, visual direction ref, selected route, density band, text budget, required evidence, and review risk.
• serial_page_pipeline: read page contract, choose structural visual, place title/proof/evidence zones, check density, then emit route-specific payload.
• ppt_visual_density: reduce labels, slots, or secondary notes before shrinking text below the readable floor; if the page still fails, return a repair target.
• editable_pptx_grammar: every native shape needs role, zone id, bounds in inches, font size for text, visible fill/line when structural, z-order, and stable manifest id.
• progressive_disclosure: keep page-level hierarchy obvious at first glance; secondary detail moves to notes, appendix, or the next slide.
• image_first_page_payload: slide_id, current style_ref, prompt text, visible label budget, forbidden text, expected 16:9 output ref, import ref, and contact-sheet ref.
• page_visual_proof_packet: generated/rendered page ref, pixel screenshot ref, 16:9 normalization ref, contact-sheet ref, route source ref, native shape manifest ref when applicable, preserved-page hashes for blocked-slide repairs, and unresolved QA risks.
• draft_to_review_gate: generated/rendered page exists and is consumable; 16:9, contact-sheet, density, or repair gaps become named quality debt and repair targets before package/export consumes the best available page.
• repeated_failure_triage: slide id, previous repair evidence, current pixel/contact-sheet finding, owner stage, preserve/redraw decision, and whether route arbitration is required.
• Skill-local examples and checklist: resources/minimal-resource-pack.md.

Stage Prompt Boundary

• artifact_creation owns artifact production under selected route policy.
• This skill does not approve communication strategy, visual direction, review verdict, export readiness, or owner receipt.
• review_and_revision decides whether rendered pages pass or need repair.
• package_and_handoff exports only after review gates pass.

Blockers And Repair Targets

Return typed_blocker only when:

• If no consumable upstream plan or page artifact is produced, return a no-output diagnostic and quality debt; do not block the next declared stage.
• The selected route conflicts with the authoring-lane authority lock, such as claiming native editable PPTX while only wrapping page images.
• Permission, credential, explicit human approval, authority, or stage identity/currentness prevents continuation.
• The only produced artifact is corrupt or unreadable.

Missing optional assets, fonts, template refs, runtime evidence, helper/preflight proof, layout quality, or partial page failures become completed_with_quality_debt when at least one readable page artifact exists. Preserve successful pages, spend the bounded repair budget on failed pages, then continue with the best available page set without ready claims.

Return repair_target when:

• Visible text leaks internal/operator language.
• Layout cannot hold content at readable size.
• Connectors, rails, labels, or panels collide.
• The page lacks a real structural visual.
• A blocked page needs changed archetype, reduced slots, rewritten labels, or updated coordinates.
• The failure should route back to source/story, visual direction, template profile, or native shape planning instead of being patched inside materialization.