Compatibility alias for existing OpenClaw installations that now applies Carapace semantic tokens, themes, shared CSS foundations, consumer adapters, and established local primitives.
76%
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
Fix and improve this skill with Tessl
tessl review fix ./.agents/skills/openclaw-design-system/SKILL.mdThis skill identifier remains available for existing skills-lock.json
entries during the v0.1.x migration. New installations should use
openclaw-carapace.
Use the shared package for foundations and framework-neutral visual primitives.
Keep consumer-specific behavior, data, routes, and layout composition local.
Before changing imports, inspect the consumer manifest: use
@openclaw/carapace when it is installed, otherwise preserve the legacy
@openclaw/design-system specifier until the dependency is migrated.
components.css before adding a one-off visual implementation.Move visual implementation into this repository when its interface is framework-neutral and useful across consumers. Keep runtime behavior and framework adapters local until at least two consumers need the same interface and behavior.
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.