I replaced a year-long design-system program in two weeks
Quicknode spent more than a year and hundreds of thousands of dollars on an unfinished system. I rebuilt it solo as MeridianDS: an agentic, multi-platform ShadCN Premium monorepo with roughly 800 components and variants. Q, Quill, and Earn use it in production.
A design system that ships the product with the component
Designers review in Storybook. Engineers import from npm. Agents load component skills. One contract carries web, desktop, chat, and marketing.
1+ year
Previous program
Still incomplete after roughly 10 contributors
2 weeks
MeridianDS core
Designed and built solo from zero
~800
Components and variants
Organized in one multi-brand monorepo
3 live
Production consumers
Q, Quill, and Earn
The company had already paid for the hard way
Roughly 10 people, more than a year, and hundreds of thousands of dollars still left Quicknode without a finished system. Accessibility and chat remained unresolved. Every new product created another exception.
Two weeks from blank foundation to production consumers
Week one established the monorepo, foundations, packages, API, and Storybook. Week two added product patterns, icons, motion, chat, skills, accessibility gates, and consumer integrations.
- Before
A year-long system was still incomplete
Roughly 10 people had touched the effort, but product teams still lacked one foundation for chat, native, web, and agent-assisted delivery.
- Week 1
Build the product foundation
I created the multi-brand monorepo, six-package architecture, semantic foundations, core component API, theming, and Storybook.
- Week 2
Connect the system to real work
I added chat patterns, technical icons, motion, skills, accessibility gates, npm delivery, and the first product integrations.
- Now
Run it in production
Q, Quill, and Earn consume the system. MeridianOS and the new Quicknode marketing site are in active integration.
I bought the commodity layer and built Quicknode's advantage
ShadCN Premium solves common controls and compositions. I spent two weeks on Quicknode's advantage: brands, technical icons, chat, motion, responsive behavior, agent instructions, and delivery.
One component ships four ways
Every component becomes product code, a Storybook proof, an agent skill, and a tested contract. One source change reaches all four.
I was the product team
I owned strategy, design, frontend, backend, package architecture, Storybook, skill generation, quality gates, and integration. End-to-end ownership made the two-week build possible.
Confidential client work
Some client studies include confidential product detail. Enter an access code to read them.