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
- 포크
- 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에서 보기