Fork it, hand Claude your website or brand PDF, and keep taking runtime updates. A brand starts as nine tokens and extends to your own layouts, CSS and scripts.
What slaydy maintains, so you don’t
Every deck is one HTML file on a runtime that keeps getting better without your fork doing anything. People fix it in the browser, Claude revises the same file, and nobody’s edits get thrown away.
Open deck.html in Chrome and press E.
“apply my notes”
Present, print, or send it.
For skill builders
The lazy way is one prompt pasted into Claude Code. The same thing as seven steps is right below it. Either way you end with an installed brand skill that keeps taking updates, and the runtime is never yours to touch.
Copy this, replace the three brackets, and paste it into Claude Code in any folder. It clones slaydy, makes your fork and stops for your review before writing anything.
Set up a slaydy deck skill for my brand. Brand: [brand name] Skill name: [what to call the skill, by default brandname-decks] References: [where to find the brand: the website, and anything else worth reading, such as a brand guidelines page or where the logo is] 1. If ~/Code/slaydy does not exist, clone https://github.com/klarasch/slaydy.git there. Never edit that checkout. 2. Read ~/Code/slaydy/SKILL.md section 8 and follow it: make the fork beside the checkout and read my brand from the references above. 3. Show me the colours, type and voice rules before writing any file, and wait for my go. 4. Then write the brand, build the skill, check that a sample deck renders, and commit. 5. Ask me before installing the skill or creating a GitHub repo.
Or step by step
Clone it where you keep code. This checkout is upstream: you never edit it, and every brand fork on your machine updates from it.
git clone https://github.com/klarasch/slaydy ~/Code/slaydyThe repo tells Claude how to set up a brand, so nothing needs installing yet.
cd ~/Code/slaydy && claudeHand over a website, a brand PDF or a logo. Claude makes the fork, ~/Code/acme-decks, beside slaydy and reads the brand.
set up slaydy for Acme from acme.comColors, type and voice rules come back before a single file is written. Say go, or say what’s off.
goClaude writes the brand, builds acme-decks, checks a sample deck renders, commits, and installs on your yes. From then on, “make me a deck” comes out in Acme.
yes, install itClaude creates a private GitHub repo only when you ask. Teammates install acme-decks-skill.zip or build from the repo.
push the fork to GitHubWhen slaydy releases, open acme-decks in Claude Code. One prompt pulls, copies the runtime in, rebuilds, and tells you what changed.
take the slaydy update> set up slaydy for Acme from acme.com, logo is in ~/Downloads/acme.svg
This is slaydy itself, so Acme gets its own fork: ~/Code/acme-decks.
Read acme.com. Here’s the brand before I write anything:
Type: Manrope for headlines and body. Wash off, it reads as a startup deck.
Voice: sentence-case headlines, no “synergy”, every deck ends on a next step.
> go
wrote themes/acme.css, themes/acme.md, images/logo.svg
wrote SKILL.fork.md name: acme-decks
wrote skeleton.html
built dist/acme-decks/
check 3-slide deck renders in Acme
commit Acme brand
Install to ~/.claude/skills/acme-decks?
runtime.jsnav, overview, edit, presenter, saveruntime.csslayout library and print stylesSKILL.mdmodes, brief, generation procedureLAYOUTS.mdthe markup contract Claude followsbuild.shassembles the skill into dist/standalone.pybuilds the single shareable fileSKILL.fork.mdskill name, description, standing ordersthemes/acme.cssnine tokens and any brand CSSthemes/acme.mdthe brand’s voice and rulesskeleton.htmldeck shell: links, fonts, body attributesfonts/ images/licensed fonts, the mark, artcustom/bespoke layouts, when you ask for them:root {
--app-bg: #dfe4ec;
--bg: #ffffff;
--fg: #1b2b4b;
--muted: rgba(27, 43, 75, 0.56);
--faint: rgba(27, 43, 75, 0.13);
--surface: #f1f4f8;
--accent: #0a66ff;
--accent-2: #ffb000;
--accent-fg:#ffffff;
}
--- name: acme-decks description: Generate editable, Acme-branded HTML slide decks and revise existing ones. Use whenever the user wants slides, a deck, a pitch, a talk. --- **This install is brand-locked to Acme.** Always copy themes/acme.css, fonts/ and images/; never set data-themes; never ask which theme. Read themes/acme.md before writing a slide.
Colours, typefaces, radius and the wash restyle every layout at once. Most brands stop here.
The theme is a full stylesheet loaded after the runtime: patterns, section treatments, your own emphasis style.
Define slide--acme-demo, describe it in themes/acme.md, and Claude generates and revises it. One line puts it in the Add-slide picker.
A custom/ folder adds behaviour on runtime events: your own transitions and slide options, animation, interactive slides like the one in the demo.
Without code
No terminal, no git. Upload slaydy to Claude desktop or claude.ai, ask for your brand in a chat, and Claude hands back your own skill as a zip to upload next to it.
Get slaydy-skill.zip from the latest release on GitHub.
In Settings › Capabilities › Skills, upload the zip. Code execution needs to be on.
In a new chat, name the brand. Attach a brand PDF or a logo if you have one.
“set up slaydy for Acme from acme.com”
Colors, type and voice rules come back first. Say go, or say what’s off.
“go”
Claude hands back acme-decks-skill.zip. Upload it the same way, turn off plain slaydy, and send the zip to your team.
Updating later: upload the new slaydy zip, then ask “update my Acme skill”. You get a fresh zip with the new runtime and your brand untouched.
Updates
Everything slaydy ships is replaceable, and everything yours lives in files a release never contains. Ask Claude to take the latest slaydy update and it runs take-update.sh, which refuses to overwrite a file your fork edited, names it, and takes the rest.
--dry-runreport what would change, copy nothing--checklist upstream files the fork edited; cheap enough for a pre-commit hook--forceoverwrite fork-edited files anywayEvery entry is marked as a new feature or a fix, and says whether a fork has nothing to do, something to check, or something to port.
Claude picks from these layouts instead of inventing one. Releases add classes; they never rename or remove them, so decks from last year and your customisations both survive.
titleagendasectionstatementbulletssplitcardsbentostatsnumbertablecomparetimelinequotecodeimagefullgallerycalloutcallout-fullplaceholderend