openclaw/carapace / openclaw-design-audit
openclaw-design-audit
VerifiedAudit 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.
| File | Kind | Size |
|---|---|---|
| SKILL.md | skill md | 1.9 KB |
| references/fix-policy.md | markdown | 982 B |
| references/github-pr-delivery.md | markdown | 2.2 KB |
| references/report-format.md | markdown | 1.3 KB |
| references/rubric.md | markdown | 1.8 KB |
references/report-format.md
View on GitHub# Audit Report Format
Produce both `design-audit.json` and `design-audit.md`.
## JSON
```json
{
"schemaVersion": 2,
"carapaceVersion": "v0.1.0",
"designSystemVersion": "v0.1.0",
"consumerSha": "<sha>",
"summary": {
"errors": 0,
"warnings": 0,
"info": 0
},
"findings": [
{
"id": "token/raw-color",
"severity": "warning",
"kind": "mechanical",
"file": "src/example.css",
"line": 12,
"message": "Use the semantic accent token.",
"remediation": "Replace the raw coral value with var(--oc-accent-primary).",
"reference": "openclaw-carapace/references/tokens.md"
}
]
}
```
During the `v0.1.x` migration, emit both version fields with the same value.
`designSystemVersion` is retained for existing parsers; new consumers should
read `carapaceVersion`.
Sort findings by severity, rule ID, file, then line. Keep stable IDs so recurring
automation can compare runs.
## Markdown
Include:
1. audited Carapace version and consumer SHA
2. validation commands and rendered routes
3. count by severity
4. every error
5. at most five warning or informational findings
6. count of additional non-error findings not expanded
Use repository-relative file links. State explicitly when no significant drift
was found.
Related skills
| Skill | Stars | Updated | Works with | Status | Install |
|---|---|---|---|---|---|
| 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: 472k | Updated | Claude CodeCodex | Verified | Install |
| 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: 472k | Updated | Claude CodeCodex | Verified | Install |
| rea-tool-designmorluto/reaAudit, investigate, design, or change REA investigation tools, CLI/MCP contracts, provider capabilities, and Evidence semantics. | Stars: 472k | Updated | Claude CodeCodex | Verified | Install |
| ponytail-auditDietrichGebert/ponytailQuality audit of the whole repo: bugs, security, real load, missing tests, speed, and what to delete. Most important first. | Stars: 194k | Updated | Claude CodeCodex | Verified | Install |