Connecting design systems to AI-ready product development
Closing the gap between design intent, prototypes, and production code.
AI tools can generate concepts quickly. But speed at the start of the process does not guarantee that a concept can become maintainable product code. When Figma, the design system, Storybook, and application code are disconnected, teams can lose track of which decisions are current and how a prototype should translate into production.
I argued for treating the design system as part of the prototyping workflow, not a library teams consult only after exploration. I advocated for stronger links between design files and code, including Storybook and MCP work, and for better traceability as designs and implementations change.
I also proposed connecting PRDs, prototypes, component usage, and the content playground into a workflow that teams could measure. Useful measures included time to ship and prototype-to-code conversion. Those measures would show whether the process was helping teams move ideas into production, not simply generate more concepts.
The focus was on building the foundations for AI-assisted product development: reusable components, clear records of decisions, and a more direct path from an idea to working software.