design-style-installer — Claude Code skill: install a theme
The design-style-installer Claude Code skill installs a design theme and applies its tokens across a project. It runs for a visual restyle, updating component paint while keeping layout and content intact.
MIT 105 installs ★ 440 updated 2026-10-20
npx skills add OneWave-AI/claude-skills --skill design-style-installer -a claude-codeWhat design-style-installer does
The skill connects a selected theme to the project, replaces hardcoded style values in components with token references, then checks the build and key screens. Choose a theme from the Open Agent Stack collection, such as aurora-mesh or sand-terra, or use a local tokens.json file.
The integration depends on the project stack: Tailwind gets theme configuration, while other setups receive CSS variables. The skill checks text-to-background contrast and writes its findings to design-install-report.md, including any hardcoded values left behind. Component structure and content stay as they are; structural suggestions go in the report.
What it helps with
- wire design tokens into Tailwind or CSS
- replace hardcoded component styles with token references
- check text and background contrast after a theme change
- find style values that remain hardcoded
Example prompts for the agent
- Install the
aurora-meshtheme in this project. - Show me the available design themes.
- Find any style values that are still hardcoded.
How to install design-style-installer
1Skills CLI (Vercel)
npx skills add OneWave-AI/claude-skills --skill design-style-installer -a claude-code2Manually: put the files in place
~/.claude/skills/design-style-installer/SKILL.mdCopy the whole skill folder; for one project use .claude/skills/design-style-installer/
1Skills CLI (Vercel)
npx skills add OneWave-AI/claude-skills --skill design-style-installer -a codex2Manually: put the files in place
.agents/skills/design-style-installer/SKILL.mdFor all projects use ~/.agents/skills/
1Skills CLI (Vercel)
npx skills add OneWave-AI/claude-skills --skill design-style-installer -a cursor2Manually: put the files in place
.cursor/skills/design-style-installer/SKILL.mdCursor also reads .agents/skills/ and .claude/skills/
1GitHub CLI
gh skill install OneWave-AI/claude-skills design-style-installer2Manually: put the files in place
.github/skills/design-style-installer/SKILL.md1Skills CLI (Vercel)
npx skills add OneWave-AI/claude-skills --skill design-style-installer -a gemini-cli2Platform CLI
gemini skills install https://github.com/OneWave-AI/claude-skills --path design-style-installerManually: put the files in place
.devin/skills/design-style-installer/SKILL.mdThe legacy .windsurf/skills/ path still works
Skills CLI (Vercel)
npx skills add OneWave-AI/claude-skills --skill design-style-installer -a opencodeClaude.ai
Zip the folder and upload it in Settings → Capabilities → Skills
Step by step, with commands for each platform: How to install skills in Claude Code: five ways
Questions about design-style-installer
How do I install design-style-installer in Claude Code?
Run npx skills add OneWave-AI/claude-skills --skill design-style-installer -a claude-code. The skill file is at ~/.claude/skills/design-style-installer/SKILL.md.
What does design-style-installer do?
It connects a design theme to a project, replaces hardcoded component styles with token references, and checks the build and contrast. It saves findings in design-install-report.md.
Which themes can design-style-installer install?
The collection includes aurora-mesh, cirrus, liquid-glass, mono-brutalist, neo-terminal, sand-terra, and tidal. A local tokens.json can also provide the theme.
Source text
SKILL.md · MIT
--- name: design-style-installer description: Install a complete design-token theme into any project in one pass -- pulls a style from the Open Agent Stack design-styles collection (aurora-mesh, cirrus, liquid-glass, mono-brutalist, neo-terminal, sand-terra, tidal) or a local tokens.json, wires it into Tailwind/CSS, and repaints existing components to match. tools: Read, Glob, Grep, Write, Edit, Bash, WebFetch model: inherit --- # Design Style Installer Apply a full design system to a project the way a brand refresh actually works: tokens first, wiring second, components last, and nothing hardcoded that the tokens already define. Sources: the seven production themes in [Open Agent Stack `design-styles/`](https://github.com/OneWave-AI/open-agent-stack/tree/main/design-styles) -- each ships `tokens.json` (W3C design-tokens), `theme.css`, `tailwind.tokens.js`, and a WCAG contrast worksheet -- or any local W3C-format tokens file. ## Workflow 1. **Pick the style.** If the user named one, fetch it from the open-agent-stack repo (or read the local clone). If not, show the seven options with their one-line personalities -- aurora-mesh (soft futuristic dark, gradient mesh), cirrus (light cloud/sky, frosted), liquid-glass (translucent layered), mono-brutalist (stark, type-led), neo-terminal (CRT green-on-black), sand-terra (warm editorial neutrals), tidal (deep ocean blues) -- and ask which fits the product. 2. **Read the project.** Detect the stack (Tailwind version, CSS modules, styled-components, plain CSS) and inventory the current styling surface: where colors, fonts, radii, and shadows are defined today, and how many components hardcode values outside that. 3. **Install the tokens.** Wire the theme by stack: Tailwind -- merge `tailwind.tokens.js` into `theme.extend` (v4: emit `@theme` CSS variables); otherwise -- add `theme.css` custom properties at `:root`/`[data-theme]`. Load the theme's fonts properly (next/font or preconnected `<link>`), never a blocking import chain. 4. **Repaint.** Replace hardcoded values in components with token references, mapping by role, not by nearest hex: old primary -> new accent, old page background -> `bg.base`, old card -> `surface`. Where the old design had roles the theme lacks (a third accent, a warning tint), derive them from the theme's palette logic and document the additions in the tokens file -- do not freelance new colors. 5. **Verify.** Run the build, then check the money paths render correctly: nav, hero, buttons in all states, forms, cards. Confirm text/background pairs still meet the contrast worksheet's AA levels after any derivations. Output `design-install-report.md`: tokens installed, files touched, hardcoded values remaining (with paths), and derived tokens added. ## Rules - Tokens are the only source of truth after installation. A repaint that leaves hex codes scattered in components has not finished. - Map by semantic role, never by visual similarity -- the old light-gray border and the old light-gray disabled-text are different tokens even if they were the same hex. - Never mix themes. If the user wants aurora-mesh cards on a sand-terra page, that is a custom theme -- fork the tokens file and name it honestly. - Preserve layout and content exactly: this skill changes paint, not structure. Structural itches go in the report as suggestions. - Respect the theme's motion tokens too -- durations and easings are part of the style, not decoration to skip. - Keep the theme's accessibility guarantees: any color you derive gets contrast-checked before it ships. ## Quick Commands - "Install [style] into this project" -- full workflow - "Show me the styles" -- step 1 gallery with personalities - "Just the tokens, no repaint" -- steps 1-3 - "What's still hardcoded?" -- the drift audit from step 5
© OneWave-AI · MIT · OneWave-AI/claude-skills