document-a-design-token
Document a reusable design value by semantic purpose, not appearance alone. Use when color, spacing, type, motion, elevation, radius, size, or other decisions must remain consistent across themes and platforms.
소스 정보
- 저장소
- protosphinx/sphinxstack
- 최근 소스 활동
- 2026년 7월 29일 13:55
- 감지된 SKILL.md 언어
- 영어
- 스타
- 3
- 포크
- 0
설치 방법
기본적으로 소스를 먼저 확인하는 Prompt가 선택됩니다. 직접 명령으로 전환하거나 로컬 사본을 다운로드할 수도 있습니다.
소스 파일 검토
설치 여부를 결정하기 전에 SKILL.md와 SkillsMP에 표시된 보조 파일을 읽어 보세요.
파일 탐색기
2 개 파일SKILL.md 표시 중
SKILL.md
소스 지침 · 읽기 전용 미리보기- name
- document-a-design-token
- category
- design
- description
- Document a reusable design value by semantic purpose, not appearance alone. Use when color, spacing, type, motion, elevation, radius, size, or other decisions must remain consistent across themes and platforms.
# document-a-design-token
## Procedure
1. Define the token's semantic job, consumers, platforms, and decision owner.
2. Choose a stable name based on purpose rather than a current literal value.
3. Record value by theme, mode, platform, density, or state where needed.
4. Define allowed uses, prohibited uses, composition, inheritance, and fallback.
5. Link accessibility, contrast, motion, brand, and technical constraints.
6. Add examples and counterexamples in representative components.
7. Specify source format, output mapping, version, aliases, deprecation, and change policy.
8. Test generated values in code and real interface states.
9. Publish migration notes and verify consuming artifacts.
## Guardrails
- Never encode meaning by color alone.
- Do not create a token for a one-off value without a reuse or governance reason.
- Avoid names that become false after a theme change.
## Done
- A token record contains semantics, values, scope, examples, and ownership
- Generated outputs and representative consumers are verified
- Accessibility and deprecation checks pass
GitHub에서 보기