Sumit K retweeted
The best part. You can just plug it into your backend.
usetulip.co
The best part. You can just plug it into your backend.
usetulip.co
Took a sloppy AI-generated dashboard and asked usetulip.co to give it some soul.
Same layout. Same data. Now it actually looks like a product.
Zero cleanup after.
Every startup is a restaurant.
The kitchen (your backend) is spotless. Great chefs, great food.
The dining room (your frontend) was decorated by five different people who never met.
Tulip gives the dining room one look and hooks it straight up to your kitchen.
Plug and play. usetulip.co
That’s the gap. Code generation got 10x faster. Context delivery didn’t move at all.
The person with the taste is still copying it in by hand, one prompt at a time.
Better prompts won’t fix this. The fix is to treat taste as infrastructure:
• Approved tokens and components in one source of truth
• Streamed into the IDE over MCP
• Checked at the PR, not caught by eye three weeks later
That’s what I’m building with Tulip, the design layer for AI-driven software.
Human-approved tokens go straight into Cursor and Claude Code. The agent stops guessing.
Private cohorts open now → usetulip.co
What actually happens on a client project:
• Brand rules live in a Figma file nobody opens
• Component decisions live in Slack threads
• The real spec lives in one designer’s head
The agent sees none of it.
I’ve been shipping production UI for clients as a #designer. Not handing off Figma files: merging PRs.
The hard part was never the code. It was the context.
Cursor and Claude Code changed who can ship. A designer with taste and an agent can take a screen from idea to merged in an afternoon.
But every session the agent starts from zero. It doesn’t know your tokens, your components, or the 40 decisions you made last month.
Introducing Tulip, the design layer for AI-built software.
Tulip turns your brief into a governed design system that stays in sync across Figma and code, then pushes it straight into your agents via MCP.
Taste infrastructure for a world where AI writes the UI.
usetulip.co
We decided to close down #Fozo, and honestly, it was one of the hardest decisions I've had to make.
Building in this space taught me so much about execution, grit, and product than any textbook ever could. I’m deeply grateful to everyone who backed us, tried the product, and rooted for us along the way.
Closing that chapter gave me the room to step back, recharge, and start building again with fresh clarity.
Tomorrow, I’m sharing what’s next. Stay tuned.






