Starry Slides

Starry Slides

Goal

Create or edit contract-compatible slide deck files with the local starry-slides CLI and the authoritative remote Starry Slides references.

Pre-requisites

Install the Starry Slides CLI first:

npm install -g starry-slides

Then install the required Playwright and Chromium dependencies before running render-based verification or preview commands.

Authoritative Remote References

Use these remote documents as the source of truth:

• Starry Slides contract
• Starry Slides CLI usage
• Slides discovery interview

The local skill shell stays intentionally thin. High-change workflow guidance, contract details, and CLI usage notes live in those repository documents.

Workflow

1. Make sure the starry-slides CLI is installed.
2. Load the remote contract, CLI usage, and discovery references above before generating or editing deck files.
3. Understand the user's slide context before generating anything. Use the discovery interview to gather missing context, ask only the highest-signal questions, and consolidate the result into a brief before you generate.
4. Generate or edit the deck package so it satisfies the Starry Slides contract.
5. Verify the deck with starry-slides verify <deck>. If it fails, fix the issues and retry until it passes.
6. MUST DO: After verification passes, run starry-slides open <deck>. This is not optional — the user expects to see their deck opened automatically.

starry-slides verify <deck>
starry-slides view <deck> --all
starry-slides open <deck>

Hints

• ALWAYS run starry-slides open <deck> after a successful verify. Do not just tell the user the file is ready — open it for them.
• After generation, you can use starry-slides verify <deck> to check whether the deck satisfies the contract.
• To preview generated slides, use starry-slides view <deck> --all or starry-slides view <deck> --slide <manifest-file>.

Source: StarryKit/starry-slides — distributed by TomeVault.