Industry
FinTech
Company
TILT
Turning product requirements into interactive prototypes.
Why I built it
What if product documentation wasn't something teams read, but something they experienced? I began experimenting with AI-generated prototypes to replace static artifacts with interactive software that people could explore, test, and react to. The goal wasn't to prototype faster. It was to create a better way for teams to communicate, collaborate, and make product decisions. Experience the prototype below. This interactive prototype was generated from product requirements, reference designs, and a design system using Claude-assisted workflows.
Built With:
Claude Design
Figma
Linear
Illustrator
The Shift
Instead of aligning around static screens, I explored a workflow where product teams collaborated around functioning prototypes generated through a combination of Linear tasks, Figma systems, and Claude-assisted development.
What I Built
• Linear task → prototype workflows • Low-fidelity interaction concepts • High-fidelity production-like prototypes
• Reusable design patterns powered by Claude • Living documentation for product discussions • Shared experiences for design, product, and engineering teams
What happened
I successfully translated product requirements into interactive prototypes that accelerated conversations, reduced ambiguity, and allowed stakeholders to experience ideas instead of interpreting them. There was a noticable shift were teams aligned faster around working software than static documentation.
What I learned