agentleFS
Sign inStart free
openclawopenclaw/docs/.agents/skills/openclaw-design-audit/SKILL.md

openclaw-design-audit

Skill76 starsChanged 27 days agoMITView on GitHub

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.

We split this skill into the rules it gives an agent

9 rules. About 0 are common, 8 are distinctive, and 1 is very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈8

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 1

    Very specific

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

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    Read rubric.md and run every applicable category.

    line 13
  2. Distinctive:

    Read the consumer's installed Carapace version and current commit SHA.

    line 14
  3. Very specific:

    Read the version-matched token contract and consumer adapters from the installed product guidance skill: openclaw-carapace for new installs …

    line 15
  4. Distinctive:

    Read the brand or marketing references when those categories apply.

    line 18
  5. Distinctive:

    Run deterministic source checks before judgment-based review.

    line 19
  6. Distinctive:

    Check light and dark themes where supported.

    line 21
  7. Distinctive:

    When asked to fix findings, apply only narrow changes allowed by fix-policy.md.

    line 23
  8. Distinctive:

    Treat zero errors, zero warnings, and five or fewer informational findings as no significant drift.

    line 43
  9. Distinctive:

    Never invent source locations or visual evidence.

    line 45

≈ “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 Audit

Separate mechanical violations from judgment. Report suggestions as suggestions unless a documented rule makes them violations.

Workflow

  1. Read rubric.md and run every applicable category.
  2. Read the consumer's installed Carapace version and current commit SHA.
  3. Read the version-matched token contract and consumer adapters from the installed product guidance skill: openclaw-carapace for new installs or the openclaw-design-system compatibility alias for an upgraded lock.
  4. Read the brand or marketing references when those categories apply.
  5. Run deterministic source checks before judgment-based review.
  6. Inspect representative rendered routes at desktop and mobile sizes.
  7. Check light and dark themes where supported.
  8. Emit the JSON and Markdown defined in report-format.md.
  9. When asked to fix findings, apply only narrow changes allowed by fix-policy.md.
  10. For scheduled ClawHub delivery, follow github-pr-delivery.md.

Evidence

Each finding must include:

  • file and line
  • category and severity
  • stable rule ID
  • concise remediation
  • Carapace reference
  • whether the finding is mechanical or judgment-based

Curation

  • Include every error.
  • Rank warnings before informational findings, then by affected-file count.
  • Surface at most five non-error findings in the concise report.
  • Summarize remaining non-error findings by count.
  • Treat zero errors, zero warnings, and five or fewer informational findings as no significant drift.
  • Never invent source locations or visual evidence.

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.
  • Other versions4 projects use a version of this.

    Word for word · 4

    1. openclaw/clawhub★ 9.5k100% same
    2. clawdbot/clawdhub★ 9.5k100% same
    3. moltbot/molthub★ 9.5k100% same
    4. openclaw/carapace★ 7100% same

    Edited · 0

    None found.

    Wrote their own version · 0

    None found.

    How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.

  • In this repository8 other files it gives its agents.

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.

Check your setup, free