Agent Skills
› Owl-Listener/designer-skills
› naming-convention
naming-convention
GitHub用于建立设计系统组件、Token 和文件的命名规范，确保名称可预测、一致且可扩展。适用于解决命名不一致或制定新规则的场景。
触发场景
建立新的命名规范
修复命名不一致问题
安装
npx skills add Owl-Listener/designer-skills --skill naming-convention -g -y
SKILL.md
Frontmatter
{
"name": "naming-convention",
"description": "Establish naming rules for components, tokens, and layers with patterns and worked examples. Use when names are inconsistent or being set. For what the tokens actually contain, use `design-token`."
}
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
版本历史
-
20e34c4
当前 2026-08-19 23:20
技能描述已优化，增加了使用触发条件和边界说明，并解决了与其他技能的冲突问题。
- acc3e57 2026-07-25 05:15
