Install
$ agentstack add skill-openclaw-design-system-openclaw-brand ✓ scanned · ✓ verified, works with Claude Code, Cursor, and more.
Security review
✓ PassedNo issues found. Passed automated security review. · v0.1.0 How review works →
- ✓ Prompt-injection patterns
- ✓ Secret / credential exfiltration
- ✓ Dangerous shell & filesystem operations
- ✓ Untrusted network calls
- ✓ Known-malicious package signatures
What it can access
- ✓ Network access No
- ✓ Filesystem access No
- ✓ Shell / process execution No
- ✓ Environment & secrets No
- ✓ Dynamic code execution No
From automated source analysis of v0.1.0. “Used” means the capability is present in the source — more access means more to trust, not that it’s unsafe.
Verified badge
Passed review? Show it. Paste this badge into your README, it links to the public security report.
Reliability & compatibility
Declared compatibility
Compatibility is declared by the source manifest. End-to-end runtime verification is coming, see below.
We're building live execution health for every listing: tool-call success rate, median latency, uptime, and last-checked timestamps, measured, not self-reported. It isn't live yet, so we don't show numbers we can't stand behind.
How agent discovery & health will work →About
OpenClaw Brand
Use the canonical identity without turning every surface into a marketing page.
Workflow
- Read [identity.md](references/identity.md) for palette, typography, logo, and voice.
- Read [asset-rights.md](references/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.
Source & license
This open-source skill is cataloged on AgentStack and links to its original source — we do not rehost the code.
- Author: openclaw
- Source: openclaw/design-system
- License: MIT
- Homepage: https://openclaw.github.io/design-system/
Install and usage instructions live in the source repository linked above.
Reviews
No reviews yet, be the first.
Write a review
Versions
- v0.1.0 Imported from the upstream source.