Agent Skills
› openclaw/clawhub
› openclaw-design
openclaw-design
GitHub指导 OpenClaw 设计工作路由至品牌、UI、营销页或审计分支。适用于涉及视觉标识、CSS 令牌、产品界面或公共网页的任务，确保设计规范与合规性。
Trigger Scenarios
涉及 OpenClaw 视觉标识或品牌决策
修改产品 UI 或共享 CSS 令牌
构建或更新公共营销页面
进行设计审计或可访问性检查
Install
npx skills add openclaw/clawhub --skill openclaw-design -g -y
SKILL.md
Frontmatter
{
"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
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.
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.
Version History
- 5a3b050 Current 2026-07-25 08:44
