create-a-component-inventory
Inventory repeated interface patterns, variants, states, implementations, and ownership. Use when a product needs evidence for consolidation, design-system planning, accessibility repair, or migration scope.
来源信息
- 仓库
- protosphinx/sphinxstack
- 最近来源活动
- 2026年7月29日 13:55
- 检测到的 SKILL.md 语言
- 英语
- 星标
- 3
- Forks
- 0
安装方式
默认使用会先检查来源的 Prompt；你也可以切换为直接命令，或下载本地副本。
检查来源文件
决定是否安装前，请先阅读 SKILL.md，以及 SkillsMP 当前展示的配套文件。
文件资源管理器
2 个文件正在显示 SKILL.md
SKILL.md
来源说明 · 只读预览- name
- create-a-component-inventory
- category
- design
- description
- Inventory repeated interface patterns, variants, states, implementations, and ownership. Use when a product needs evidence for consolidation, design-system planning, accessibility repair, or migration scope.
# create-a-component-inventory
## Procedure
1. Define products, platforms, repositories, routes, libraries, states, and date of observation.
2. Collect components from code, design files, screenshots, rendered pages, and usage telemetry.
3. Group by user purpose before visual similarity.
4. Record name, source, owner, consumers, variants, states, behavior, accessibility, tokens, dependencies, and status.
5. Preserve near-duplicates until behavior and contracts are compared.
6. Flag orphaned, conflicting, inaccessible, unowned, deprecated, and one-off patterns.
7. Link representative live examples and implementation references.
8. Propose adopt, align, merge, replace, retire, exempt, or investigate with impact.
9. Have design and engineering owners verify a sample and disputed groups.
## Guardrails
- Do not infer usage from design files alone.
- Keep private routes and security-sensitive details restricted.
- Similar appearance does not prove interchangeable behavior.
## Done
- A component inventory lists evidence, consumers, states, owners, and decisions
- Code, design, and rendered samples are reconciled
- Duplicate and retirement proposals have verified impact
在 GitHub 查看