UI Styling
Ohh-889/skyroc
Create beautiful, accessible user interfaces with shadcn/ui components (built on Radix UI + Tailwind), Tailwind CSS utility-first styling, and canvas-based visual designs.
Guides UI work on OpenClaw apps so it uses the shared Carapace package: semantic design tokens, theme foundations, shared CSS classes and the product's existing local components.
Install OpenClaw Carapace UI
$ npx skills add openclaw/clawhub --skill openclaw-carapace -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install openclaw/clawhub openclaw-carapace --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/openclaw/clawhub.git skills-src && mkdir -p .claude/skills && cp -r skills-src/.agents/skills/openclaw-carapace .claude/skills/openclaw-carapace && 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 "openclaw-carapace" agent skill from https://github.com/openclaw/clawhub/tree/main/.agents/skills/openclaw-carapace into .claude/skills/openclaw-carapace/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "openclaw-carapace", 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/openclaw/clawhub/tree/main/.agents/skills/openclaw-carapaceType 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 openclaw/clawhub --skill openclaw-carapace -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install openclaw/clawhub openclaw-carapace --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/openclaw/clawhub.git skills-src && mkdir -p .agents/skills && cp -r skills-src/.agents/skills/openclaw-carapace .agents/skills/openclaw-carapace && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "openclaw-carapace" agent skill from https://github.com/openclaw/clawhub/tree/main/.agents/skills/openclaw-carapace into .agents/skills/openclaw-carapace/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "openclaw-carapace", 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 openclaw/clawhub --skill openclaw-carapace -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install openclaw/clawhub openclaw-carapace --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/openclaw/clawhub.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/.agents/skills/openclaw-carapace .cursor/skills/openclaw-carapace && 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 "openclaw-carapace" agent skill from https://github.com/openclaw/clawhub/tree/main/.agents/skills/openclaw-carapace into .cursor/skills/openclaw-carapace/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "openclaw-carapace", 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/openclaw/clawhub.git --path .agents/skills/openclaw-carapace--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 openclaw/clawhub --skill openclaw-carapace -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install openclaw/clawhub openclaw-carapace --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/openclaw/clawhub.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/.agents/skills/openclaw-carapace .gemini/skills/openclaw-carapace && 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 "openclaw-carapace" agent skill from https://github.com/openclaw/clawhub/tree/main/.agents/skills/openclaw-carapace into .gemini/skills/openclaw-carapace/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "openclaw-carapace", 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 openclaw/clawhub openclaw-carapaceInstalls 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 openclaw/clawhub --skill openclaw-carapace -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/openclaw/clawhub.git skills-src && mkdir -p .github/skills && cp -r skills-src/.agents/skills/openclaw-carapace .github/skills/openclaw-carapace && 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 "openclaw-carapace" agent skill from https://github.com/openclaw/clawhub/tree/main/.agents/skills/openclaw-carapace into .github/skills/openclaw-carapace/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "openclaw-carapace", 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 openclaw/clawhub --skill openclaw-carapace -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install openclaw/clawhub openclaw-carapace --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/openclaw/clawhub.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/.agents/skills/openclaw-carapace .opencode/skills/openclaw-carapace && 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 "openclaw-carapace" agent skill from https://github.com/openclaw/clawhub/tree/main/.agents/skills/openclaw-carapace into .opencode/skills/openclaw-carapace/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "openclaw-carapace", 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.
Facts
- Skill name
openclaw-carapace- GitHub stars
- 9.5k
- Token cost
- ~699 tokens
- SKILL.md length
- 309 words
- Files
- 6 (incl. references)
- Skills in repo
- 55
- Repo updated
- First seen
- Licence
- MIT
At a glance
Guides UI work on OpenClaw apps so it uses the shared Carapace package: semantic design tokens, theme foundations, shared CSS classes and the product's existing local components.
- Works in 9 steps: Read tokens.md before choosing colors,… → Read consumer-adapters.md for the… → Read application-surfaces.md when… → …
- Building a new settings screen or pane in an OpenClaw application
- SKILL.md covers Workflow, Interface Rules and Ownership
- Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md
What it does
This skill sends the agent to the shared Carapace package for colors, spacing, type, radii and shadows, while routes, data, behavior and layout composition stay local to each product. Reference files cover the token set, adapters for each consuming framework, application surfaces such as shells, panes and settings screens, terminal interfaces, and surfaces rendered inside a host frame such as an MCP app.
The workflow asks the agent to inspect the product's existing shared primitives before building a component, to use semantic tokens for UI intent and palette primitives only for documented exceptions, and to check the affected routes with existing tests and real browser screenshots. The interface rules favor one primary action per decision area, accessible names on icon-only buttons, square corners through radius tokens, stable sizes for repeated elements and dense, scannable layouts for operational screens. The excerpt is cut off in the ownership section, which says framework-neutral visual code belongs in the shared repository.
When your agent uses it
- Building a new settings screen or pane in an OpenClaw application
- Replacing hard-coded colors and spacing with semantic design tokens
- Adding dark or light theme support to an existing OpenClaw interface
- Designing or auditing a terminal UI that should follow the shared visual language
Example prompts
- “Build a settings page for the gateway config using the Carapace tokens and our existing form primitives.”
- “Swap the raw hex colors in this component for semantic tokens and check it in both themes.”
- “Review our terminal UI against the Carapace terminal guidance and list what to change.”
Requirements
- A consuming OpenClaw project that installs the Carapace package
Workflow steps
9 steps, taken from the first numbered list in SKILL.md.
- Read tokens.md before choosing colors, spacing, type, radii, or shadows.
- Read consumer-adapters.md for the current framework.
- Read application-surfaces.md when working on shells, panes, settings, or operational screens.
- Read terminal-ui.md when designing or auditing a terminal interface.
- Read embedded-surfaces.md when the surface renders inside a host frame, such as an MCP app.
- Inspect the consumer's existing shared primitives before creating a component.
- Use semantic tokens for UI intent; use palette primitives only for documented exceptions.
- Keep application behavior, routes, and information architecture unchanged unless the task says otherwise.
- Validate the affected routes with existing tests and real browser screenshots.
What it can do on your machine
Read from SKILL.md and the folder at commit d044664. It shows what the files ask for, not the result of running them.
Tool permissions
Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.
From allowed-tools in the SKILL.md frontmatter.
Runs code
No scripts in the folder and no shell commands in SKILL.md.
From the folder's file list and the shell code blocks in SKILL.md.
Network
No URLs in SKILL.md.
From URLs in SKILL.md, links to its own repository left out.
Credentials
Names no API keys, tokens, secrets or passwords.
From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.
Context cost
OpenClaw Carapace UI loads about 699 tokens when it runs, and up to ~10k if it reads all its reference files. Until then it costs about 66 tokens; SKILL.md has 309 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.
Safety
Auto-check passed
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.
SKILL.md
The full file from openclaw/clawhub at commit d044664, republished under its MIT licence (© openclaw). 309 words, ~699 tokens.
Download SKILL.mdSave it as
.claude/skills/openclaw-carapace/SKILL.md (or your agent's skills folder). This skill also uses 5 other files; get the full folder from GitHub.- name
- openclaw-carapace
- description
- Build or modify OpenClaw application UI using canonical semantic tokens, themes, shared CSS foundations, consumer adapters, and established local primitives. Use for product interfaces, component styling, theme work, or design-token integration.
Carapace
Use the shared package for foundations and framework-neutral visual primitives. Keep consumer-specific behavior, data, routes, and layout composition local.
Workflow
- Read tokens.md before choosing colors, spacing, type, radii, or shadows.
- Read consumer-adapters.md for the current framework.
- Read application-surfaces.md when working on shells, panes, settings, or operational screens.
- Read terminal-ui.md when designing or auditing a terminal interface.
- Read embedded-surfaces.md when the surface renders inside a host frame, such as an MCP app.
- Inspect the consumer's existing shared primitives before creating a component.
- Use semantic tokens for UI intent; use palette primitives only for documented exceptions.
- Keep application behavior, routes, and information architecture unchanged unless the task says otherwise.
- Validate the affected routes with existing tests and real browser screenshots.
Interface Rules
- Import the complete CSS contract or its focused exported entry points.
- Compose shared classes from
components.cssbefore adding a one-off visual implementation. - Use local shared primitives before raw controls or one-off component implementations.
- Keep one primary action per decision area.
- Use familiar icons for icon-only commands and provide accessible names.
- Use status colors for status, warning, success, error, and informational meaning.
- Keep cards, controls, and repeated fixed-format elements dimensionally stable.
- Avoid nested decorative cards and page sections styled as floating cards.
- Keep surfaces, controls, and insets square through their semantic radius tokens.
- Reserve round geometry for avatars, status dots, and other truly circular indicators.
- Keep focus, hover, active, disabled, loading, and invalid states coherent.
- Keep text within its container at supported viewport sizes.
- Prefer dense, scan-friendly composition for operational product surfaces.
- Share application anatomy across consumers without forcing web and native implementations into pixel-identical layouts.
Ownership
Move visual implementation into this repository when its interface is framework-neutral and useful across consumers. Keep runtime behavior and framework adapters local until at least two consumers need the same interface and behavior.
© openclaw, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file
Files
SKILL.md and 5 other files (references) in .agents/skills/openclaw-carapace of openclaw/clawhub.
- SKILL.md
- references/application-surfaces.md
- references/consumer-adapters.md
- references/embedded-surfaces.md
- references/terminal-ui.md
- references/tokens.md
Open the folder on GitHubat commit d044664
Compare with similar skills
OpenClaw Carapace UI 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 |
|---|---|---|---|---|---|---|
| OpenClaw Carapace UI this skillopenclaw/clawhub | 9.5k | — | ~699 | Automated safety check: Pass | MIT | |
| UI StylingOhh-889/skyroc | 795 | 13 repos | ~2.5k | Automated safety check: Pass | MIT | |
| Liuguang Banlan UIsickn33/agentic-awesome-skills | 47k | 1 repos | ~2.5k | Automated safety check: Pass | MIT | |
| Material Design 3 UI/UX Guideskydashnet/material-design-3-ui-skill | 135 | — | ~3k | Automated safety check: Pass | MIT | |
| UI Design Systemtry-works/role-model | 118 | — | ~5k | Automated safety check: Pass | MIT | |
| Tailwind V4 Shadcnever-works/ever-works | 162 | 2 repos | ~3.8k | Automated safety check: Pass | MIT |
Similar skills
Liuguang Banlan UI
sickn33/agentic-awesome-skills
Implements an interface in one of two named color modes, iridescent white or colorful black, from a parameterized starter that reports measured color intensity.
Material Design 3 UI/UX Guide
skydashnet/material-design-3-ui-skill
Guides designing, reviewing or implementing interfaces that follow Google's Material Design 3 system: semantic tokens, component states, adaptive layout and accessibility.
UI Design System
try-works/role-model
React UI component systems with TailwindCSS + Radix + shadcn/ui.
Tailwind V4 Shadcn
ever-works/ever-works
Production-tested setup for Tailwind CSS v4 with shadcn/ui, Vite, and React.
UI Design Styling
ryokun6/ryos
Design and style ryOS UI using the current OS theme token system, Tailwind variants, shared primitives, Aqua Glass, dark mode, and accent conventions.
More from openclaw/clawhub
All 55 skills in this repoAxiom Alerting Management
openclaw/clawhub
Creates and manages Axiom monitors and notifiers end to end through the v2 API, with scripts for each CRUD operation and a recommended create-validate-tune workflow.
Axiom Dashboard Builder
openclaw/clawhub
Designs and deploys Axiom dashboards through the API, choosing chart types and writing APL or metrics queries, with templates and migration notes for Splunk and Grafana.
Axiom Cost Control
openclaw/clawhub
Finds unused data in Axiom by analyzing query patterns, then deploys a cost dashboard and ingest monitors to keep spend under the contract limit.
Axiom Metrics Query
openclaw/clawhub
Explores and queries OpenTelemetry metrics in Axiom MetricsDB, listing datasets, metrics and tags first and picking the right aggregation for each metric's type.
Axiom SRE Investigator
openclaw/clawhub
Investigates incidents and production problems with hypothesis-driven debugging, queries Axiom observability data when available, and keeps secrets out of commands and output.
Axiom Eval Writer
openclaw/clawhub
Scaffolds evaluation suites for the Axiom AI SDK: eval files, scorers, flag schemas and axiom.config.ts, generated from plain descriptions of an AI capability.
Related
Categories
Questions about OpenClaw Carapace UI
What does OpenClaw Carapace UI do?
Guides UI work on OpenClaw apps so it uses the shared Carapace package: semantic design tokens, theme foundations, shared CSS classes and the product's existing local components. This skill sends the agent to the shared Carapace package for colors, spacing, type, radii and shadows, while routes, data, behavior and layout composition stay local to each product. Reference files cover the token set, adapters for each consuming framework, application surfaces such as shells, panes and settings screens, terminal interfaces, and surfaces rendered inside a host frame such as an MCP app.
When should I use OpenClaw Carapace UI?
OpenClaw Carapace UI fits situations like: building a new settings screen or pane in an OpenClaw application; replacing hard-coded colors and spacing with semantic design tokens; adding dark or light theme support to an existing OpenClaw interface; designing or auditing a terminal UI that should follow the shared visual language.
How do I install OpenClaw Carapace UI in Claude Code?
Run `npx skills add openclaw/clawhub --skill openclaw-carapace -a claude-code`. Or copy the skill folder (.agents/skills/openclaw-carapace in openclaw/clawhub) into .claude/skills/openclaw-carapace in your project. Claude Code loads it when a task matches its description.
How do I install OpenClaw Carapace UI in Codex?
Run `npx skills add openclaw/clawhub --skill openclaw-carapace -a codex`. Or copy the skill folder (.agents/skills/openclaw-carapace in openclaw/clawhub) into .agents/skills/openclaw-carapace in your project. Codex loads it when a task matches its description.
Can I use OpenClaw Carapace UI in Cursor, Gemini CLI or GitHub Copilot?
Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add openclaw/clawhub --skill openclaw-carapace -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/openclaw-carapace, .gemini/skills/openclaw-carapace, .github/skills/openclaw-carapace and .opencode/skills/openclaw-carapace in your project.
What does OpenClaw Carapace UI need to run?
SKILL.md names no scripts, command-line tools or credentials: OpenClaw Carapace UI is instructions for the agent only. Our summary lists: A consuming OpenClaw project that installs the Carapace package.
Does OpenClaw Carapace UI access the network?
SKILL.md contains no URLs. Any network use would come from the scripts or tools the agent runs. This is read from the text; nothing was executed.
Is OpenClaw Carapace UI safe to install?
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.
What licence does OpenClaw Carapace UI use?
OpenClaw Carapace UI is published under the MIT licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.
How many tokens does OpenClaw Carapace UI use?
About 699 tokens (SKILL.md is roughly 2.8k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full. Its references folder adds about 9.3k tokens, read only when the agent opens those files.
What are the alternatives to OpenClaw Carapace UI?
Skills that share tags, products or a category with OpenClaw Carapace UI: UI Styling (Ohh-889/skyroc, 795 stars), Liuguang Banlan UI (sickn33/agentic-awesome-skills, 47k stars), Material Design 3 UI/UX Guide (skydashnet/material-design-3-ui-skill, 135 stars) and UI Design System (try-works/role-model, 118 stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains OpenClaw Carapace UI?
openclaw (a GitHub organization) maintains it in openclaw/clawhub, which has 9,500 GitHub stars. The repository holds 55 skills in this directory. The repository was last updated on October 8, 2026.
Source: openclaw/clawhub on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.