codex-slides-browser

1# Codex Slides Browser
2 
3This specialized skill remains for compatibility. The canonical
4`codex-slides` sibling skill owns the full workflow and portable CLI.
5 
61. Call `open_codex_slides` when the MCP tool is available. Otherwise run
7   `node ../codex-slides/scripts/codex-slides.mjs open --json '<input>'` from
8   this skill directory. Pass `projectId` when the user named a deck;
9   otherwise omit it for the create workspace.
10   Use `view:"scenarios"` for the 24-workflow catalog,
11   `view:"design-files"` plus `projectId` and optional `filePath` for project
12   files, or `view:"brand-system"` plus `projectId` for the brand editor.
132. Navigate the returned resource link in the Codex in-editor Browser. Do not
14   stop after printing the URL and do not ask the user to open it manually.
15   Follow `browserHandoff.url` exactly so slide, panel, version, mode,
16   checkpoint, conversation, and run focus are preserved.
173. For a new deck, always open and verify the home/create screen before any
18   research, outline, or rendering call. Submit the topic in that UI so it
19   creates a durable project and opens the guided workspace. Use
20   `start_project` / CLI `start-project` only if UI submission needs a
21   deterministic fallback, then navigate its project resource immediately.
224. Keep the Browser visible and operate the checkpoints in order: clarify,
23   outline review, inspiration/style selection, render, deck review. Do not run
24   the entire workflow invisibly in the Codex conversation.
25…