Structured code review through the shared OpenClaw agent-skills installation.
The English summary is being prepared. Showing the original description.
openclaw/docs76Updated Oct 21, 2026
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.
The English summary is being prepared. Showing the original description.
See how to installFiles included (3)
- SKILL.md1.7 KB
- references/asset-rights.md802 B
- references/identity.md1.7 KB
SKILL.md (original)
Review the instructions the agent will receive before you install.
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.
Reviews
No reviews yet. Tell others what you thought.
Comments
No login needed. Share how it worked for you, ask a question, or note where it did not run.
No comments yet. Be the first to write one.
More skills from this repository
Use the Crabbox wrapper for OpenClaw remote validation across Linux, macOS, Windows, and WSL2, including delegated Blacksmith Testbox proof. Report the actual provider and id.
The English summary is being prepared. Showing the original description.
openclaw/docs76Updated Oct 21, 2026
Build or modify OpenClaw application UI using canonical semantic tokens, themes, shared CSS foundations, consumer adapters, and established local primitives. Use for product interfaces, component styling, theme work, or design-token integration.
The English summary is being prepared. Showing the original description.
openclaw/docs76Updated Oct 21, 2026
Route OpenClaw design work to canonical brand, Carapace product-interface, marketing-page, or design-audit guidance. Use when a task touches OpenClaw visual identity, shared CSS tokens, product UI, public web pages, or Carapace compliance.
The English summary is being prepared. Showing the original description.
openclaw/docs76Updated Oct 21, 2026
Audit OpenClaw frontend code and rendered interfaces for Carapace drift, token misuse, primitive reimplementation, accessibility problems, responsive defects, and off-brand copy. Use for design reviews, compliance checks, or scheduled audit-and-fix workflows.
The English summary is being prepared. Showing the original description.
openclaw/docs76Updated Oct 21, 2026
Compatibility alias for existing OpenClaw installations that now applies Carapace semantic tokens, themes, shared CSS foundations, consumer adapters, and established local primitives.
The English summary is being prepared. Showing the original description.
openclaw/docs76Updated Oct 21, 2026