Skip to content

openclaw/carapace / openclaw-design

openclaw-design

Verified

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.

OpenClaw Design

For OpenClaw and OpenClaw Foundation logo-only tasks, use the brand kit README directly. For other design work, choose one focused branch before changing an interface. Load multiple branches only when the task genuinely crosses them.

SkillUse for
openclaw-brandIdentity decisions, typography, imagery, voice, and non-product brand artifacts
openclaw-carapaceApplication UI, semantic tokens, themes, component reuse, and framework adapters
openclaw-design-systemCompatibility alias for projects upgrading an existing skill lock
openclaw-marketing-pagesPublic-page composition, landing/content pages, navigation, SEO, and responsive layout
openclaw-design-auditDesign 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, 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.
rea-analysis-optimizationmorluto/reaOptimize REA providers and shared analysis workflows for agent context, latency, CPU, and memory while preserving correctness and Evidence. Use for analysis bottlenecks and cache or query design; CI/test-suite optimization belongs to rea-ci-tests-audit.Stars: 468kUpdated Claude CodeCodexVerifiedInstall
rea-ci-tests-auditmorluto/reaAudit REA CI and test suites for correctness, fixture drift, false passes, and measured performance; use for suite or workflow investigations and efficiency changes, rather than ordinary feature testing or a single test failure.Stars: 468kUpdated Claude CodeCodexVerifiedInstall
rea-tool-designmorluto/reaAudit, investigate, design, or change REA investigation tools, CLI/MCP contracts, provider capabilities, and Evidence semantics.Stars: 468kUpdated Claude CodeCodexVerifiedInstall
ponytail-auditDietrichGebert/ponytailQuality audit of the whole repo: bugs, security, real load, missing tests, speed, and what to delete. Most important first.Stars: 194kUpdated Claude CodeCodexVerifiedInstall