Shaping the future of design system features
Defining the nitty-gritty details of how components, variables, and design systems work across the Figma ecosystem, from idea to shipped product.
The "zero-to-one" problem
Every designer has been there: staring at a blank Figma file, knowing they need to set up a design system, but facing hours of tedious work before they can start creating.
Variables need to be created. Component architectures need to be defined. Documentation needs to be written. And all of it needs to follow best practices that most teams don't have time to research.
This is where most design systems die: before they even begin.
How I work
I'm a systems-minded product designer with 5+ years designing intuitive, high-quality UX and UI for complex systems. I don't just design interfaces; I architect experiences that scale.
My approach is rooted in understanding the nitty-gritty details: how variables propagate through component hierarchies, how modes interact with instance overrides, how the design editor connects with the broader Figma ecosystem.
I thrive in ambiguity, working independently to drive projects from exploration through launch, balancing user needs, technical constraints, and business goals.
Systems thinking
I think in patterns, relationships, and scale. Every decision considers how features work holistically across the entire Figma ecosystem.
Craft & detail
I obsess over polished interactions and pixel-perfect visuals. Excellence lives in the hundreds of small decisions that compound into delightful experiences.
Cross-functional leadership
I collaborate closely with engineering, product, and research teams. My technical fluency makes me an effective bridge between design vision and implementation reality.
Spectrum Foundry: one click, infinite possibilities
What if setting up a production-ready design system took seconds instead of days? I built a plugin to find out.
The problem teams face
Picture this: A product team gets excited about using Figma's powerful design systems features (variables, component properties, modes). They've read the docs, watched the tutorials, and understand the potential.
But then reality hits. Before they can build anything, they need to create variable collections for colors, typography, spacing, elevation, motion, shadows, borders, icons... The list goes on.
Each variable needs careful naming. Each collection needs thoughtful organization. Each token needs documentation explaining when and how to use it.
Teams spend days on setup before they can start the work they actually wanted to do.
The solution: design systems in seconds
I designed and built Spectrum Foundry: a one-click plugin that creates complete, production-ready design system foundations instantly. What used to take days now takes seconds.
Comprehensive variable collections
Creates structured collections for every design foundation: colors, typography, spacing, radius, elevation, motion, opacity, layout, icons, shadows, and borders.
Teaching-quality documentation
Generates responsive documentation artboards with instructive specimens showing both the values and exactly how to use them.
Ready-to-use components
Produces component sets wired to variables, demonstrating modern properties, variants, and bindings that teams can copy and extend.
Safe & deterministic
Idempotent variable creation that updates existing files cleanly without duplicates. Run it multiple times, get the same reliable result.
Why this matters
Business impact
Reduces time-to-market by 40% by eliminating foundational setup friction. Instead of spending days creating infrastructure, teams can focus on innovation from minute one.
For organizations, this accelerates workspace expansion, increases feature adoption, and creates a repeatable onboarding asset for enterprise conversions.
Product strategy alignment
Demonstrates the "happy path" for how Variables + Components should work together. The plugin embodies exactly how Figma wants system primitives to power component state and scale across files.
It's a living specification for design systems features, showing how investments in modes, tokens, and component properties translate into real, comprehensible outcomes.
Design value
The curated, opinionated foundations match how designers actually think and how components need to consume tokens. It's pragmatic and legible, not academic.
The presentation teaches by doing: showing elevation applied to surfaces, motion represented with progress visuals, spacing in auto-layout samples. Designers grasp both value and usage instantly.
Engineering excellence
Built with idempotent variable creation, typed token architecture, and clean separation of concerns. The code is maintainable, extensible, and serves as a reference architecture.
It bridges design and engineering by establishing a typed source of truth that enables future code-gen pipelines and platform style dictionaries.
What makes it different
Unlike typical token generators, Spectrum Foundry doesn't just create data; it composes variables into a coherent, pedagogical artifact that teams can adopt immediately.
Shows real variable bindings
Demonstrates padding, corner radius, fills, typography properties bound to variables, turning abstract token theory into living, remixable systems.
Multi-foundation coverage
Goes beyond color and typography to cover elevation, motion, layout, shadows, iconography: the real surface area of system craft.
Executable documentation
Creates documentation that operationalizes strategy, not just data. Teams learn by seeing tokens applied in realistic contexts.
Ecosystem thinking
Built with extensibility for modes, theming, multi-brand systems, and export pipelines. Ready for where Figma is going, not just where it is.
"Spectrum Foundry operationalizes Figma's design systems vision end-to-end: instantly creating structured variables, turning them into understandable artifacts, and wiring them into real components. It's the kind of product-led storytelling that converts curiosity into committed practice."
More systems-oriented work
Enterprise admin tooling & onboarding
Designed comprehensive admin experiences for enterprise organizations (billing systems, user management, workspace configuration). Made inherently complex workflows intuitive through progressive disclosure patterns and contextual guidance.
Component property architecture for design editor
Defined how component properties propagate through nested structures. Designed inheritance models that balance predictability with flexibility, override visualizations that make relationships legible, and error states that guide without blocking.
Design systems features philosophy
Nitty-gritty details matter
Great design system features are built on hundreds of small, thoughtful decisions. I obsess over how variables propagate, how modes interact, how documentation scaffolds understanding.
Thinking across the ecosystem
Features don't live in isolation. I approach problems holistically, considering how components flow between design editor, FigJam, Dev Mode, and beyond.
Systems-minded problem solving
I think in patterns, relationships, and scale. Comfortable navigating ambiguity and synthesizing complex requirements into elegant solutions that work at every level.
Community engagement
The design systems community is a vital partner. I actively gather feedback, understand pain points, and synthesize insights into product strategy that pushes the industry forward.
Core competencies
Design systems features
- • Components architecture
- • Variables & modes
- • Design editor patterns
- • Ecosystem thinking
- • Documentation strategy
Complex systems
- • Admin tooling
- • Onboarding flows
- • Billing systems
- • Access control
- • Multi-tenant architecture
Technical skills
- • Plugin development
- • Prototyping (Figma/code)
- • Design token architecture
- • Component API design
- • Version control
Collaboration
- • End-to-end ownership
- • Cross-functional leadership
- • Clear storytelling
- • Feedback synthesis
- • Community engagement
"The future of design systems lies in the details: in how components understand variables, how modes enable flexibility, and how features work together across the entire ecosystem. Great design systems features don't just enable workflows; they make the complex feel effortless and unlock creativity at scale."
Let's shape the future together
Interested in discussing design systems features, the Figma ecosystem, and how we can build tools that empower millions of designers? I'd love to connect.
