autoreview
FreeStructured code review through the shared OpenClaw agent-skills installation.
The English summary is being prepared. Showing the original description.
openclaw/carapace7Updated Oct 17, 2026
FreePublished on GitHub
openclaw-design
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.
See how to installFiles included (1)
- SKILL.md2.0 KB
SKILL.md (original)
Review the instructions the agent will receive before you install.
OpenClaw Design
Choose one focused branch before changing an interface. Load multiple branches only when the task genuinely crosses them.
| Skill | Use for |
|---|---|
openclaw-brand | Identity decisions, typography, logos, imagery, voice, and non-product brand artifacts |
openclaw-carapace | Application UI, semantic tokens, themes, component reuse, and framework adapters |
openclaw-design-system | Compatibility alias for projects upgrading an existing skill lock |
openclaw-marketing-pages | Public-page composition, landing/content pages, navigation, SEO, and responsive layout |
openclaw-design-audit | Design drift, token misuse, component substitution, accessibility, and recurring audits |
For a public website change, start with openclaw-marketing-pages and add
openclaw-brand only when the task changes identity, logo, imagery, typography,
or voice. For a product application, start with openclaw-carapace when it is
installed. Projects upgrading an existing lock may use
openclaw-design-system as the v0.1.x compatibility alias.
Shared Contract
- Install agent guidance from this repository's default branch and refresh it with
npx skills@1.5.16 update --project --yes. - Keep runtime CSS pinned to a semantic release tag.
- Prefer semantic tokens over raw palette values.
- Keep product-specific components and layouts in their consumer repository.
- Add shared implementation only after at least two consumers demonstrate the same interface.
- Preserve consumer behavior while changing the visual foundation.
- Validate rendered pages in a real browser at desktop and mobile sizes.
- Check both light and dark themes where the consumer supports them.
- Do not redistribute fonts, logos, or artwork without recorded permission.
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
openclaw-brand
FreeApply 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.
openclaw/carapace7Updated Oct 17, 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/carapace7Updated Oct 17, 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/carapace7Updated Oct 17, 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/carapace7Updated Oct 17, 2026
Create or update OpenClaw public-page composition for websites, landing pages, content pages, ecosystem pages, and campaigns. Use for page structure, navigation, responsive layout, media, SEO presentation, or public-site visual polish.
The English summary is being prepared. Showing the original description.
openclaw/carapace7Updated Oct 17, 2026