Route OpenClaw design work to canonical brand, Carapace product-interface, marketing-page, or design-audit guidance. Use when a task touches OpenClaw visual identity, shared CSS tokens, product UI, public web pages, or Carapace compliance.
82%
Does it follow best practices?
Run evals on this skill
Adds up to 20 points to the overall score
Passed
No findings from the security scan
Choose one focused branch before changing an interface. Load multiple branches only when the task genuinely crosses them.
| Skill | Use for |
|---|---|
openclaw-brand | Identity decisions, typography, logos, imagery, voice, and non-product brand artifacts |
openclaw-carapace | Application UI, semantic tokens, themes, component reuse, and framework adapters |
openclaw-design-system | Compatibility alias for projects upgrading an existing skill lock |
openclaw-marketing-pages | Public-page composition, landing/content pages, navigation, SEO, and responsive layout |
openclaw-design-audit | Design drift, token misuse, component substitution, accessibility, and recurring audits |
For a public website change, start with openclaw-marketing-pages and add
openclaw-brand only when the task changes identity, logo, imagery, typography,
or voice. For a product application, start with openclaw-carapace when it is
installed. Projects upgrading an existing lock may use
openclaw-design-system as the v0.1.x compatibility alias.
npx skills@1.5.16 update --project --yes.openclaw/clawhub
7aa988e
If you maintain this skill, you can claim it as your own. Once claimed, you can manage eval scenarios, bundle related skills, attach documentation or rules, and ensure cross-agent compatibility.