codex-slides-deck

1# Codex Slides Deck
2 
3The canonical `codex-slides` sibling skill owns the complete workflow. Use the
4`codex_slides` MCP tools when available; otherwise run its self-contained CLI
5at `../codex-slides/scripts/codex-slides.mjs`. Keep the live workspace available
6in the in-editor Browser whenever visual review helps.
7 
8## Choose the flow
9 
10- Default to the live Browser workflow: open the Codex Slides home screen,
11  submit the request there, then operate the created project through clarify,
12  outline confirmation, style selection, rendering, and review. Keep the
13  Browser visible throughout.
14- If Browser UI submission fails, use `start_project` / CLI `start-project` to
15  create the durable project shell, immediately open its returned URL, and
16  continue in the UI.
17 
18- Use `list_scenarios` / CLI `scenarios` when a named workflow such as business
19  report, document-to-deck, data insights, brand application, localization, or
20  batch generation fits. Upload required slot files and pass `scenarioId`,
21  `materialIds`, and `materialContexts` into creation.
22- Only when the user explicitly requests an unattended/headless one-call
23  result, call `create_deck` or CLI command `create`.
24- For CLI automation or recovery, call `create_outline`, optionally
25  `revise_outline` and `rank_inspiration`, then `render_deck`; the CLI commands
26  are `outline`, `revise-outline`, `inspiration`, and `render`.
27- For an existing deck, use `list_projects` or `get_project`, then choose the
28  smallest mutation tool.
29…