style-library
Skill0 starsChanged 12 days agoMITView on GitHub
Save, list, apply and update named style packs for web-slides decks — theme tokens plus React/CSS component patterns (title hero, KPI, timeline, …). Use when the user likes a deck or component look and wants to reuse it later, asks to save a theme pack, apply a saved style, or browse the style library. Companion to web-slides; does not replace building a deck.
5 other projects use a version of this.
Adopted by
Most recently taken up by
- F0rger123/claude-video-editing-god-modetheir own version, first seen Oct 25, 2026
- NexumAI-online/skills-ediciontheir own version, first seen Oct 25, 2026
- nateherkai/herk-edit-kittheir own version, first seen Oct 15, 2026
- nateherkai/hyperframes-student-kittheir own version, first seen Oct 14, 2026
- nateherkai/hyperframes-video-pipelinetheir own version, first seen Sep 8, 2026
Other versions5 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 5
- nateherkai/hyperframes-student-kit★ 2.2ksame name
- nateherkai/herk-edit-kit★ 1.5ksame name
- nateherkai/hyperframes-video-pipeline★ 21same name
- NexumAI-online/skills-edicion★ 4same name
- F0rger123/claude-video-editing-god-mode★ 1same name
How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.
In this repository2 other files it gives its agents.
- slide-reviewerSkill
- web-slidesSkill
The file
We split this skill into the rules it gives an agent
6 rules. 0 are common, 3 are distinctive, and 3 are very specific to this project.
0
Common
Most of the 4 edited versions we read keep these.
3
Distinctive
This author's own choices. Worth a look.
3
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 22
After polishing a deck whose brand or layout recipes are worth reusing.
- Distinctive: line 23
Before inventing a new brand from scratch when a pack already covers the need.
- Very specific: line 25
Prefer web-slides built-in / inspiration themes (midnight, aurora, paper, tech-dark, bento-minimal, navy-pitch) for generic looks.
- Very specific: line 35
Search order for list / apply: $STYLE_LIBRARY_DIR → user dir → repo styles/.
- Distinctive: line 41
Run from the repo root (or any cwd.
- Very specific: line 65
Update: If the user refined the look, update --id <pack-id> --from <deck>.
“Common” is measured: kept by at least 6 in 10 of the 4 edited versions of this file we could read. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
Style library
Capture a look you (or the user) liked — theme tokens and/or component/layout patterns — as a named pack, then reuse it on the next deck.
This skill does not vendor third-party PPTX/Google Slides. Packs are original CSS/TSX snapshots (and short Markdown recipes) derived from a web-slides deck you already built or from this repo’s template.
Paths below are relative to this skill directory unless noted. Read references/ when a step tells you to.
When to use
- User says “save this style”, “remember this theme”, “use the airport title look again”, “apply pack X”.
- After polishing a deck whose brand or layout recipes are worth reusing.
- Before inventing a new brand from scratch when a pack already covers the need.
Prefer web-slides built-in / inspiration themes (midnight, aurora, paper, tech-dark, bento-minimal, navy-pitch) for generic looks. Use this library for user-specific or named packs (project brand, title-hero recipe, KPI strip convention).
Pack locations
| Location | Path | Who owns it |
| Repo packs | skills/style-library/styles/<pack-id>/ | Shared with the skill; commit when the pack is general |
| User packs | ~/.pi/agent/style-library/styles/<pack-id>/ | Personal; never commit secrets or uncleared photos |
| Override | $STYLE_LIBRARY_DIR/<pack-id>/ | Wins over both when set |
Search order for list / apply: $STYLE_LIBRARY_DIR → user dir → repo styles/. Same id in a higher-priority dir shadows a lower one.
Schema: references/pack-schema.md. Workflow detail: references/workflow.md. Examples: references/examples.md.
Commands
Run from the repo root (or any cwd; the script resolves the skill dir):
node skills/style-library/scripts/style-lib.mjs list
node skills/style-library/scripts/style-lib.mjs save --id <pack-id> --from <deck-dir> [--name "..."] [--theme brand|navy-pitch|…] [--patterns title-hero,kpi,timeline] [--dest repo|user]
node skills/style-library/scripts/style-lib.mjs apply --id <pack-id> --deck <deck-dir> [--patterns-only] [--theme-only] [--no-wire]
node skills/style-library/scripts/style-lib.mjs update --id <pack-id> --from <deck-dir> [--patterns title-hero,kpi]
node skills/style-library/scripts/style-lib.mjs show --id <pack-id>| Command | Does |
| list | Print pack id, name, tags, path |
| save | Snapshot brand.css / a theme block + selected pattern recipes into a new pack |
| apply | Write theme into brand.css, set theme: "brand", write content/style-pack.json, patch deck.spec.yaml (style_pack + per-slide pattern/layout/title-hero fields), wire matching slide TSX, emit src/slides/generated/from-pack.ts, and copy recipes to style-import/pack-<id>/. Use --no-wire to only copy files. |
| update | Refresh an existing pack from a deck (bumps updated, replaces files) |
| show | Dump pack.json + file list |
Agent workflow
- Study. Open the deck (or template slide) the user liked. Note theme (
brand/ preset) and which patterns matter (title hero, KPI strip, timeline, compare, …). - Save. Pick a kebab
pack-id. Runsavewith--from <deck>and--patterns …as needed. Prefer--dest userfor one-off client brands;--dest repoonly for packs meant to ship with this skill. - Confirm.
list/showand tell the user the id and what was captured (theme tokens? which patterns?). - Apply later. On a new deck,
apply --id <pack-id> --deck <dir>(wires theme + patterns into the build:brand.css,content/style-pack.json,deck.spec.yaml, matching slide TSX,src/slides/generated/from-pack.ts). Thencd <dir> && npm run spec && npm run check:tokens && npm run review. Adapt copy; do not paste third-party assets. - Update. If the user refined the look,
update --id <pack-id> --from <deck>.
Scope (what a pack holds)
- Theme: CSS custom properties under
[data-theme="brand"](colors, fonts, radii, layout-feel tokens). Source: decksrc/theme/brand.css, or a named block extracted fromtokens.css. - Patterns: Markdown recipes + optional
.css.snippet/.tsx.snippetfor layouts/components already in web-slides (title-hero,kpi,timeline,compare,bento, …). Patterns describe how to compose existing primitives — they do not fork the whole engine. - Not in scope: vendored PPTX, hotlinked stock photos, proprietary fonts, copying another vendor’s slide masters.
Pairing with web-slides
- Scaffold with web-slides (
new-deck.mjs), then apply a pack. - Or finish a deck, save a pack, then point web-slides brief at that pack next time.
- Style import (
style:url/style:images/style:svg) creates a one-offbrand.css. If the user likes it, save it here so the next deck does not re-scrape.
See web-slides references/style-import.md and docs/template-inspiration.md for one-shot brand capture; this skill is the reuse layer.
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

