Material Design 3 UI/UX Guide
skydashnet/material-design-3-ui-skill
Guides designing, reviewing or implementing interfaces that follow Google's Material Design 3 system: semantic tokens, component states, adaptive layout and accessibility.
Two-mode frontend skill: (1) authoring — accessibility, responsive layout, loading/error states, performance, DESIGN.md authoring, visual direction; (2) critique — READ-only scored review of built…
Install Frontend
$ npx skills add romiluz13/cc10x --skill frontend -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install romiluz13/cc10x frontend --agent claude-codeProject scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).
$ git clone --depth 1 https://github.com/romiluz13/cc10x.git skills-src && mkdir -p .claude/skills && cp -r skills-src/plugins/cc10x/skills/frontend .claude/skills/frontend && rm -rf skills-srcUse ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.
Claude Code skills documentation · loads skills from .claude/skills/
Install the "frontend" agent skill from https://github.com/romiluz13/cc10x/tree/main/plugins/cc10x/skills/frontend into .claude/skills/frontend/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "frontend", then confirm the skill loads.Claude Code copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$skill-installer install https://github.com/romiluz13/cc10x/tree/main/plugins/cc10x/skills/frontendType this inside Codex. $skill-installer <name> installs a curated skill from openai/skills. The installer writes to $CODEX_HOME/skills (default ~/.codex/skills). Restart Codex if the skill does not show up.
$ npx skills add romiluz13/cc10x --skill frontend -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install romiluz13/cc10x frontend --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/romiluz13/cc10x.git skills-src && mkdir -p .agents/skills && cp -r skills-src/plugins/cc10x/skills/frontend .agents/skills/frontend && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "frontend" agent skill from https://github.com/romiluz13/cc10x/tree/main/plugins/cc10x/skills/frontend into .agents/skills/frontend/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "frontend", then confirm the skill loads.Codex copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add romiluz13/cc10x --skill frontend -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install romiluz13/cc10x frontend --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/romiluz13/cc10x.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/plugins/cc10x/skills/frontend .cursor/skills/frontend && rm -rf skills-srcUse ~/.cursor/skills/ instead of .cursor/skills for a personal install.
Cursor skills documentation · loads skills from .cursor/skills/, .agents/skills/, .claude/skills/, .codex/skills/
Install the "frontend" agent skill from https://github.com/romiluz13/cc10x/tree/main/plugins/cc10x/skills/frontend into .cursor/skills/frontend/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "frontend", then confirm the skill loads.Cursor copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gemini skills install https://github.com/romiluz13/cc10x.git --path plugins/cc10x/skills/frontend--scope user (default) or --scope workspace; --path is the subfolder of the repo that holds the skill; --consent skips the security confirmation prompt.
$ npx skills add romiluz13/cc10x --skill frontend -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install romiluz13/cc10x frontend --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/romiluz13/cc10x.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/plugins/cc10x/skills/frontend .gemini/skills/frontend && rm -rf skills-srcUse ~/.gemini/skills/ instead of .gemini/skills for a personal install, then run /skills reload.
Gemini CLI skills documentation · loads skills from .gemini/skills/, .agents/skills/
Install the "frontend" agent skill from https://github.com/romiluz13/cc10x/tree/main/plugins/cc10x/skills/frontend into .gemini/skills/frontend/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "frontend", then confirm the skill loads.Gemini CLI copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gh skill install romiluz13/cc10x frontendInstalls for Copilot at project scope by default; add --scope user for a personal install. Preview a skill first with gh skill preview. Needs GitHub CLI 2.90.0 or later (public preview).
$ npx skills add romiluz13/cc10x --skill frontend -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/romiluz13/cc10x.git skills-src && mkdir -p .github/skills && cp -r skills-src/plugins/cc10x/skills/frontend .github/skills/frontend && rm -rf skills-srcUse ~/.copilot/skills/ instead of .github/skills for a personal install. Commit .github/skills so cloud agent and code review can use it.
GitHub Copilot skills documentation · loads skills from .github/skills/, .claude/skills/, .agents/skills/
Install the "frontend" agent skill from https://github.com/romiluz13/cc10x/tree/main/plugins/cc10x/skills/frontend into .github/skills/frontend/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "frontend", then confirm the skill loads.GitHub Copilot copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add romiluz13/cc10x --skill frontend -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install romiluz13/cc10x frontend --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/romiluz13/cc10x.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/plugins/cc10x/skills/frontend .opencode/skills/frontend && rm -rf skills-srcUse ~/.config/opencode/skills/ instead of .opencode/skills for a personal install.
OpenCode skills documentation · loads skills from .opencode/skills/, .claude/skills/, .agents/skills/
Install the "frontend" agent skill from https://github.com/romiluz13/cc10x/tree/main/plugins/cc10x/skills/frontend into .opencode/skills/frontend/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "frontend", then confirm the skill loads.OpenCode copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
Facts
- Skill name
frontend- GitHub stars
- 164
- Token cost
- ~2k tokens
- SKILL.md length
- 928 words
- Files
- 6 (incl. references)
- Skills in repo
- 22
- Repo updated
- First seen
- Licence
- MIT
At a glance
Two-mode frontend skill: (1) authoring — accessibility, responsive layout, loading/error states, performance, DESIGN.md authoring, visual direction; (2) critique — READ-only scored review of built…
- Works in 2 steps: First-order: Could you guess the… → Second-order: Could you guess it from…
- Tasks that involve Quizzes and assessments
- SKILL.md covers Reference Files, Shared Visual Direction Rules, Mode: AUTHORING and Mode: CRITIQUE
- Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md
What it does
Frontend is an agent skill from romiluz13/cc10x. Two-mode frontend skill: (1) authoring — accessibility, responsive layout, loading/error states, performance, DESIGN.md authoring, visual direction; (2) critique — READ-only scored review of built UI against anchored rubric, AI-slop detection, two isolated assessments. Router invokes mode via context.
Its SKILL.md is about 2k tokens, which your agent loads only when the skill is triggered. The skill folder holds 6 other files, including reference files (for example `references/accessibility-and-forms.md`, `references/design-md-authoring.md` and `references/design-md-inspiration-index.md`).
It sits in Frontend & Design, covering Quizzes and assessments, Design tokens and Responsive design. The repository describes itself as: The Loop Engine for Claude Code — engineer the loop, not the prompt. 1 router · 9 agents · 16 skills · 4 workflows. Fail-closed gates, test honesty, anti-anchored review. The licence is MIT.
When your agent uses it
- Tasks that involve Quizzes and assessments
- Tasks that involve Design tokens
- Tasks that involve Responsive design
Example prompts
- “/frontend”
Requirements
- Node.js
- Pre-approved tools (allowed-tools): Read, Grep, Glob, Bash, LSP
Workflow steps
2 steps, taken from the first numbered list in SKILL.md.
- First-order: Could you guess the theme/palette from the category alone? ("Fintech → blue + sans-serif.") If yes → generic. Reject.
- Second-order: Could you guess it from category + anti-references? Once everyone "avoids the purple gradient," the avoidance becomes a…
What it can do on your machine
Read from SKILL.md and the folder at commit f346ebe. It shows what the files ask for, not the result of running them.
Tool permissions
Pre-approves these tools, so the agent can use them without asking each time:
ReadGrepGlobBashLSP
From allowed-tools in the SKILL.md frontmatter.
Runs code
No scripts in the folder and no shell commands in SKILL.md.
From the folder's file list and the shell code blocks in SKILL.md.
Network
No URLs in SKILL.md.
From URLs in SKILL.md, links to its own repository left out.
Credentials
Names no API keys, tokens, secrets or passwords.
From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.
Context cost
Frontend loads about 2k tokens when it runs, and up to ~5.4k if it reads all its reference files. Until then it costs about 78 tokens; SKILL.md has 928 words of instructions outside code blocks.
Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.
Safety
Auto-check: notes
The automated check noted patterns worth knowing about, such as sudo or a known installer.
- NotePre-approves every shell command (allowed-tools: Bash)SKILL.md
allowed-tools: Read, Grep, Glob, Bash, LSP
Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.
SKILL.md
The full file from romiluz13/cc10x at commit f346ebe, republished under its MIT licence (© romiluz13). 928 words, ~2,027 tokens.
Download SKILL.mdSave it as
.claude/skills/frontend/SKILL.md (or your agent's skills folder). This skill also uses 5 other files; get the full folder from GitHub.- name
- frontend
- description
- Two-mode frontend skill: (1) authoring — accessibility, responsive layout, loading/error states, performance, DESIGN.md authoring, visual direction; (2) critique — READ-only scored review of built UI against anchored rubric, AI-slop detection, two isolated assessments. Router invokes mode via context.
- allowed-tools
- Read, Grep, Glob, Bash, LSP
- user-invocable
- false
Frontend (Authoring + Critique)
Two modes: authoring (build UI with patterns) and critique (score built UI). Both share the visual-direction rules below.
Reference Files
Read only what's needed:
references/ui-state-and-feedback.md— loading/error/empty/success ordering, skeleton vs spinnerreferences/accessibility-and-forms.md— WCAG, keyboard/focus, labels, form patterns, mobilereferences/performance-and-layout.md— responsive, motion, overflow, URL state, light/dark modereferences/design-md-authoring.md— creating/updating DESIGN.md from screenshots, existing UI, preferencesreferences/design-md-inspiration-index.md— style references when user asks for direction
Shared Visual Direction Rules
Two-Altitude Reflex Check
Before committing a visual direction, run both tests:
- First-order: Could you guess the theme/palette from the category alone? ("Fintech → blue + sans-serif.") If yes → generic. Reject.
- Second-order: Could you guess it from category + anti-references? Once everyone "avoids the purple gradient," the avoidance becomes a reflex — fintech dodging blue lands on the same off-black + lime. If predictable given what people flee toward → still generic. Reject.
The cure: derive direction from the specific product, audience, and content — not from the category or what the category is fleeing.
Reflex-Reject Lists (maintained, pruned as families saturate)
| Reflex-reject fonts | Reflex-reject aesthetic lanes |
|---|---|
| Inter, Roboto, Arial, system-ui defaults | Purple/violet gradient on white (AI-tool reflex #1) |
| Geist / Geist Mono (over-saturated) | Off-black + acid-lime "anti-corporate" (reflex #2) |
| Space Grotesk as default "modern" pick | Warm-beige + serif "anti-AI" editorial (reflex #2) |
| Generic Google-Fonts pairing of the month | Glassmorphism cards on gradient mesh |
Prune a lane out once it stops being a reflex; add new families as they saturate. A stale blocklist becomes its own reflex.
Anti-patterns Blocklist
| Anti-pattern | Fix |
|---|---|
user-scalable=no, maximum-scale=1 | Remove — blocks accessibility zoom |
transition: all | List properties explicitly |
outline-none without replacement | Add focus-visible:ring-* |
<div onClick> | Use <button> or <a> |
Images without width/height | Add dimensions (prevents CLS) |
| Form inputs without labels | Add <label> or aria-label |
Icon buttons without aria-label | Add aria-label |
| Emoji as UI icons (🚀 ✨) | Use SVG icons (Heroicons, Lucide) |
| Hardcoded date/number formats | Use Intl.DateTimeFormat |
autoFocus everywhere | Use sparingly, desktop only |
Motion Rules
Animate transform/opacity only — never width/height/top/left. No layout-shifting hover effects. List transition properties explicitly. 150-300ms for micro-interactions. Honor prefers-reduced-motion. Allow animation cancellation — motion must not block user action.
Mode: AUTHORING
Design for user success, not aesthetic preference. Map user flow before writing UI. State order: Error → Loading (no data) → Empty → Success.
Mock-Fidelity Inventory (No Silent Loss)
A build can pass every test and still quietly omit the hero or signature motif. Once a design/mock is approved, before coding, INVENTORY its major visible ingredients:
| Ingredient | Implementation path |
|---|---|
| Hero / focal moment | Build now / phase 2 (explicit) / cut (approved) |
| Signature motifs | Build now / approximate / cut (approved) |
| Sections | Build now / phase 2 (explicit) / cut (approved) |
| Interactions | Build now / static fallback / cut (approved) |
| States (empty/loading/error) | Build now (states are not optional) |
Every ingredient gets exactly one path. "Cut" and "phase 2" are legitimate, but only when explicitly named — never reached by omission. Treat any silently-dropped major ingredient as a P0 fidelity defect.
Design-System Drift Classifier
When a feature deviates from the design system, classify the root cause:
| Root cause | Fix |
|---|---|
| Missing token — system has no value for this need | Add the token to the system, then use it |
| One-off impl — token/component exists, but feature reimplemented locally | Swap to shared component/token; delete the one-off |
| Conceptual misalignment — feature's interaction model fights the system's | Rework the flow — patching pixels won't fix it |
Flow-shape match: a feature's flow shape must match its neighbors. Modal vs full-page, save-on-blur vs explicit submit — inconsistency reads as broken even when every pixel is on-system. Treat unexplained flow-shape mismatch as conceptual-misalignment.
Show full SKILL.md (367 more words)Show less
Mode: CRITIQUE
READ-only. Scores and flags; caller decides what to fix. A design self-graded by the head that built it is not reviewed — it is rationalized.
Two Isolated Assessments + Synthesis
Assessment A — design-director qualitative review. Read the UI as a senior design director would: hierarchy, rhythm, restraint, intentionality. Score the rubric. A forms its opinion WITHOUT running the ban-list scan.
Assessment B — AI-slop / pattern scan. SEPARATE pass walking the ban-list. B must NOT see A's conclusions — give it the artifact, not A's writeup.
Synthesis — reconcile only after both commit. Where A and B independently agree → high confidence. Where B caught what A's eye glossed → keep it. Where B's match is a false positive → drop with one-line reason.
If only one head: run B first (mechanical, no narrative), record it, THEN run A — never the reverse. A's narrative contaminates B; B's list barely colors A.
Anchored 0-4 Rubric
Heuristics: visual hierarchy, visual rhythm & spacing, restraint & intentionality, consistency & system fit, feedback & state legibility, distinctiveness.
| Score | Criteria |
|---|---|
| 0 | Broken or actively confusing |
| 1 | Works but generic and fragile. Template defaults, AI-slop tells |
| 2 | Solid, competent, unremarkable. Most real interfaces live here |
| 3 | Good. Intentional hierarchy, consistent system, distinctive |
| 4 | Genuinely excellent. Every element earns its place. Rare |
| Band (avg) | Action | Severity |
|---|---|---|
| 0 | Do not ship | P0 |
| 1 | Rework before ship | P1 |
| 2 | Ship with noted follow-ups | P2 |
| 3-4 | Ship | P3 (polish only) |
Most real interfaces score 2; anti-grade-inflation is the job.
AI-Slop Ban-List
| Slop pattern | Default verdict |
|---|---|
| Side-stripe / left-accent-border cards | Refuse |
| Gradient text headings | Refuse |
| Glassmorphism by default | Refuse |
| Hero-metric template (stat row) | Refuse |
| Identical card grids (no hierarchy) | Refuse |
| Modal as first-thought container | Refuse |
| Cream + serif + terracotta "editorial" palette | Refuse |
| Black + acid-lime/green accent | Refuse |
A ban-list match is a finding, not an automatic 0 — let synthesis decide severity against A's read.
Optional Deterministic Detector
If an npx slop-detector is configured/available, run it in Assessment B. If not, the ban-list scan runs by hand. Never block on a missing tool, never invent a tool call.
RTL / Hebrew-Aware Notes
When UI is RTL: check mirroring correctness (layout, icon direction, progress/flow), logical properties (margin-inline-start over hard-coded left/right), mixed-direction runs (Latin tokens in RTL text), and typography (missing intentional Hebrew face = distinctiveness gap).
© romiluz13, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file
Files
SKILL.md and 5 other files (references) in plugins/cc10x/skills/frontend of romiluz13/cc10x.
- SKILL.md
- references/accessibility-and-forms.md
- references/design-md-authoring.md
- references/design-md-inspiration-index.md
- references/performance-and-layout.md
- references/ui-state-and-feedback.md
Open the folder on GitHubat commit f346ebe
Compare with similar skills
Frontend next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.
| Skill | Stars | Used in | Tokens | Auto-check | Licence | Repo updated |
|---|---|---|---|---|---|---|
| Frontend this skillromiluz13/cc10x | 164 | — | ~2k | Automated safety check: Notes | MIT | |
| Material Design 3 UI/UX Guideskydashnet/material-design-3-ui-skill | 130 | — | ~3k | Automated safety check: Pass | MIT | |
| UI Design Systemtry-works/role-model | 118 | — | ~5k | Automated safety check: Pass | MIT | |
| Design Handoff Specgetcrew44/crew44 | 356 | — | ~680 | Automated safety check: Pass | MIT | |
| OpenClaw Design Auditopenclaw/clawhub | 9.5k | — | ~498 | Automated safety check: Pass | MIT | |
| Bmad UXaj-geddes/claude-code-bmad-skills | 487 | — | ~2k | Automated safety check: Notes | Custom licence |
Similar skills
UI Design System
try-works/role-model
React UI component systems with TailwindCSS + Radix + shadcn/ui.
Design Handoff Spec
getcrew44/crew44
Produces an implementation-ready spec from a finished design, covering layout, tokens, states, responsive behavior, edge cases, motion and accessibility, so engineers do not have to guess.
OpenClaw Design Audit
openclaw/clawhub
Audits OpenClaw frontend code and rendered pages for token misuse, reimplemented primitives, accessibility and responsive defects and off-brand copy, with an evidence-based report.
Bmad UX
aj-geddes/claude-code-bmad-skills
Solutioning-phase UX planning skill (optional; activate when the project has a UI).
Design Auditor
borghei/Claude-Skills
Audit UI/UX designs for quality, AI-generated slop, and accessibility.
More from romiluz13/cc10x
All 22 skills in this repoBuilding
romiluz13/cc10x
A skill your agent uses when writing production code test-first: the RED-GREEN-REFACTOR cycle, false-RED detection, vertical slicing, scope escalation, test process discipline, and code generation…
Diff Driven Docs
romiluz13/cc10x
A skill your agent uses when a BUILD phase completes, a commit is staged, or a PR is about to be created, and the diff has not yet been reflected in documentation.
Planning
romiluz13/cc10x
A skill your agent uses when writing an execution plan or a decision RFC: task decomposition, context references, validation levels, risk-based testing, ADR format, plan completeness gate, and…
Verification
romiluz13/cc10x
A skill your agent uses when judging whether a task reached its goal, not just finished: the gate function, self-critique gate, validation levels, evidence array protocol, and goal-backward lens.
Agent Common
romiluz13/cc10x
A skill your agent uses when a cc10x agent starts a task: the shared preamble for the memory protocol, the contract format, and the output rules.
Cc10x Guide
romiluz13/cc10x
Answers questions about cc10x itself — what it is, how to install and configure it, how the router, workflows, memory, and hooks operate, and how to troubleshoot.
Related
Categories
Questions about Frontend
What does Frontend do?
Two-mode frontend skill: (1) authoring — accessibility, responsive layout, loading/error states, performance, DESIGN.md authoring, visual direction; (2) critique — READ-only scored review of built…. Frontend is an agent skill from romiluz13/cc10x.md authoring, visual direction; (2) critique — READ-only scored review of built UI against anchored rubric, AI-slop detection, two isolated assessments.
When should I use Frontend?
Frontend fits situations like: tasks that involve Quizzes and assessments; tasks that involve Design tokens; tasks that involve Responsive design.
How do I install Frontend in Claude Code?
Run `npx skills add romiluz13/cc10x --skill frontend -a claude-code`. Or copy the skill folder (plugins/cc10x/skills/frontend in romiluz13/cc10x) into .claude/skills/frontend in your project. Claude Code loads it when a task matches its description.
How do I install Frontend in Codex?
Run `npx skills add romiluz13/cc10x --skill frontend -a codex`. Or copy the skill folder (plugins/cc10x/skills/frontend in romiluz13/cc10x) into .agents/skills/frontend in your project. Codex loads it when a task matches its description.
Can I use Frontend in Cursor, Gemini CLI or GitHub Copilot?
Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add romiluz13/cc10x --skill frontend -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/frontend, .gemini/skills/frontend, .github/skills/frontend and .opencode/skills/frontend in your project.
What does Frontend need to run?
SKILL.md names no scripts, command-line tools or credentials: Frontend is instructions for the agent only. Our summary lists: Node.js. Its frontmatter pre-approves these tools: Read, Grep, Glob, Bash, LSP.
Does Frontend access the network?
SKILL.md contains no URLs. Any network use would come from the scripts or tools the agent runs. This is read from the text; nothing was executed.
Is Frontend safe to install?
Our automated static check of SKILL.md found notes only (pre-approves every shell command (allowed-tools: bash)), nothing it rates as a warning. It is not a guarantee. Review the folder before installing.
What licence does Frontend use?
Frontend is published under the MIT licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.
How many tokens does Frontend use?
About 2k tokens (SKILL.md is roughly 8.1k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full. Its references folder adds about 3.4k tokens, read only when the agent opens those files.
What are the alternatives to Frontend?
Skills that share tags, products or a category with Frontend: Material Design 3 UI/UX Guide (skydashnet/material-design-3-ui-skill, 130 stars), UI Design System (try-works/role-model, 118 stars), Design Handoff Spec (getcrew44/crew44, 356 stars) and OpenClaw Design Audit (openclaw/clawhub, 9.5k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains Frontend?
romiluz13 (a GitHub user) maintains it in romiluz13/cc10x, which has 164 GitHub stars. The repository holds 22 skills in this directory. The repository was last updated on October 7, 2026.
Source: romiluz13/cc10x on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.