Drop it into chat
Under about 50KB. Attach it to your message, tell Claude where it goes. Claude uploads it into the deck's assets folder and references it on the slide.
Open Claude Desktop, describe what you want, get a polished RKH-styled deck back. Brand rules baked in. No JSX, no commands, no git.
Everyone with an RKH login does this once. After that the deck builder lives inside Claude Desktop alongside your other chats.
Download from claude.ai/desktop and sign in with your Pro, Max or Team account. Free Claude accounts work too but the chat budget is tighter.
Ask Jake, or open /admin?key=<ADMIN_KEY> if you have admin access and issue your own. The URL looks like https://decks.rkhdigital.com/mcp/u/yourname?token=<long-hex>.
Open ~/Library/Application Support/Claude/claude_desktop_config.json. Cmd+Shift+G in Finder navigates straight there. If the file is empty, paste this and replace the URL with yours.
{
"mcpServers": {
"rkh-decks": {
"command": "npx",
"args": ["-y", "mcp-remote", "<your URL>"]
}
}
}
Cmd+Q completely — the dock icon must disappear. Reopen. In a new chat, the deck-builder tools are now live. You can keep using Claude for everything else as normal.
You do not need a special command. Just describe the deck — Claude takes it from there.
"I want to build a small RKH deck about our Q2 results. Internal team, 8 slides, cyan accent. Standalone read-out."
About ten questions across two or three messages — title, audience, colour, slide budget, whether you want statement slides and a recap. Answer plainly, anything you skip Claude will sensibly default.
A slide-by-slide list with the primitive type for each. Claude waits for your approval before scaffolding the deck. Push back on anything that feels off.
You get a preview URL — open it in a new browser tab. As slides land, the preview rebuilds in the background. Refresh the tab when Claude says a batch is done.
Tell Claude what you want changed. "Slide five needs a quote, not a stat." "Make the colour cyan everywhere." "Move slide three to the end." Claude updates the JSX and rebuilds.
Say "publish it" when the deck is ready. The deck lands at https://decks.rkhdigital.com/d/<your-slug>/ — a shareable URL you can paste into emails or invites.
Three paths, depending on what you have.
Under about 50KB. Attach it to your message, tell Claude where it goes. Claude uploads it into the deck's assets folder and references it on the slide.
Anything bigger. Claude hands you a pre-filled URL — click it, drop the same file into the form, page confirms. Say "done" in chat. Claude picks it up.
Notes plus images plus the odd video. Zip locally with zip -r mystuff.zip mystuff/, drop the zip into the upload form. Claude reads the markdown and references the images directly.
For Unsplash, Pexels or any other public URL, just paste the link into the chat. No upload step at all — the deck references it directly.
Say "publish it" when the deck looks right. Claude commits the deck, builds the single-file HTML, and gives you back a public URL.
Share that URL with clients, embed in emails, drop into calendar invites. The deck is a single self-contained HTML file — no external dependencies, opens offline once loaded.
To continue an existing deck, paste its /d/<slug>/ URL into a fresh chat, or say "continue the deck I was just working on". Claude picks up where you left off.
The preview rebuilds after every change, but the browser likes to cache. Cmd+Shift+R does a hard refresh and forces the latest.
"Slide four is broken." "The image is not loading." "That title is too long." Claude can read the slide source, diagnose, fix.
If a deck genuinely will not build or publish, send the deck URL. There is usually a one-line fix.