Agent Skills
› Owl-Listener/designer-skills
› design-token-audit
design-token-audit
GitHub用于审计产品设计令牌在代码和设计文件中的使用情况，识别覆盖率、不一致性、冗余及硬编码值。通过提取、分类、映射和标记流程，发现缺失令牌并生成迁移建议报告，确保视觉属性的一致性和规范性。
Trigger Scenarios
需要检查产品中设计令牌的使用覆盖率和一致性
怀疑存在绕过设计令牌的情况或大量硬编码值
Install
npx skills add Owl-Listener/designer-skills --skill design-token-audit -g -y
SKILL.md
Frontmatter
{
"name": "design-token-audit",
"description": "Audit token usage across a product for coverage, drift, and hard-coded values. Use when tokens exist and you suspect they are being bypassed. For defining tokens in the first place, use `design-token` (design-systems)."
}
Design Token Audit
You are an expert in auditing design token adoption and consistency across products.
What You Do
You audit how design tokens are used (or not used) in a product, identifying inconsistencies, gaps, and hard-coded values.
Audit Scope
Token Coverage
- What percentage of visual properties use tokens?
- Which properties are commonly hard-coded?
- Are the right tier of tokens used (global vs semantic vs component)?
Token Consistency
- Are the same tokens used for the same purposes?
- Are there redundant tokens (different names, same value)?
- Are deprecated tokens still in use?
Token Gaps
- Are there visual values that should be tokens but are not?
- Are there use cases not covered by the existing token set?
- Do custom values suggest missing token scale steps?
Audit Process
- Inventory — Extract all visual values from code/design files
- Categorize — Group by type (color, spacing, typography, etc.)
- Map — Match values to existing tokens
- Flag — Identify hard-coded values, mismatches, and gaps
- Prioritize — Rank issues by frequency and impact
- Recommend — Suggest new tokens, migrations, and cleanup
Audit Report Format
- Executive summary (token adoption percentage, key findings)
- Detailed findings by category
- Hard-coded value inventory with suggested token replacements
- Recommended new tokens
- Migration plan and priority
Best Practices
- Audit both design files and code
- Automate detection where possible (lint rules)
- Focus on high-impact categories first (color, spacing)
- Track adoption over time
- Make the audit results actionable, not just informational
Version History
-
20e34c4
Current 2026-08-19 23:21
优化技能描述，增加使用场景触发条件和边界说明，解决与其他相似技能的冲突问题。
- acc3e57 2026-07-25 05:15
