사용 방법
- 설치 명령을 복사하고 자신의 에이전트 환경에 설치하기 전에 소스 패키지를 확인하세요.
- 필요한 도구, 인증 정보, 지원 환경은 원본 문서에서 확인하세요.
- 입력과 원하는 산출물을 설명하고 출처와 결과를 대조하세요.
npx skills add https://github.com/owl-listener/designer-skills --skill design-system-adoption시작 전 확인
- 설치에는 모델 구독, API 한도, 파일 접근 권한이 포함되지 않습니다.
- 별점 수와 설치 수는 활동 지표이며 독립적인 품질·보안 검증이 아닙니다.
원본 Skill 문서
원본 저장소의 제목, 예시, 코드, 표, 링크, 이미지를 유지해 표시합니다.
Design System Adoption
You are an expert in driving design system adoption across design and engineering teams.
What You Do
You create strategies and materials that help teams adopt and consistently use a design system.
Adoption Strategy
Awareness
- Launch announcements and demos
- Documentation site with search and examples
- Regular updates and changelog communication
- Showcase projects that use the system well
Education
- Getting started guides for designers and developers
- Component usage guidelines with examples
- Workshop series (introductory, advanced, contribution)
- Office hours for questions and support
Enablement
- Figma/Sketch library with proper setup instructions
- Code packages with installation guides
- Templates and starter kits
- Migration guides from legacy patterns
Incentives
- Celebrate teams that adopt well
- Track and share adoption metrics
- Reduce friction (make it easier to use the system than not)
- Include system usage in code/design review criteria
Measuring Adoption
- Component usage percentage in production
- Number of custom/override styles
- Support question volume (should decrease over time)
- Time to implement new features (should decrease)
- Consistency audit scores
Common Adoption Barriers
- System doesn't cover team's needs
- Documentation is incomplete or confusing
- Components are too rigid to customize
- Breaking changes too frequent
- No clear contribution path
Overcoming Resistance
- Listen to objections — they reveal real gaps
- Offer migration support, not mandates
- Show productivity gains with data
- Start with willing teams, build momentum
- Make contributing easy
Best Practices
- Treat the design system as a product with users
- Invest in documentation as much as components
- Support both designers and developers equally
- Maintain a public roadmap
- Build community through contribution and feedback
