Requirements
- Target platform
- OpenClaw
- Install method
- Manual import
- Extraction
- Extract archive
- Prerequisites
- OpenClaw
- Primary doc
- SKILL.md
Build design systems with tokens, components, and documentation that scale across teams and products.
Build design systems with tokens, components, and documentation that scale across teams and products.
Hand the extracted package to your coding agent with a concrete install brief instead of figuring it out manually.
I downloaded a skill package from Yavira. Read SKILL.md from the extracted folder and install it by following the included instructions. Tell me what you changed and call out any manual steps you could not complete.
I downloaded an updated skill package from Yavira. Read SKILL.md from the extracted folder, compare it with my current installation, and upgrade it while preserving any custom configuration unless the package docs explicitly say otherwise. Summarize what changed and any follow-up checks I should run.
On first use, read setup.md for integration guidelines. All preferences are stored in ~/design-system/memory.md.
User needs to create, maintain, or extend a design system. Agent handles token architecture, component patterns, documentation structure, and cross-platform consistency.
Memory lives in ~/design-system/. See memory-template.md for structure. ~/design-system/ βββ memory.md # Status + context + decisions βββ tokens/ # Token definitions if exported
TopicFileSetup processsetup.mdMemory templatememory-template.md
Design tokens are the foundation. Before building any component: Define color tokens (semantic, not raw hex) Define spacing scale (consistent multiplier) Define typography scale (modular) Components consume tokens. Never hardcode values.
BadGoodblue-500primary14pxtext-sm8pxspace-2 Semantic names survive rebrand. Literal names break everything.
Primitive β Semantic β Component β β β gray-900 text-primary button-text Primitive: Raw values (colors, sizes) Semantic: Meaning-based (primary, danger, muted) Component: Specific use (button-bg, card-border)
Every token and component needs: What: The value or pattern When: Usage context Why: The decision behind it When NOT: Anti-patterns to avoid
Design tokens should export to: CSS custom properties Tailwind config iOS/Android native Figma variables One source, many outputs. Use Style Dictionary or similar.
All components follow the same patterns: Same prop naming (variant, size, disabled) Same size scale (sm, md, lg) Same variant names (primary, secondary, ghost) Predictability beats cleverness.
Breaking changes need: Version bump (semver) Migration guide Deprecation warnings before removal Codemods when possible
Premature abstraction β Build 3 instances before extracting a pattern Token explosion β 50 grays is not a system, it is chaos Skipping documentation β Undocumented patterns get reimplemented wrong Designing for edge cases first β Cover 80% well before 100% poorly No dark mode strategy β Retrofit is 10x harder than planning upfront Inconsistent spacing β Use a scale (4px base), not arbitrary values Component prop sprawl β More than 10 props means split the component
Data that stays local: Design decisions in ~/design-system/ Token definitions and component specs This skill does NOT: Access files outside ~/design-system/ Make network requests Store sensitive data
Install with clawhub install <slug> if user confirms: css β Styling fundamentals tailwindcss β Utility-first CSS frontend β Frontend development ui β User interface patterns design β Design principles
If useful: clawhub star design-system Stay updated: clawhub sync
Agent frameworks, memory systems, reasoning layers, and model-native orchestration.
Largest current source with strong distribution and engagement signals.