What problem does it solve?
Building consistent OpenClaw product interfaces across web, native macOS, terminal, and embedded MCP surfaces is hard when every consumer invents its own colors, spacing, and components. This Skill enforces the canonical Carapace design system so UI work stays coherent across consumers.
Core Features & Use Cases
- Semantic token guidance: Directs color, spacing, typography, radius, and motion choices through the
--oc-* token contract instead of ad-hoc values.
- Consumer adapters: Provides import order and integration rules for plain CSS, Astro, Tailwind 4, native macOS (SwiftUI/AppKit), and static documentation builders.
- Surface-specific references: Covers application shells and settings panes, terminal UI compositions, and sandboxed embedded MCP app surfaces with sizing, branding, and lifecycle rules.
- Use Case: When styling a new settings screen in the Control UI, follow the workflow to read the token and application-surface references, compose existing
.oc-* classes, and validate with browser screenshots instead of writing one-off CSS.
Quick Start
Ask the agent to restyle an OpenClaw route or component using the Carapace semantic tokens and shared component classes, then validate the result with existing tests and browser screenshots.