Design
Ohh-889/skyroc
Comprehensive design skill: brand identity, design tokens, UI styling, logo generation (55 styles, Gemini AI), corporate identity program (50 deliverables, CIP mockups), HTML presentations…
How to write and maintain DESIGN.md as the visual specification layer for Cavekit projects.
$ npx skills add JuliusBrussee/caveman-code --skill cavekit-design-system -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install JuliusBrussee/caveman-code cavekit-design-system --agent claude-codeProject scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).
$ git clone --depth 1 https://github.com/JuliusBrussee/caveman-code.git skills-src && mkdir -p .claude/skills && cp -r skills-src/packages/coding-agent/skills/cavekit-design-system .claude/skills/cavekit-design-system && rm -rf skills-srcUse ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.
Claude Code skills documentation · loads skills from .claude/skills/
Install the "cavekit-design-system" agent skill from https://github.com/JuliusBrussee/caveman-code/tree/main/packages/coding-agent/skills/cavekit-design-system into .claude/skills/cavekit-design-system/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "cavekit-design-system", then confirm the skill loads.Claude Code copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$skill-installer install https://github.com/JuliusBrussee/caveman-code/tree/main/packages/coding-agent/skills/cavekit-design-systemType this inside Codex. $skill-installer <name> installs a curated skill from openai/skills. The installer writes to $CODEX_HOME/skills (default ~/.codex/skills). Restart Codex if the skill does not show up.
$ npx skills add JuliusBrussee/caveman-code --skill cavekit-design-system -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install JuliusBrussee/caveman-code cavekit-design-system --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/JuliusBrussee/caveman-code.git skills-src && mkdir -p .agents/skills && cp -r skills-src/packages/coding-agent/skills/cavekit-design-system .agents/skills/cavekit-design-system && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "cavekit-design-system" agent skill from https://github.com/JuliusBrussee/caveman-code/tree/main/packages/coding-agent/skills/cavekit-design-system into .agents/skills/cavekit-design-system/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "cavekit-design-system", then confirm the skill loads.Codex copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add JuliusBrussee/caveman-code --skill cavekit-design-system -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install JuliusBrussee/caveman-code cavekit-design-system --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/JuliusBrussee/caveman-code.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/packages/coding-agent/skills/cavekit-design-system .cursor/skills/cavekit-design-system && rm -rf skills-srcUse ~/.cursor/skills/ instead of .cursor/skills for a personal install.
Cursor skills documentation · loads skills from .cursor/skills/, .agents/skills/, .claude/skills/, .codex/skills/
Install the "cavekit-design-system" agent skill from https://github.com/JuliusBrussee/caveman-code/tree/main/packages/coding-agent/skills/cavekit-design-system into .cursor/skills/cavekit-design-system/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "cavekit-design-system", then confirm the skill loads.Cursor copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gemini skills install https://github.com/JuliusBrussee/caveman-code.git --path packages/coding-agent/skills/cavekit-design-system--scope user (default) or --scope workspace; --path is the subfolder of the repo that holds the skill; --consent skips the security confirmation prompt.
$ npx skills add JuliusBrussee/caveman-code --skill cavekit-design-system -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install JuliusBrussee/caveman-code cavekit-design-system --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/JuliusBrussee/caveman-code.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/packages/coding-agent/skills/cavekit-design-system .gemini/skills/cavekit-design-system && rm -rf skills-srcUse ~/.gemini/skills/ instead of .gemini/skills for a personal install, then run /skills reload.
Gemini CLI skills documentation · loads skills from .gemini/skills/, .agents/skills/
Install the "cavekit-design-system" agent skill from https://github.com/JuliusBrussee/caveman-code/tree/main/packages/coding-agent/skills/cavekit-design-system into .gemini/skills/cavekit-design-system/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "cavekit-design-system", then confirm the skill loads.Gemini CLI copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gh skill install JuliusBrussee/caveman-code cavekit-design-systemInstalls for Copilot at project scope by default; add --scope user for a personal install. Preview a skill first with gh skill preview. Needs GitHub CLI 2.90.0 or later (public preview).
$ npx skills add JuliusBrussee/caveman-code --skill cavekit-design-system -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/JuliusBrussee/caveman-code.git skills-src && mkdir -p .github/skills && cp -r skills-src/packages/coding-agent/skills/cavekit-design-system .github/skills/cavekit-design-system && rm -rf skills-srcUse ~/.copilot/skills/ instead of .github/skills for a personal install. Commit .github/skills so cloud agent and code review can use it.
GitHub Copilot skills documentation · loads skills from .github/skills/, .claude/skills/, .agents/skills/
Install the "cavekit-design-system" agent skill from https://github.com/JuliusBrussee/caveman-code/tree/main/packages/coding-agent/skills/cavekit-design-system into .github/skills/cavekit-design-system/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "cavekit-design-system", then confirm the skill loads.GitHub Copilot copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add JuliusBrussee/caveman-code --skill cavekit-design-system -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install JuliusBrussee/caveman-code cavekit-design-system --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/JuliusBrussee/caveman-code.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/packages/coding-agent/skills/cavekit-design-system .opencode/skills/cavekit-design-system && rm -rf skills-srcUse ~/.config/opencode/skills/ instead of .opencode/skills for a personal install.
OpenCode skills documentation · loads skills from .opencode/skills/, .claude/skills/, .agents/skills/
Install the "cavekit-design-system" agent skill from https://github.com/JuliusBrussee/caveman-code/tree/main/packages/coding-agent/skills/cavekit-design-system into .opencode/skills/cavekit-design-system/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "cavekit-design-system", then confirm the skill loads.OpenCode copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
cavekit-design-systemHow to write and maintain DESIGN.md as the visual specification layer for Cavekit projects.
Cavekit Design System is an agent skill from JuliusBrussee/caveman-code. How to write and maintain DESIGN.md as the visual specification layer for Cavekit projects. Nine-section format, design tokens, accessibility, integration with kits/plans. Use when defining or revising visual identity, importing a third-party design system, or auditing UI code against design tokens.
Its SKILL.md is about 4.5k tokens, which your agent loads only when the skill is triggered. It is a single SKILL.md file with no bundled scripts.
It sits in Frontend & Design, covering Design tokens, Design systems and Logo and visual identity. The repository describes itself as: Frozen — terminal coding agent measured at 1.93× fewer tokens than Codex CLI. Still works; active development moved to JuliusBrussee/caveman (caveman wrap). The licence is MIT.
4 steps, taken from the first numbered list in SKILL.md.
Read from SKILL.md and the folder at commit 3a21be1. It shows what the files ask for, not the result of running them.
Pre-approves these tools, so the agent can use them without asking each time:
readgrepeditFrom allowed-tools in the SKILL.md frontmatter.
No scripts in the folder and no shell commands in SKILL.md (its code samples are markdown and css).
From the folder's file list and the shell code blocks in SKILL.md.
Links to these hosts (documentation or services it may open):
stitch.withgoogle.comgithub.comFrom URLs in SKILL.md, links to its own repository left out.
Names no API keys, tokens, secrets or passwords.
From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.
Cavekit Design System loads about 4.5k tokens when it runs. Until then it costs about 81 tokens; SKILL.md has 1,232 words of instructions outside code blocks.
Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.
The automated check found no risky patterns in SKILL.md.
Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.
The full file from JuliusBrussee/caveman-code at commit 3a21be1, republished under its MIT licence (© JuliusBrussee). 1,232 words, ~4,484 tokens.
.claude/skills/cavekit-design-system/SKILL.md (or your agent's skills folder).DESIGN.md is the visual equivalent of kits. It defines the project's visual language — colors, typography, spacing, components, responsive behavior — in a format AI agents can read and apply consistently. It is a parallel constraint layer that all Hunt phases consult.
| Document | Defines | Audience |
|---|---|---|
| CLAUDE.md | How to build the project | Coding agents |
| Kits | What must be true (behavior) | All agents |
| DESIGN.md | What it looks like (visual) | UI-building agents |
| Plans | How to build it (tasks) | Builder agents |
Without DESIGN.md, visual decisions scatter across kits, plans, and code:
DESIGN.md centralizes these decisions. Every agent reads it before writing UI code.
DESIGN.md follows the Google Stitch format — 9 sections that together define a complete visual language. Every DESIGN.md must contain all 9 sections.
The design philosophy, mood, and overall aesthetic. Use evocative, specific language — not generic terms like "clean and modern."
## 1. Visual Theme & Atmosphere
This is a warm editorial experience built on natural materials. Think: a well-curated
bookshop with soft overhead lighting and carefully chosen display shelves. The density
is low — generous whitespace signals confidence and clarity. Every element earns its
place; nothing decorative exists without functional purpose.
**Key attributes:** Warm, unhurried, editorial, confident
**Density:** Low — generous whitespace, single-column focus
**Personality:** Thoughtful librarian, not flashy storefrontWhat good looks like: A new designer reading this section could sketch a rough layout without seeing any other section.
Anti-pattern: "Clean, modern, and professional" — this describes nothing specific.
Every color needs three things: a semantic name, a hex value, and a functional role.
## 2. Color Palette & Roles
### Primary
| Name | Hex | Role |
|------|-----|------|
| Terracotta Brand | #c96442 | Primary CTA, active states, brand anchors |
| Terracotta Hover | #b85838 | Hover/pressed state for primary actions |
### Neutral
| Name | Hex | Role |
|------|-----|------|
| Near Black | #141413 | Primary text, headings |
| Olive Gray | #5e5d59 | Secondary text, captions |
| Parchment | #f5f4ed | Page background, default canvas |
| Ivory White | #ffffff | Card surfaces, overlays |
### Semantic
| Name | Hex | Role |
|------|-----|------|
| Success Green | #2d7d46 | Confirmation, success states |
| Warning Amber | #c27217 | Warnings, attention needed |
| Error Red | #c24132 | Errors, destructive actions |
| Info Blue | #3b6fb5 | Informational states, links |
### Dark Mode (if applicable)
| Light Name | Dark Equivalent | Hex |
|------------|----------------|-----|
| Parchment | Deep Charcoal | #1a1a1a |
| Near Black | Off White | #e8e8e8 |Rules:
Complete type hierarchy with specific values — no "roughly 16px" or "medium weight."
## 3. Typography Rules
### Font Stack
- **Display/Heading:** "Anthropic Serif", Georgia, "Times New Roman", serif
- **Body:** "Anthropic Sans", -apple-system, BlinkMacSystemFont, sans-serif
- **Code:** "Anthropic Mono", "SF Mono", "Fira Code", monospace
### Type Scale
| Level | Size | Weight | Line Height | Letter Spacing | Font |
|-------|------|--------|-------------|----------------|------|
| H1 | 48px / 3rem | 500 | 1.10 | -0.02em | Serif |
| H2 | 36px / 2.25rem | 500 | 1.15 | -0.01em | Serif |
| H3 | 24px / 1.5rem | 500 | 1.25 | 0 | Serif |
| H4 | 20px / 1.25rem | 600 | 1.30 | 0 | Sans |
| Body | 16px / 1rem | 400 | 1.60 | 0 | Sans |
| Small | 14px / 0.875rem | 400 | 1.50 | 0.01em | Sans |
| Caption | 12px / 0.75rem | 500 | 1.40 | 0.02em | Sans |
### Principles
- Headings use serif for warmth and authority
- Body text uses sans-serif for readability at small sizes
- Maximum line length: 65ch for body text
- Minimum font size: 14px (never go below)Rules:
Concrete styling for common components including interaction states.
## 4. Component Stylings
### Buttons
**Primary:**
- Background: Terracotta Brand (#c96442)
- Text: Ivory White (#ffffff), 16px Sans, weight 500
- Padding: 12px 24px
- Border radius: 8px
- Hover: Terracotta Hover (#b85838), translateY(-1px), shadow-sm
- Active: translateY(0), shadow-none
- Disabled: opacity 0.5, cursor not-allowed
- Transition: all 150ms ease-out
**Secondary:**
- Background: transparent
- Border: 1px solid Olive Gray (#5e5d59)
- Text: Near Black (#141413)
- Hover: background Parchment (#f5f4ed)
### Cards
- Background: Ivory White (#ffffff)
- Border: 1px solid rgba(0,0,0,0.06)
- Border radius: 12px
- Padding: 24px
- Shadow: 0 1px 3px rgba(0,0,0,0.04)
- Hover: shadow 0 4px 12px rgba(0,0,0,0.08), translateY(-2px)
### Inputs
- Border: 1px solid #d0d0d0
- Border radius: 8px
- Padding: 10px 14px
- Focus: border Terracotta Brand, ring 2px rgba(201,100,66,0.2)
- Error: border Error Red, ring 2px rgba(194,65,50,0.2)
### Navigation
...Rules:
Spacing system, grid, containers, and whitespace philosophy.
## 5. Layout Principles
### Spacing Scale (base: 4px)
| Token | Value | Usage |
|-------|-------|-------|
| space-1 | 4px | Tight gaps, icon margins |
| space-2 | 8px | Related element spacing |
| space-3 | 12px | Component internal padding |
| space-4 | 16px | Standard gap between elements |
| space-6 | 24px | Section padding, card padding |
| space-8 | 32px | Between major sections |
| space-12 | 48px | Page-level vertical rhythm |
| space-16 | 64px | Hero/banner spacing |
### Grid
- Max content width: 1200px
- Column count: 12
- Gutter: 24px (space-6)
- Margin: 16px mobile, 24px tablet, auto desktop
### Border Radius Scale
| Token | Value | Usage |
|-------|-------|-------|
| radius-sm | 4px | Badges, tags |
| radius-md | 8px | Buttons, inputs |
| radius-lg | 12px | Cards, panels |
| radius-xl | 16px | Modals, dialogs |
| radius-full | 9999px | Avatars, pills |Shadow system and visual layering.
## 6. Depth & Elevation
### Shadow Scale
| Level | Value | Usage |
|-------|-------|-------|
| shadow-none | none | Flat elements |
| shadow-sm | 0 1px 2px rgba(0,0,0,0.04) | Subtle lift (cards at rest) |
| shadow-md | 0 4px 12px rgba(0,0,0,0.08) | Hover states, active cards |
| shadow-lg | 0 8px 24px rgba(0,0,0,0.12) | Dropdowns, popovers |
| shadow-xl | 0 16px 48px rgba(0,0,0,0.16) | Modals, dialogs |
### Surface Hierarchy
1. **Base** — page background (Parchment)
2. **Raised** — cards, panels (Ivory White + shadow-sm)
3. **Floating** — dropdowns, tooltips (Ivory White + shadow-lg)
4. **Overlay** — modals, dialogs (Ivory White + shadow-xl + scrim)Concrete examples with code — not just prose rules.
## 7. Do's and Don'ts
### DO: Use semantic color names
```css
/* Good */
.button-primary { background: var(--color-terracotta-brand); }/* Bad */
.button-primary { background: #c96442; }/* Good — uses scale */
.card { padding: var(--space-6); margin-bottom: var(--space-8); }/* Bad — 19px is not on the scale */
.card { padding: 19px; margin-bottom: 37px; }
### Section 8: Responsive Behavior
Breakpoints, mobile patterns, and adaptation rules.
```markdown
## 8. Responsive Behavior
### Breakpoints
| Name | Width | Target |
|------|-------|--------|
| mobile | < 640px | Phones |
| tablet | 640–1024px | Tablets, small laptops |
| desktop | > 1024px | Laptops, monitors |
### Touch Targets
- Minimum interactive element size: 44x44px
- Minimum spacing between targets: 8px
### Mobile Adaptations
- Navigation collapses to hamburger menu below 640px
- Cards stack single-column below 640px
- Font sizes: H1 reduces to 32px on mobile, H2 to 28px
- Side padding: 16px on mobile, 24px tablet, auto-center desktop
### Behavior Patterns
- Horizontal scrolling: never (use stacking or truncation)
- Images: responsive with srcset, max-width: 100%
- Tables: horizontal scroll wrapper below tablet breakpointHow AI agents should use this document when generating UI.
## 9. Agent Prompt Guide
### Quick Reference
- Primary CTA color: Terracotta Brand (#c96442)
- Background: Parchment (#f5f4ed)
- Heading font: Serif, weight 500
- Body font: Sans, weight 400
- Standard spacing: 24px (space-6)
- Card radius: 12px (radius-lg)
### How to Use This Document
1. Before writing any UI code, read the full DESIGN.md
2. Reference specific section names when implementing: "Following Section 4: Buttons"
3. Use design token names in CSS (var(--color-terracotta-brand)), not raw hex values
4. Check Section 7 (Do's and Don'ts) before submitting
5. If a component is not covered, create it following existing patterns and flag for DESIGN.md update
### Example Component Prompt
"Create a hero section on Parchment (#f5f4ed) with a headline at H1 scale
(48px Serif weight 500, line-height 1.10). Use Near Black (#141413) text.
Add a subtitle in Olive Gray (#5e5d59) at Body scale (16px Sans, line-height 1.60).
Place a Terracotta Brand (#c96442) primary button with Ivory text, radius-md (8px)."
### Iteration Guide
- Change one component at a time
- Reference specific color names and token values
- Describe the component's state (default, hover, active, disabled)
- Specify responsive behavior for the componentTokens are the bridge between DESIGN.md and code. Consistent naming ensures agents can translate design specs into CSS/Tailwind variables.
--{category}-{name}[-{modifier}]| Category | Examples |
|---|---|
color- | --color-terracotta-brand, --color-near-black, --color-success-green |
space- | --space-1, --space-4, --space-8 |
text- | --text-h1, --text-body, --text-caption |
radius- | --radius-sm, --radius-md, --radius-lg |
shadow- | --shadow-sm, --shadow-md, --shadow-lg |
font- | --font-serif, --font-sans, --font-mono |
DESIGN.md tokens map directly to CSS custom properties:
:root {
--color-terracotta-brand: #c96442;
--space-6: 24px;
--radius-lg: 12px;
--shadow-sm: 0 1px 2px rgba(0,0,0,0.04);
}When using Tailwind, DESIGN.md tokens map to tailwind.config.js extensions. The builder agent should configure this once and reference throughout.
When DESIGN.md exists and kits contain UI requirements, acceptance criteria should reference design tokens by section and name. This creates a traceable chain:
DESIGN.md → Cavekit acceptance criterion → Plan task → Implementation| In Cavekit Acceptance Criteria | Design Reference |
|---|---|
| "CTA button uses primary brand styling" | DESIGN.md Section 4: Buttons, primary variant |
| "Headings follow the type hierarchy" | DESIGN.md Section 3: Type Scale |
| "Cards have subtle resting elevation" | DESIGN.md Section 6: shadow-sm |
| "Layout uses the standard grid" | DESIGN.md Section 5: Grid |
| "Colors adapt for dark mode" | DESIGN.md Section 2: Dark Mode mapping |
Do NOT duplicate DESIGN.md content into kits. Reference by section/token name only. If a color changes in DESIGN.md, kits should not need updating.
If a cavekit needs a visual pattern not in DESIGN.md, the acceptance criterion should note this:
- [ ] Component uses a card-like container [DESIGN.md: pattern not yet defined — flag for design update]This tells the inspect phase to check whether DESIGN.md needs a new pattern.
When the architect generates task descriptions for UI work, each task should include:
**Design Reference:** DESIGN.md Section {N} — {section name}This tells the task-builder which DESIGN.md sections to read before implementing.
Task-builder agents follow this protocol for UI work:
When visual fixes are made manually (outside the Hunt loop), /ck:revise traces them back to DESIGN.md:
| Fix Type | DESIGN.md Action |
|---|---|
| Color change that should apply globally | Update DESIGN.md Section 2 with corrected value |
| New component pattern not in DESIGN.md | Add to DESIGN.md Section 4 |
| Spacing adjustment revealing wrong scale | Update DESIGN.md Section 5 scale |
| Typography fix | Update DESIGN.md Section 3 type scale |
| Responsive behavior change | Update DESIGN.md Section 8 |
context/designs/design-changelog.mdThe awesome-design-md repository contains 54+ curated design systems extracted from real products. These serve as starting points.
vercel, claude, stripe, github, linear, etc.The imported DESIGN.md becomes the project's own. Future updates are made directly — the import is a seed, not a dependency.
Every value in DESIGN.md must be concrete and unambiguous:
| Too Vague | Specific Enough |
|---|---|
| "a warm blue" | #3b6fb5 (Info Blue) |
| "medium spacing" | 24px (space-6) |
| "slightly rounded" | 8px (radius-md) |
| "subtle shadow" | 0 1px 2px rgba(0,0,0,0.04) (shadow-sm) |
| "large heading" | 48px / 3rem, weight 500, line-height 1.10 |
© JuliusBrussee, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file
Just SKILL.md in packages/coding-agent/skills/cavekit-design-system of JuliusBrussee/caveman-code.
Open the folder on GitHubat commit 3a21be1
Cavekit Design System next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.
| Skill | Stars | Used in | Tokens | Auto-check | Licence | Repo updated |
|---|---|---|---|---|---|---|
| Cavekit Design System this skillJuliusBrussee/caveman-code | 942 | — | ~4.5k | Automated safety check: Pass | MIT | |
| DesignOhh-889/skyroc | 795 | 9 repos | ~3.1k | Automated safety check: Pass | MIT | |
| Replica DesignJakeschincariol/replica-skill | 1.2k | — | ~994 | Automated safety check: Pass | MIT | |
| Shadcn Tailwind UILiarMTTT/TavernWeave | 153 | — | ~1.7k | Automated safety check: Pass | Custom licence | |
| Brand DesignEliasOulkadi/shokunin | 114 | — | ~3k | Automated safety check: Pass | MIT | |
| Figma Design System Builderwarpdotdev/warp | 65k | 2 repos | ~4.4k | Automated safety check: Pass | AGPL-3.0 |
Ohh-889/skyroc
Comprehensive design skill: brand identity, design tokens, UI styling, logo generation (55 styles, Gemini AI), corporate identity program (50 deliverables, CIP mockups), HTML presentations…
Jakeschincariol/replica-skill
Rebuilds an app's design system for a clone: colour roles, type scale, spacing, radius, shadows and every component with its states, as design tokens plus component specs, with original assets…
LiarMTTT/TavernWeave
Build, restyle, or review accessible React interfaces that use shadcn/ui, Radix UI primitives, and Tailwind CSS.
EliasOulkadi/shokunin
Generate brand guidelines, design systems with design tokens (W3C format), creative direction (SCAMPER, Design Thinking, TRIZ), and design briefs with scope and success criteria.
warpdotdev/warp
Builds or updates a design system in Figma from a codebase in ordered phases: discovery, variables and tokens, components, theming and documentation, with checkpoints.
warpdotdev/warp
Required groundwork before any use_figma call: the rules and reference files for running JavaScript in a Figma file through the Plugin API without common failures.
JuliusBrussee/caveman-code
Cavekit specification-driven development methodology — the Hunt lifecycle (Draft → Architect → Build → Inspect → Monitor) and how to apply it.
JuliusBrussee/caveman-code
Trace bugs and manual fixes back to kits and prompts; fix at the source so the iteration loop can reproduce the fix autonomously.
JuliusBrussee/caveman-code
Validation-first design for Cavekit — every kit requirement must be automatically verifiable.
JuliusBrussee/caveman-code
Rewrites a memory file such as CLAUDE.md or a todo list in terse caveman-style text to cut input tokens, saving a readable backup outside the project tree.
JuliusBrussee/caveman-code
Scaffold a complete cave plugin bundle — generates .cave-plugin/plugin.json manifest and the standard directory structure (commands/, skills/, agents/, themes/, hooks/).
Categories
How to write and maintain DESIGN.md as the visual specification layer for Cavekit projects. Cavekit Design System is an agent skill from JuliusBrussee/caveman-code.md as the visual specification layer for Cavekit projects.
Cavekit Design System fits situations like: revising visual identity; importing a third-party design system; auditing UI code against design tokens.
Run `npx skills add JuliusBrussee/caveman-code --skill cavekit-design-system -a claude-code`. Or copy the skill folder (packages/coding-agent/skills/cavekit-design-system in JuliusBrussee/caveman-code) into .claude/skills/cavekit-design-system in your project. Claude Code loads it when a task matches its description.
Run `npx skills add JuliusBrussee/caveman-code --skill cavekit-design-system -a codex`. Or copy the skill folder (packages/coding-agent/skills/cavekit-design-system in JuliusBrussee/caveman-code) into .agents/skills/cavekit-design-system in your project. Codex loads it when a task matches its description.
Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add JuliusBrussee/caveman-code --skill cavekit-design-system -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/cavekit-design-system, .gemini/skills/cavekit-design-system, .github/skills/cavekit-design-system and .opencode/skills/cavekit-design-system in your project.
SKILL.md names no scripts, command-line tools or credentials: Cavekit Design System is instructions for the agent only. Its frontmatter pre-approves these tools: read, grep, edit.
SKILL.md names 2 domains. As links in the text: stitch.withgoogle.com and github.com. This is read from the text; nothing was executed.
Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.
Cavekit Design System is published under the MIT licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.
About 4.5k tokens (SKILL.md is roughly 18k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.
Skills that share tags, products or a category with Cavekit Design System: Design (Ohh-889/skyroc, 795 stars), Replica Design (Jakeschincariol/replica-skill, 1.2k stars), Shadcn Tailwind UI (LiarMTTT/TavernWeave, 153 stars) and Brand Design (EliasOulkadi/shokunin, 114 stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
JuliusBrussee (a GitHub user) maintains it in JuliusBrussee/caveman-code, which has 942 GitHub stars. The repository holds 6 skills in this directory. The repository was last updated on August 14, 2026.
Source: JuliusBrussee/caveman-code on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.