design-systems

Name: design-systems
Author: refoundai

Framework-based guidance for building and scaling design systems from product leaders at Figma and Airbnb. Covers four core principles: separating conceptual design from production output, leveraging design systems for organizational scaling, creating self-teaching assets, and evolving beyond flat design toward dimensional interfaces Provides assessment questions to determine scope (component library, tokens, documentation), adoption strategy, and success metrics Flags common pitfalls including premature systematization, over-engineering for non-designers, lack of ownership, poor adoption, and treating systems as static rather than evolving Guides users through staged rollout, from defining the smallest viable version to planning long-term maintenance and evolution

INSTALLATION

npx skills add https://github.com/refoundai/lenny-skills --skill design-systems

Run in your project or agent environment. Adjust flags if your CLI version differs.

SKILL.md

$2a

Design systems drive enterprise expansion

Claire Butler: "Design systems are one of the main reasons you upgrade from pro to org or enterprise. That became just the key thing we leaned in on." Design systems practitioners are key internal champions for organizational scaling.

Assets should teach their own usage

Jessica Hische: "My goal always when designing a logo is to design a logo that's so easy to use that you don't have to be an extremely skilled designer to design well with it." Design assets that 'teach' the user how to apply them through their inherent structure, prioritizing ease of use over complexity.

Flat design is evolving

Brian Chesky: "I think flat design is over or ending. We're going to move back into a world with color, texture, dimensionality, more haptic feedback." Interface design is shifting from flat aesthetics to more dimensional, tactile, and AI-enhanced experiences.

Questions to Help Users

"What's the biggest inconsistency problem you're facing today?"

"Who will be using this design system - designers only, or engineers too?"

"How will you measure adoption and success of the design system?"

"Do you have the resources to maintain and evolve the system over time?"

"What's the smallest viable version you could ship first?"

Common Mistakes to Flag

Building too early - Creating a design system before you have enough patterns to systematize

Over-engineering - Building complex systems that require expert designers to use correctly

No ownership - Creating a design system without dedicated resources to maintain it

Ignoring adoption - Building a beautiful system that no one actually uses

Static systems - Treating the design system as 'done' rather than continuously evolving

Deep Dive

For all 4 insights from 4 guests, see references/guest-insights.md

Related Skills

Running Design Reviews