← Work

Research · 2025 to 2026

Teaching AI a Design System

A year building an AI design system taught me the machine could match the surface and never the system underneath. The harder problem was the one it left behind: when a senior person leaves, the judgment they carry leaves with them.

Role
Creator and primary researcher
Organization
Oracle
Moonbird workflow diagram: design system, accessibility, regulatory, and health domain inputs feeding a vector database, then flowing through Figma Make, VS Code, and Oracle JET into production code.

This project started as a defense to a hypothetical situation: A PM uses Figma Make to create a product workflow that looks like Oracle Redwood (but isn’t) and ships it to engineering, without design ever seeing it.

The best way to stop off-system work would be to make the system available to everyone. If a design system’s rationale was machine accessible, then a PM generating a screen would be working from the same thing a designer works from.

I worked toward designing a knowledge layer that lived outside specific design tools, so anything generating a screen could query the design rationale instead of guessing at it.

The architecture I designed for Oracle isn’t the one I’d prescribe for anyone else. In fact, I don’t think there is a one-size-fits-all solution to this particular problem.

Then the layoff came, and slowing down was what let me see straight. We’d been moving so fast that none of us caught the holes in our own thinking. We’d been satisfied that pulling from the written docs was enough.

When any person leaves, their institutional knowledge leaves with them. Most of what they knew was never written down, and the part that wasn’t is usually the part that corrects what was.

The knowledge in layers, each owned by the people who produce it.

The plain version of this idea is that you capture what’s in people’s heads before they leave, before they quit or get walked out. Said out loud, it lands somewhere between pragmatic and dystopian, and I’ve never fully made peace with which. The benefit of better context is real, but I can’t pretend the other edge isn’t there. Forcing what’s in someone’s head out into the open, so a company keeps it after the person is gone, is useful but far from settled. The bigger parts of this need to be answered by laws and labor norms and voting, not by designers and engineers.

More case studies