بنقرة واحدة
slides-grab-plan
// Stage 1 planning skill for Codex. Build and iterate slide-outline.md until explicit user approval.
// Stage 1 planning skill for Codex. Build and iterate slide-outline.md until explicit user approval.
Stage 2 design skill for Codex. Generate and iterate slide-XX.html files in the selected slides workspace.
End-to-end presentation workflow for Codex. Use when making a full presentation from scratch — planning, designing slides, editing, and exporting. PDF and per-slide PNG are preferred; PPTX/Figma export is experimental / unstable.
Generate square Instagram-style card news by reusing the slides-grab workflow with card-news mode enabled. Defaults to per-slide PNG export.
Stage 3 conversion skill for Codex. Convert approved HTML slides to PDF or per-slide PNG reliably, and to experimental / unstable PPTX/Figma outputs on a best-effort basis.
| name | slides-grab-plan |
| description | Stage 1 planning skill for Codex. Build and iterate slide-outline.md until explicit user approval. |
| metadata | {"short-description":"Create and revise slide outline before design stage"} |
Use this when the user asks to start a new presentation from scratch.
Produce an approved slide-outline.md before any slide HTML generation.
slide-outline.md (must include style: <id> in meta section)slides-grab list-styles, shortlist 2–3 styles, and get explicit user approval. Optionally offer slides-grab preview-styles for visual preview. Record as style: <id>.
b. Custom DESIGN.md path — if a local DESIGN.md exists (e.g. provided directly or fetched via slides-grab import-design <https-url>), inspect it with slides-grab show-design ./DESIGN.md and confirm with the user.
c. Free-form custom direction — if neither bundled nor DESIGN.md fits, propose a written custom direction and get approval.DESIGN.md imported from voltagent/awesome-design-md or similar sources describes a marketing website (top-nav, hero-band, CTA buttons, pricing cards, footer-band). Slides are single 720pt × 405pt frames with no scroll, no nav, no clicks — copying web components into slides produces deck pages that look like landing pages.references/design-md-to-slides-conversion.md for the canonical conversion guide../DESIGN.md into a sibling ./DESIGN.slides.md next to it. Leave the original DESIGN.md untouched. The DESIGN.slides.md MUST follow the Output Contract in the reference and apply every row of the web → slide mapping table (top-nav → eyebrow strip, hero-band → cover layout, CTA buttons → kicker text, footer-band → thin footer strip, pricing grids → dropped, etc.).slides-grab show-design ./DESIGN.slides.md to confirm the parser reads it cleanly.slide-outline.md with ordered slides and key messages. Record the approved style reference in the meta section:
style: <id>style: ./DESIGN.slides.mdstyle: block describing it<slides-dir>/slide-*.html) in this stage.slides-grab CLI.If needed, use the bundled outline reference:
references/outline-format.mdreferences/plan-workflow-reference.md — archived detailed planning workflow and organizer-agent guidancereferences/design-md-to-slides-conversion.md — DESIGN.md (web) → DESIGN.slides.md (slide) translation guide, including the structured output template and the web → slide mapping table