DeckCoderAIDownloads

FOR THE HUMAN + THE AGENT

Connect your
AI agent.

Add the presentation skill to Codex or Claude Code, or connect your agent to a deck you already have open.

DeckCoderAI gives an external AI agent a local way to author ordinary HTML, inspect saved scenes and try live controls. You choose the presentation and the scope.

CLIMCPComputer Use
Install the presentation skill

CODEX / CLAUDE CODE

Add the presentation skill.

Install it in your project, then ask for a talk with reveals, comparisons or audience choices. Your agent can choose DeckCoderAI without you naming the app.

The skill uses the separate desktop app. It does not grant access to an open deck.

Install for both agents

Run this from your project folder with Node.js and npx, then start a fresh agent session.

npx skills add tojileon/deckcoderai-skill --skill deckcoderai-presentations --agent codex claude-code

01 / OPTIONAL LIVE APP CONNECTION

Your tools.
Your permission.

  1. 01

    Open your presentation.

    Choose a build on the download page, read its platform limits, open the deck you want to work on, and save or discard any drafts.

  2. 02

    Configure your client.

    In Agent access, copy the configuration for Codex, Claude Desktop, Cursor, VS Code or Generic JSON. Merge it into your client and restart its MCP server.

  3. 03

    Choose the scope.

    Enable access for this presentation. It ends when you revoke it, open another deck or quit. Preparing a request does not start a model.

02 / THE FIRST CONVERSATION

Start with
a clear brief.

Give your agent the subject, audience and change you want the presentation to make. Then ask it to read the app’s current context.

A STARTING POINT TO COPY & MAKE YOUR OWN

Read this site’s /llms.txt and /agent-guide.md. Help me build a presentation in DeckCoderAI. Ask for my subject, audience and intended outcome. Read the current app context and effective preferences. Preserve my notes, work within my chosen scope, and verify the saved result and important interactions.

03 / CHOOSE THE RIGHT INTERFACE

Build. Inspect.
Try it for real.

Use the installed CLI for saved files, MCP for the open app and guarded edits, and Computer Use for native interaction.

Use the installed app’s CLI. If your installation is elsewhere, use the invocation returned by the app’s authoring brief.

"/Applications/DeckCoderAI.app/Contents/Resources/deckcoder" guide --json
"/Applications/DeckCoderAI.app/Contents/Resources/deckcoder" init ./my-talk --starter stage
"/Applications/DeckCoderAI.app/Contents/Resources/deckcoder" check ./my-talk --json
"/Applications/DeckCoderAI.app/Contents/Resources/deckcoder" render ./my-talk --steps all -o ./frames
"/Applications/DeckCoderAI.app/Contents/Resources/deckcoder" export ./my-talk --format browser -o ./my-talk.html
Installed app · saved-file workflow · no source checkout required

A GOOD SCENE IS MORE THAN A SUCCESSFUL SAVE.

Keep the human
in the story.

01 / CREATE WITH PURPOSE

Imagine the scene.

Choose an idea, a presenter action and a visible change that helps someone understand. A deliberate still image is a valid choice too.

02 / RESPECT THE SOURCE

Preserve what matters.

Keep notes and unrelated content intact. Read current revisions and scope before guarded writes. Rejected candidates stay unsaved.

03 / VERIFY THE EXPERIENCE

Rehearse the important parts.

Check saved frames and findings, then try controls, Back and Reset. Technical checks do not certify beauty or projector legibility.

DIRECT ROUTES FOR AGENTS

The useful details.
Ready to read.

01Start herellms.txt ↗02Authoring & verificationAgent guide ↗03Capabilities & limitsJSON manifest ↗04Mac preview recordArtifact metadata ↗

Windows experimental artifact record ↗

This website provides documentation and local browser demonstrations. It does not execute commands, connect to your desktop or expose a remote MCP server. External AI services have their own permissions and charges.