Getting teams to actually use your design system is harder than building it. This handles the adoption side: creating launch strategies, education materials, migration guides, and measuring what's working through component usage and consistency audits. It covers the full spectrum from Figma library setup to tracking adoption metrics to handling the inevitable resistance from teams who think the system doesn't fit their needs. The approach is pragmatic, treating the design system as a product with real users rather than a mandate from above. Use this when you've got components built but adoption is stuck at 30% and engineers keep writing custom CSS anyway.
npx skills add https://github.com/owl-listener/designer-skills --skill design-system-adoption