openclaw-design-system
Compatibility alias for existing OpenClaw installations that now applies Carapace semantic tokens, themes, shared CSS foundations, consumer adapters, and established local primitives.
- License 许可
- MIT
- 所属仓库
- openclaw/clawhub
- 最近更新
- 2026-11-15
- Stars
- ★ 9.6k
- Forks
- 1.5k
01 前言 Front Matter
- name
- openclaw-design-system
- description
- Compatibility alias for existing OpenClaw installations that now applies Carapace semantic tokens, themes, shared CSS foundations, consumer adapters, and established local primitives.
02 资源文件 2
- 参考文档references/consumer-adapters.md2.0 KB
- 参考文档references/tokens.md3.0 KB
03 SKILL.md 正文
Carapace Compatibility Alias
This 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.
Workflow
- Read tokens.md before choosing colors, spacing, type, radii, or shadows.
- Read consumer-adapters.md for the current framework.
- Inspect the consumer's existing shared primitives before creating a component.
- Use semantic tokens for UI intent; use palette primitives only for documented exceptions.
- Keep application behavior, routes, and information architecture unchanged unless the task says otherwise.
- Validate the affected routes with existing tests and real browser screenshots.
Interface Rules
- Import the complete CSS contract or its focused exported entry points.
- Compose shared classes from
components.cssbefore adding a one-off visual implementation. - Use local shared primitives before raw controls or one-off component implementations.
- Keep one primary action per decision area.
- Use familiar icons for icon-only commands and provide accessible names.
- Use status colors for status, warning, success, error, and informational meaning.
- Keep cards, controls, and repeated fixed-format elements dimensionally stable.
- Avoid nested decorative cards and page sections styled as floating cards.
- Keep surfaces, controls, and insets square through their semantic radius tokens.
- Reserve round geometry for avatars, status dots, and other truly circular indicators.
- Keep focus, hover, active, disabled, loading, and invalid states coherent.
- Keep text within its container at supported viewport sizes.
- Prefer dense, scan-friendly composition for operational product surfaces.
Ownership
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.
04 同仓库更多 Skills
notes
Turn user-provided notes into a concise agenda.
hosted-research
Read approved reference material for the hosted proof.
convex-advisor
Read the Convex deployment's 72h insights (read limits, OCC contention), root-cause each event in code, report evidence-backed perf/cost findings with fixes.
convex-add
Add a capability to the CURRENT Convex app — consults the served Convex capability catalog for always-current procedures (billing, crons, auth, agent, search, …); falls back to built-in hosting or @convex-dev component search. TRIGGER when the user runs /add, or asks to add hosting/publishing or any backend capability to an existing Convex app.
convex-acquire-domain
Find and buy a domain for the current Convex app through Convex, then bind it (labs; spend action).
controlling-costs
Analyzes Axiom query patterns to find unused data, then builds dashboards and monitors for cost optimization. Use when asked to reduce Axiom costs, find unused columns or field values, identify data waste, or track ingest spend.