What problem does it solve?
OpenClaw design work spans brand identity, product interfaces, marketing pages, and design audits, and choosing the wrong guidance leads to inconsistent tokens, drifted components, and off-brand pages. This Skill routes each design task to the correct canonical guidance branch before any interface changes are made.
Core Features & Use Cases
- Task Routing: Directs work to one of five focused branches: openclaw-brand, openclaw-carapace, openclaw-design-system, openclaw-marketing-pages, or openclaw-design-audit.
- Shared Design Contract: Enforces rules such as preferring semantic tokens over raw palette values, pinning runtime CSS to semantic release tags, and validating pages in real browsers at desktop and mobile sizes.
- Use Case: When asked to redesign a public landing page, start with the openclaw-marketing-pages branch and only add openclaw-brand if the task also changes identity, logo, imagery, typography, or voice.
Quick Start
Ask the agent to route your OpenClaw design task, for example: route this landing page redesign to the correct OpenClaw design guidance before making changes.