openclaw-design git:20261027.bad4e40A

Immutable. This exact content never changes and is served at /api/v1/blob/962c71fba73f0b90.

---
name: openclaw-design
description: 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.
---

# OpenClaw Design

For OpenClaw and OpenClaw Foundation logo-only tasks, use the
[brand kit README](https://github.com/openclaw/carapace/tree/main/brand-kit) directly.
For other design work, 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, 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, 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.

## Shared Contract

- Install agent guidance from this repository's default branch and refresh it with
  `npx skills@1.5.16 update --project --yes`.
- Keep runtime CSS pinned to a semantic release tag.
- Prefer semantic tokens over raw palette values.
- Keep product-specific components and layouts in their consumer repository.
- Add shared implementation only after at least two consumers demonstrate the same interface.
- Preserve consumer behavior while changing the visual foundation.
- Validate rendered pages in a real browser at desktop and mobile sizes.
- Check both light and dark themes where the consumer supports them.
- Do not redistribute fonts, logos, or artwork without recorded permission.