Skip to content

openclaw/carapace / openclaw-carapace

openclaw-carapace

Verified

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.

Carapace

Use the shared package for foundations and framework-neutral visual primitives. Keep consumer-specific behavior, data, routes, and layout composition local.

Workflow

  1. Read tokens.md before choosing colors, spacing, type, radii, or shadows.
  2. Read consumer-adapters.md for the current framework.
  3. Read application-surfaces.md when working on shells, panes, settings, or operational screens.
  4. Read terminal-ui.md when designing or auditing a terminal interface.
  5. Read embedded-surfaces.md when the surface renders inside a host frame, such as an MCP app.
  6. Inspect the consumer's existing shared primitives before creating a component.
  7. Use semantic tokens for UI intent; use palette primitives only for documented exceptions.
  8. Keep application behavior, routes, and information architecture unchanged unless the task says otherwise.
  9. Validate the affected routes with existing tests and real browser screenshots.

Interface Rules

  • Import the complete CSS contract or its focused exported entry points.
  • Compose shared classes from components.css before adding a one-off visual implementation.
  • Use local shared primitives before raw controls or one-off component implementations.
  • Keep one primary action per decision area.
  • Use familiar icons for icon-only commands and provide accessible names.
  • Use status colors for status, warning, success, error, and informational meaning.
  • Keep cards, controls, and repeated fixed-format elements dimensionally stable.
  • Avoid nested decorative cards and page sections styled as floating cards.
  • Keep surfaces, controls, and insets square through their semantic radius tokens.
  • Reserve round geometry for avatars, status dots, and other truly circular indicators.
  • Keep focus, hover, active, disabled, loading, and invalid states coherent.
  • Keep text within its container at supported viewport sizes.
  • Prefer dense, scan-friendly composition for operational product surfaces.
  • Share application anatomy across consumers without forcing web and native implementations into pixel-identical layouts.

Ownership

Move visual implementation into this repository when its interface is framework-neutral and useful across consumers. Keep runtime behavior and framework adapters local until at least two consumers need the same interface and behavior.

brainstormingobra/superpowersYou MUST use this before any creative work - creating features, building components, adding functionality, modifying behavior, or planning anything new, in software or out of it (a talk, a business, a renovation).Stars: 322kUpdated Claude CodeCodexVerifiedInstall
brand-guidelinesanthropics/skillsApplies Anthropic's official brand colors and typography to any sort of artifact that may benefit from having Anthropic's look-and-feel. Use it when brand colors or style guidelines, visual formatting, or company design standards apply.Stars: 197kUpdated Claude CodeCodexVerifiedInstall
frontend-designanthropics/skillsGuidance for distinctive, intentional visual design when building new UI or reshaping an existing one. Helps with aesthetic direction, typography, and making choices that don't read as templated defaults.Stars: 197kUpdated Claude CodeCodexVerifiedInstall
mcp-builderanthropics/skillsGuide for creating high-quality MCP (Model Context Protocol) servers that enable LLMs to interact with external services through well-designed tools. Use when building MCP servers to integrate external APIs or services, whether in Python (FastMCP) or Node/TypeScript (MCP SDK).Stars: 197kUpdated Claude CodeCodexVerifiedInstall