/system-benchmark
Benchmark your design system across 12 scored dimensions
$ npx -y skills add murphytrueman/design-system-ops --agent claude-codeShips with design-system-ops. Installing the plugin gets this command.
How it fires
How this command gets triggered: by you, by Claude, or both.
- Fires itselfClaude auto-loads it when your prompt matches the work.
- You can call itInvoke it directly when you want it.
- Slash command
/system-benchmark
Context preview
What this command does when you run it.
Benchmark your design system across 12 scored dimensions
Command definition
system-benchmark.mddescription: Benchmark your design system across 12 scored dimensions allowed-tools: Read, Write, Grep, Glob, Bash(cat:*), Bash(find:*), Bash(head:*), Bash(ls:*), Bash(sort:*), Bash(tail:*), Bash(wc:*)
Run the system-benchmark skill against the user's design system.
Load the system-benchmark skill from ${CLAUDE_PLUGIN_ROOT}/skills/system-benchmark/SKILL.md and follow its complete workflow.
If the user provided a file or directory path as an argument, use that as the system root: $ARGUMENTS
If no argument was provided, search the codebase for package.json, component directories, token files, and documentation to identify the system boundaries.
Before starting the benchmark, read the knowledge notes declared in the skill's frontmatter `references:` field, located in ${CLAUDE_PLUGIN_ROOT}/knowledge-notes/.
Produce the full benchmark report including: 12-dimension scores across 4 pillars, percentile positioning, pillar analysis, and improvement recommendations.
Claude Code skills for the work that keeps a design system alive.
Repo: murphytrueman/design-system-ops
Other commands on design-system-ops.
- /cicd-integration
Generate a CI/CD pipeline for design system quality checks
Open command - /codemod-generator
Generate a migration codemod with tests and rollback plan
Open command - /component-audit
Audit your component library inventory
Open command - /describe-component
Generate an AI-optimised component description
Open command - /docs-coverage
Audit whether your documentation surface keeps pace with your components
Open command - /drift-check
Detect where teams are diverging from the system
Open command

