Soffi (@soffi_dev) header
Soffi (@soffi_dev) profile picture

Where enterprise product teams build together. Prototype, edit, review, and ship on your real product.

San Francisco
Joined October 2025
Photo by Soffi (@soffi_dev)Photo by Soffi (@soffi_dev)Photo by Soffi (@soffi_dev)Photo by Soffi (@soffi_dev)Photo by Soffi (@soffi_dev)Photo by Soffi (@soffi_dev)Photo by Soffi (@soffi_dev)Photo by Soffi (@soffi_dev)Photo by Soffi (@soffi_dev)Photo by Soffi (@soffi_dev)
Engineering team: “We want to actually build this ourselves.” Two weeks later: “Wait, I think this is exactly what Soffi does for us.” youtu.be/D-uxZW4Tbc0?si=Ff-W…
There's an awesome discussion right now about teams building their own prototyping playgrounds so PMs and designers can build freely. I love it. How can we get EVERY product team their own prototyping playground that they don't have the burden to maintain? Building is easy. Keeping it up to date is not. That's why this team came back and said, "I think this is exactly what Soffi does for us."
2
54
I know every founder says this, but this is for real. Designing @soffi_dev with Soffi is the coolest design experience yet. I walk through every role, permission, and broken state on the live product and fix it as I go. Data Twin is the coolest thing we’ve built ❤️
1
2
3
121
The most elegant design is often invisible. The best tools often don't feel like tools. People should be able to work directly on the product they already have, visually, in text, or in code.
Building in Claude or Cursor is the easy part now. Seeing the change on the real product, and getting a PR an engineer can actually review, is still the hard part.
1
1
68
Building in Claude or Cursor is the easy part now. Seeing the change on the real product, and getting a PR an engineer can actually review, is still the hard part.
1
1
144
Everyone sells velocity as the ROI of AI prototyping. But teams tell me they see 20–30% gains with Claude, not 2x. A VC told us about research showing the same: designer-shipped code spiked, then plateaued. Work stays in prototypes, engineers still prefer static files, and it gets handed off again. The fix isn't better prototypes, nor going back to static design files. It's removing the handoff and building on the real product, the way teams like to work: visually and collaboratively. Seeing the change instead of a wall of code.
2
1
1
114
Seeing a failed payment or an empty state usually means pulling in production data, secrets and auth. Soffi reads your code and builds a working twin of your backend instead, with the same API calls, auth and data shapes, so any state renders in your own components.
1
1
1
3
201
What it means for us: an isolated sandbox for every workspace, a data twin that never touches your prod envirnment, every change shipped as a normal PR, and a harness we keep current as models change.
"Why not just build it ourselves?" is a fair question, and plenty of teams try: forked repos for designers, mock data in Storybook, homegrown comment plugins. Building it is easy. Maintaining it, keeping it current, and keeping it secure is the hard part.
1
2
190
Teams write their own as Markdown files: /brand-review for voice and visual choices, /accessibility-check for contrast, keyboard navigation and type size, /break-my-ui for long strings, empty states and overflow, and /pre-ship for your checklist before a screen is done.
1
13
Every Soffi organization starts with /design-system-review. It checks UI code against your own tokens and components and flags hard-coded values and hand-rolled components, with evidence.
1
25
Most design system standards live in people’s heads, so they get repeated in every request or caught in review. Skills in Soffi turn them into playbooks anyone on the team can run with a command.
1
1
2
60
Engineers: "We're scared of designers shipping PRs." Designers: "Have you seen your AI-generated PRs?" Fair on both sides. The solution? Guardrails, reviews, and better systems.
1
1
1
1
307
Your PR says 240 files changed, 12,000 lines. Nobody is manually reviewing that. So it gets approved on trust, and whatever happened to the UI ships unlooked at. Or someone pulls the branch, runs it locally, gets the setup right, and hunts for the screen that actually changed. Soffi deploys both versions of your app, the pull request and its base branch, then screenshots every page the change touches on each. Real deployments, not renders. So a reviewer can see the change in seconds instead of pulling it down, and nobody merges a UI change they never saw. On by default for PRs you ship from Soffi. An Admin can turn it on for PRs opened anywhere else.
1
1
1
130
3 designers. 3 prototypes. 0 shared source of truth. AI made everyone faster individually. Now who's putting it all back together? It's time for multiplayer AI. Full episode here: youtu.be/D-uxZW4Tbc0?si=Ff-W… 2 impressions
2
1
141
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…
3
6
546