SECURITY REVIEW
Not yet assessed
Review the original instructions and requested permissions before installing.
No security review is available for this catalog entry yet.
Design · Business · Documentation / AGENT SKILL
design-system-adoption
0
Develop adoption strategies and enablement materials to increase design system usage.
Create adoption strategy and enablement materials to drive design system usage. Use when the system exists but teams ignore it. For contribution and versioning rules, use `design-system-governance` (design-systems).
Understand the trade-offs.
SKILL QUALITY
Not yet assessed
How clearly the skill guides your agent, how complete its workflow is, and how you can check the outcome.
No quality assessment is available for this catalog entry yet.
The full skill.
Original instructions from the publisher’s SKILL.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
Skill folder
Files included alongside SKILL.md in the publisher’s repository.