tomjiu Ardot Slides
Domain workflow and guidelines for slide deck / presentation deliverables on the Ardot canvas.
The general workflow and hard rules live in
ardot-design-core, which is injected alongside this skill. This skill carries the slide-specific 6-phase workflow and design rules. The slides workflow is more detailed and takes precedence over the generic core workflow for deck tasks — followslides-workflow.mdend-to-end, and use core for schema, editing rules, effects, and screenshot verification.
Slide Workflow (follow strictly — do NOT improvise from the core skeleton)
- Core slide workflow →
{SKILL_ROOT}/workflows/slides-workflow.md— the 6-phase process (Phase 0 Requirement Clarification → Phase 5 Final Review). Phases 0→4 are strictly sequential. - Mandatory slide design rules →
{SKILL_ROOT}/references/guidelines-slides.md— L01–L20 layout contracts, large typography, rich backgrounds, visual rhythm. This is the authoritative source for all slide visual decisions.
Files referenced by the slide workflow that live in the core skill (
design-rules.md,ardot-workflow.md,ardot-schema.md,effects-guide.md) are read from the ardot-design-core skill root — its absolute path is provided in the same prompt that injected this skill.
pptx Boundary (read before starting)
This skill produces a design (Ardot canvas). If the user explicitly wants a PowerPoint .pptx file as the deliverable — "导出 pptx", "生成 PPT 文件", "export to PowerPoint", or references an existing .pptx filename — that is not this skill's job; defer to the pptx skill. If the user says "设计稿", "design", "Ardot", "canvas", "mockup", or gives no file-format constraint, stay here.