Naming Audit

by murphytrueman

Naming Audit is a Quality skill for Claude Code, published by murphytrueman in design-system-ops.

176 stars7 forkson murphytrueman/design-system-opsAdded 2026/09/07+1% in starsRepository updated 2026/08/22

View source on GitHub Download repo ZIP

claude-codeclaude-code-plugindesign-systemdesign-systemsdesign-tokensfigmaskills

Install in seconds

Install Naming Audit

Copy Naming Audit into your Claude Code skills folder. Run the command in your terminal, or review the source on GitHub before installing.

terminal

npx degit https://github.com/murphytrueman/design-system-ops/tree/main/skills/naming-audit ~/.claude/skills/naming-audit

Requires Node.js. Downloads this skill only — not the rest of the repository — into your Claude Code skills folder.

Without Node.js

git clone https://github.com/murphytrueman/design-system-ops.git

Clones the whole repository, then copy the skill’s own directory into your skills folder yourself.

In this catalog

Source file: skills/naming-audit/SKILL.md in murphytrueman/design-system-ops
Installs to: ~/.claude/skills/naming-audit
Collection: One of 25 skills cataloged from this repository
Category: Quality — 1817 skills

What Naming Audit does

Naming Audit checks design system components, tokens, and patterns for consistency, ambiguity, and clear purpose. Use it when you need a naming review or want to find inconsistent names and rename candidates.

Naming Audit is cataloged under Quality on DirSkills. Naming Audit comes from a repository tagged claude-code, claude-code-plugin, design-system, design-systems and design-tokens.

Documentation

README

Excerpt

Naming audit

A skill for auditing naming conventions across a design system's components, tokens, and patterns. Produces a violation report with specific examples, ambiguity flags, and rename suggestions with rationale.

Context

Naming is the primary interface between a design system and its consumers. A name is the first piece of information a designer or developer gets about what a component does, what a token means, or how a pattern behaves. Good names are predictable: consumers can guess what a name refers to before they look it up. Bad names require lookup, then clarification, then occasionally a conversation to confirm what was meant.

This is the opening of the README. Read the full README on GitHub.

Frequently asked about Naming Audit

What else does murphytrueman publish alongside Naming Audit?
Naming Audit is one of 25 skills that DirSkills catalogs from murphytrueman/design-system-ops, the repository it ships in. Its siblings there include AI Component Description, Accessibility Per Component and Adoption Report. Each one is a separate skill with its own page in this directory, installs the same way Naming Audit does, and is maintained by murphytrueman in that same repository. The rest of the collection is listed on the murphytrueman/design-system-ops page.
How does Naming Audit compare to other Quality skills?
Naming Audit ranks #1703 by stars among the 1817 Quality skills in this catalog. The most-starred ones next to it are Benchmark, Benchmark Optimization Loop and API Design Patterns. DirSkills ranks by the star count of the repository each skill ships in, so that order reflects how popular those repositories are rather than any review of Naming Audit against them. Open each page to compare what they document and how they install.