design-system-adoption
This skill helps teams drive design system adoption by creating comprehensive strategies that span awareness, education, enablement, and incentives. It provides frameworks for measuring adoption success through production metrics and identifying common barriers like incomplete documentation or overly rigid components. Use it when launching a design system, struggling with team uptake, or needing to overcome resistance through data-driven approaches and community engagement.
git clone --depth 1 https://github.com/Owl-Listener/designer-skills /tmp/design-system-adoption && cp -r /tmp/design-system-adoption/designer-toolkit/skills/design-system-adoption ~/.claude/skills/design-system-adoptionSKILL.md
# 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
Facilitate structured design critiques with clear feedback frameworks and actionable outcomes.
Identify, categorize, and prioritize accumulated design inconsistencies and structural problems across a product.
Communicate design's contribution to business and user outcomes in terms that resonate with stakeholders.
Create QA checklists for verifying design implementation accuracy.
Establish design review gates with criteria, checklists, and approval workflows.
Plan and facilitate design sprints from challenge framing through prototype testing.
Create developer handoff specifications with measurements, behaviors, assets, and edge cases.
Design team workflows covering task management, collaboration rituals, and tooling.