Skip to content
cccskills
FreePublished on GitHub

openclaw-design

Choose the right OpenClaw design guidance for brand identity, application interfaces, public pages, or audits. It directs agents to focused instructions and shared rules for consistent styling, reusable components, and browser checks.

OriginalShow the original description

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.

See how to install

Good for

  • Choosing guidance for a public website update
  • Updating application styling and themes
  • Reviewing visual consistency and accessibility
  • Checking rules for logo and typography changes

Files 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.

SkillUse for
openclaw-brandIdentity decisions, typography, logos, 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, 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.

Comments are published right away. Do not include personal information such as email addresses or phone numbers. Up to 2 URLs.

0 / 1,000 characters

This form is protected by reCAPTCHA, and the Google Privacy Policy and Terms of Service apply.

More skills from this repository

autoreview

FreeSummary

Review code using shared OpenClaw instructions and a Python helper, while also following the target repository’s review requirements. This skill points to a common installation that supplies the actual review procedure.

  • Reviewing code with shared OpenClaw instructions
  • Applying repository-specific review requirements
  • Keeping shared review instructions up to date
openclaw/clawhub9.5KUpdated Oct 19, 2026

axiom-alerting

FreeSummary

Create and manage Axiom alert rules and notification destinations through its API. Connect alerts to email, Slack, or webhooks, check monitor history, and adjust thresholds and evaluation schedules to address excessive or missing alerts.

  • Set up error alerts and notification destinations
  • Tune monitors that send too many alerts
  • Investigate monitors that never trigger
openclaw/clawhub9.5KUpdated Oct 19, 2026

axiom-sre

FreeSummary

Investigate production incidents and bugs using logs, metrics, and code evidence. The skill guides hypothesis testing, root cause analysis, fix validation, and reusable investigation notes, with access to configured observability tools such as Axiom.

  • Investigate production outages and rising error rates
  • Trace causes using logs, metrics, and code
  • Reproduce bugs and validate minimal fixes
openclaw/clawhub9.5KUpdated Oct 19, 2026

Design and build Axiom dashboards from logs or metrics, the numerical measurements of system behavior. Create charts, filters, and layouts for monitoring and reporting, or migrate existing Splunk and Grafana panels while validating queries against available data.

  • Build a service health monitoring dashboard
  • Create interactive filters for investigating logs
  • Migrate dashboards from Splunk or Grafana
openclaw/clawhub9.5KUpdated Oct 19, 2026

Drafts, previews, sends, and records emails for existing ClawHub content rights cases. It supports publisher removal notices and requester updates, requires approval of the final draft, and preserves the exact correspondence in the case record.

  • Preparing a skill removal notice for a publisher
  • Sending a requester a progress update or closure note
  • Preserving sent correspondence in an existing rights case
openclaw/clawhub9.5KUpdated Oct 19, 2026

clawhub-convex

FreeSummary

Apply ClawHub-specific rules when developing with Convex, including deployment targeting, runtime checks, data migrations, search performance, and skill statistics. It also directs specialized work to the appropriate companion skills.

  • Changing Convex functions or schemas
  • Planning production data migrations
  • Reviewing search query performance
openclaw/clawhub9.5KUpdated Oct 19, 2026

See all skills by openclaw

Report a problem with this skill