Convert raw material into per-page Content PROMPTs by analyzing content density, intent, and slide usage. Outputs $HUMAN_MATERIAL_PATH/slides/<deck>/prompts/content/<deck>.md. Use when the user has notes/materials and wants a well-planned per-page content prompt before styling.
Turn raw material (notes, markdown, images, links) into a per-page Content PROMPT file that:
$HUMAN_MATERIAL_PATH/slides/<deck>/materials/... (preferred) or a provided Markdown blob$HUMAN_MATERIAL_PATH/slides/<deck>/configs/deck.yaml (audience/language/style/dimensions)Write to: $HUMAN_MATERIAL_PATH/slides/<deck>/prompts/content/<deck>.md
Format (recommended):
## Page N: <title>Templates and references:
references/content-prompt-template.mdreferences/analysis-framework.mdreferences/content-rules.mdPage N and Page N (cont.).For a more detailed checklist, see:
references/content-prompt-template.mdreferences/analysis-framework.mdreferences/content-rules.mdreferences/splitting-guide.mdreferences/common-pitfalls.mdUse a consistent phase checklist (inspired by the planning/validation patterns in archived v1 skills):
Copy/paste checklist:
## Review gate (required)
Do not proceed to `styled-prompts` until the content prompt passes:
- No silent dropping (everything important is in “Must include” somewhere)
- Each page has exactly one intent and a clear primary representation
- Any missing data for tables/figures is explicitly marked as TODO
Content PROMPT Progress:
- [ ] Setup & analyze (audience, use case, length)
- [ ] Draft page plan (titles + representations)
- [ ] Density pass (split/merge)
- [ ] Consistency pass (terms, acronyms, naming)
- [ ] Coverage pass (no silent dropping)
Treat $HUMAN_MATERIAL_PATH/slides/<deck>/prompts/content/<deck>.md as the single source of truth for planning.
Page N and Page N (cont.), then re-check density and intent.When this skill is triggered:
$HUMAN_MATERIAL_PATH/slides/<deck>/prompts/content/<deck>.md.$uv-styled-prompts, no $uv-styled-artifacts, no rendering sanity-checks) unless the user explicitly requested them in the same message.Recommended next steps (include this block in your response):
$uv-styled-prompts on the generated file.
$HUMAN_MATERIAL_PATH/slides/<deck>/configs/deck.yaml (style:) if present$HUMAN_MATERIAL_PATH/slides/styles/blueprint.md, $HUMAN_MATERIAL_PATH/slides/styles/chalkboard.md, $HUMAN_MATERIAL_PATH/slides/styles/sketch-notes.md, ...$uv-styled-prompts convert "$HUMAN_MATERIAL_PATH/slides/<deck>/prompts/content/<deck>.md" + "$HUMAN_MATERIAL_PATH/slides/styles/<style>.md" into "$HUMAN_MATERIAL_PATH/slides/<deck>/prompts/styled/<deck>.md".If the user requested only a sample (e.g. 4 pages), recommend validating the sample first, then rerunning this skill for full coverage.