owl-listener/naming-convention
design-systems/skills/naming-convention/SKILL.md
Establish a naming convention system for design elements, components, and tokens with clear rules and examples.
$ install --global
skillsauthnpx skillsauth add owl-listener/designer-skills naming-conventionInstall this skill globally with one command. Works with Claude Code, Cursor, and Windsurf.
Security Scan Results
3 of 9 scanners reported clean
Some scanners were skipped, did not run, or reported a non-clean status. Review each row below.
3
Scanners Passed
9
Scanners in report
Clean
TrivyContainer and dependency vulnerability scanner
95%
Clean
SemgrepStatic code analysis for vulnerabilities
95%
Clean
mcp-scan (Snyk)Model Context Protocol security validation
95%
Skipped
Snyk (dep)Open source security scanning
50%
Skipped
Socket.devSupply chain security analysis
50%
Skipped
VirusTotalMulti-engine malware detection
50%
Skipped
CrowdStrikeAdvanced threat intelligence
50%
Skipped
OSV-ScannerOpen Source Vulnerability database check
50%
Skipped
OWASP Dep-Check
50%
Last scanned: May 15, 2026, 5:27 AM245.1s1 file scanned
SKILL.md
- name:
- naming-convention
- description:
- Establish a naming convention system for design elements, components, and tokens with clear rules and examples.
Naming Convention
You are an expert in creating clear, scalable naming systems for design assets, components, and tokens.
What You Do
You establish naming conventions that make design systems predictable, searchable, and maintainable.
Principles
- Predictable 2. Consistent 3. Scalable 4. Scannable 5. Unambiguous
Patterns
- Components: [category]/[name]/[variant]/[state]
- Tokens: {category}-{property}-{concept}-{variant}-{state}
- Files: [type]-[name]-[variant].[ext]
- Design files: Numbered + descriptive pages, PascalCase components
- Code: kebab-case CSS, PascalCase React, camelCase props
- Assets: icon-[name]-[size], illust-[scene]-[variant]
Common Pitfalls
- Abbreviations only the author understands
- Inconsistent separators
- Names based on visual properties instead of purpose
Best Practices
- Document rules in a single reference page
- Automate name linting
- Use prefixes for sorting and grouping
- Review names in team critiques
Related Skills
owl-listener/critique-visual-hierarchy
tools
VerifiedTrustedCommunity
Critique a screen's visual hierarchy — entry point, eye flow, weight distribution, and emphasis.
1,265SKILL.mdUpdated May 15, 2026
owl-listener/critique-typography
tools
VerifiedTrustedCommunity
Critique a screen's typography — scale usage, readability, consistency, and token compliance.
1,265SKILL.mdUpdated May 15, 2026
owl-listener/critique-composition
testing
VerifiedTrustedCommunity
Critique a screen's composition — balance, whitespace, rhythm, and gestalt principles.
1,265SKILL.mdUpdated May 15, 2026
owl-listener/critique-brand-consistency
data-ai
VerifiedTrustedCommunity
Critique a screen's brand consistency against mood.md, voice.md, and tokens.md.
1,265SKILL.mdUpdated May 15, 2026