Where enterprise product teams build together. Prototype, edit, review, and ship on your real product.
San Francisco
Joined October 2025
- Tweets114
- Following102
- Followers84
- Likes59
Soffi retweeted
Building @soffi_dev with Soffi gets pretty meta.
Today I showed @brayden_love a new design context feature I'd barely tested. We taught Soffi a design rule, tried to break it, found some bugs, and attempted to ship a PR.
All recorded. Nothing scripted.
Behind the Build: youtube.com/watch?v=hoMS1cwE…
Soffi retweeted
I've been obsessed with the PR.
PMs and designers want to ship the real change. Engineers want something they can actually use. A prototype is neither.
So we built the PR engineers want to merge and PMs and designers can contribute to:
Before and after screenshots of every change. Not renders.
A backend requirements section with every API call an engineer or their agent needs.
A Data Twin per workspace, so you can test any state without touching production.
Nobody manually reviews a 10,000 line diff. Now you don't have to.
Full release: soffi.ai/docs/reference/chan…
A diff tells you which lines changed. It doesn't tell you what happened to the screen.
Reviewing a UI change means pulling the branch, running it locally, hunting for the state that changed. About an hour before you can even look.
Read more: soffi.ai/docs/changelog
And you can open any PR in Soffi and see it running. Comment on the page, or fix what's off and push it back.
The PR engineers want to merge, and PMs and designers can contribute to.
Also shipped: Skills, so Soffi follows your team's playbooks. And a Data Twin for every workspace, so anyone can test any state without production data.
~~Full update: soffi.ai/docs/reference/chan…~~
AI was supposed to mean less work. "It's making work more work."
Not more hours. More of the work outside your old role. @crisdobbins on why that's the point.
Ask Soffi for a viewer on an expired plan, an account with 300 invoices, or the sync that failed halfway, and your live product renders it in seconds.
Our founder, @crisdobbins wrote about what it's like to design this way:
Canvas vs. IDE is the wrong debate for designers on complex B2B products. The real problem is we’ve never been able to see every state. Now I design on my live product with mirrored data, ask for any role, error, or edge case, and see it in seconds.
I wrote about what it’s like to design this way: crisdobbins.substack.com/p/t…
Designers shouldn't have to become engineers and use an IDE to build with AI. They need AI tools that speak their language, too.
"A lot of people are making tools for AI, instead of actually making tools that use AI for humans." @crisdobbins on Soffi Sessions:
Watch here: youtu.be/HgnVaDVFLpc
Designers shouldn't have to become engineers to build with AI.
"A lot of people are making tools for AI, instead of actually making tools that use AI for humans." @arushij93 and @crisdobbins on Soffi Sessions:
Full episode 👉 youtu.be/HgnVaDVFLpc
+100 to all of this, even better when it runs on your real product and you can see and interact with it live
Things you can use Al for when working on UI:
- ask it to try and break the stuff you built
- let it create state machines to check different scenarios (success, error, different user roles, etc.)
- when finished, ask it to make before/after screenshots
- make it ask you lots of questions about the thing you are working on to validate the idea
- let it create a few variants of a Ul piece so you can try it out
- setup loops to maintain a quality bar by constantly monitoring
Her title: product designer.
Her GitHub: Go and agents.
“It’s not that the titles need to change, but our perception of them needs to change.”
@crisdobbins on Soffi Sessions: youtu.be/HgnVaDVFLpc
Design is NOT dead.
Anyone can generate an interface now. Designing a great experience still takes empathy, systems thinking, and taste.
Introducing Soffi Sessions 🎙️
In our first episode, our Founder & CEO @crisdobbins shares why design isn't disappearing. The canvas is just getting bigger.
Watch 👇