Design System Adoption — Designer Skills

When to use it

Provide current libraries, documentation, team obstacles and adoption evidence. Produces onboarding, migration and measurement recommendations, not a new component library. Distinct from governance rules or documentation templates: its focus is helping teams adopt existing assets. Proposed productivity gains and adoption measures require real instrumentation and validation. Upstream reviewed; not installed or runtime-tested. GitHub stars are repository-wide, not skill-specific.

Compatible agents

Claude CodeGemini CLI

Installation

In Claude Code, run /plugin marketplace add Owl-Listener/designer-skills, then /plugin → Discover and install designer-toolkit. Ask the agent to use design-system-adoption. Gemini CLI extension installation is also documented in the repository README.

Review the source and instructions before installing in your agent.

License

MIT

Last checked Oct 17, 2026.

Pair this skill with a visual reference

A skill guides how your agent works; a design reference shows the direction you want. Choose an example for a specific job, such as the headline hierarchy or form layout, and keep your project's existing design rules explicit.

Start with design references you can inspect, then use our guide to briefing an AI coding agent to turn observations into requirements. If you need implementation components, compare UI libraries for your stack.

These pages are public. Browsing a skill does not install it, and TastefulKit's design-reference MCP tools do not search the AI-skill directory.