mirror of
https://github.com/openclaw/clawhub.git
synced 2026-08-14 00:47:57 +00:00
Patrick Erichsen
de29369ba7
* chore: install OpenClaw design system * feat: adopt shared design system palette * chore: automate design system updates * feat: add weekly design system audit * fix: prevent mobile skills tab overlap * fix: harden design audit automation * fix: validate audit changes before execution * fix: scope design system clone credentials * fix: align audit with installed design release * fix: preserve audit artifacts and access * feat: adopt shared design system on landing page * fix: align icon geometry with design tokens * chore: pin design system to v0.0.1 * chore: pin design system to v0.0.1 * chore: pin design system to v0.0.1 * chore: pin design system to v0.0.1 * chore: pin design system to v0.0.1 * fix: migrate ClawHub UI to design tokens * fix: use public design system installs * fix: use public design system distribution
1.7 KiB
1.7 KiB
name, description
| name | description |
|---|---|
| openclaw-brand | Apply OpenClaw visual identity to logos, typography, imagery, voice, documents, presentations, social graphics, and launch materials. Use when the task changes brand identity rather than ordinary product UI or public-page composition. |
OpenClaw Brand
Use the canonical identity without turning every surface into a marketing page.
Workflow
- Read identity.md for palette, typography, logo, and voice.
- Read asset-rights.md before copying or redistributing assets.
- Identify the artifact's audience and whether it is product, documentation, or marketing.
- Use semantic design tokens when the artifact is code.
- Keep status colors functional; do not use them as arbitrary decoration.
- Verify contrast, responsive cropping, and text legibility.
- Verify logo clearspace only when approved consumer-local guidance defines it; otherwise report that check as unavailable rather than inventing a measurement.
Rules
- Use sentence case for headings, labels, buttons, and navigation.
- Let OpenClaw coral carry primary brand emphasis.
- Use sea-glass green as a restrained secondary accent.
- Use neutral ink and warm-paper surfaces as the foundation.
- Prefer Switzer-compatible sans-serif stacks for interface and body copy.
- Reserve Sentient-compatible serif stacks for editorial accents and quotations.
- Use system monospace for code unless the consumer already licenses another face.
- Preserve logo proportions and colors. Do not rotate, distort, outline, or add effects.
- Use real product, interface, community, or mascot imagery when imagery is needed.
- Avoid generic technology gradients, decorative blobs, and ornamental glow as a substitute for content.