agentleFS
openclawopenclaw/docs/.agents/skills/openclaw-design/SKILL.md

openclaw-design

Skill76 starsChanged 27 days agoMITView on GitHub

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.

We split this skill into the rules it gives an agent

6 rules. About 0 are common, 6 are distinctive, and 0 are very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈6

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 0

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    Keep runtime CSS pinned to a semantic release tag.

    line 29
  2. Distinctive:

    Prefer semantic tokens over raw palette values.

    line 30
  3. Distinctive:

    Keep product-specific components and layouts in their consumer repository.

    line 31
  4. Distinctive:

    Add shared implementation only after at least two consumers demonstrate the same interface.

    line 32
  5. Distinctive:

    Check both light and dark themes where the consumer supports them.

    line 35
  6. Distinctive:

    Do not redistribute fonts, logos, or artwork without recorded permission.

    line 36

≈ “Common” is an estimate: at least 1 in 5 of the 308,232 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

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.

Download now (ZIP)

Trending

Steady: 0 new projects took it in the last 4 weeks, none the 4 weeks before.thin data

Week of Aug 30: 0 new projectsWeek of Sep 6: 0 new projectsWeek of Sep 13: 0 new projectsWeek of Sep 20: 0 new projectsWeek of Sep 27: 0 new projectsWeek of Oct 4: 0 new projectsWeek of Oct 11: 0 new projectsWeek of Oct 18: 0 new projects
Aug 2026Sep 2026Oct 2026
New projects taking a version of this file each week, over the 8 weeks our latest run read: only 0 in all, so this is a hint, not a trend.

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.