traditional designers are the new flash designers. the only way forward is designing in code with bias to shipping

the 2 biggest complaints in software design in the past 6 months: 1. not being able to share prototypes with colleagues, users or stakeholders, and 2. joining the infamous club of people sharing localhost links sharing is one of the most beloved features of @modeinspect, we built it early on, and it's super basic too! we're now kicking off a new wave of updates to sharing and collaboration, so you don't have to record videos or get eyeball emojis on your localhost slack messages. here's the first one: sharing a specific page of your prototype, interactions included, with anyone.

vibe coding broke slow is smooth, smooth is fast. we see many product teams going fast without going slow first, designers, PMs, engineers, everyone ships. this is great, if components, tokens, design system are in a place which the whole team draws from. the velocity without the fundamentals is like swimming fast without a good form, works great in the first 10 seconds, falls apart shortly after. in teams we see this creating a drift that slowly grows. every screen is a little different, every fix is a rebuild. customers complain, six months in, "fast" is gone.

new corporate benefits have arrived

the best craftsmen and artists in the past didn't do design QA or handovers. the holy grail of product design is crafting designs directly in code. Effortlessly, visually, without technical and non-technical frictions.

we're rolling out @modeinspect 1.0. design canvas, code and agents, all in one place. we've built a delightful experience for designing in code; canvas to code = one-shot, 1:1 component adherence, shipping PRs and sharing your work is only 1 click away. design engineering is back!

Dyson built 5,127 prototypes with his own hands. so why did we ever accept that designers don't build? on the return of design engineering in the era of AI.

a hack for design engineers tired of the 60% fidelity: everyone tried to bridge design <> code. design.md files, MCP servers, hours of agent prompting, you still end up babysitting the output. the actual fix is boring: stop describing components to the agent, hand it the real one, the way you're already used to in canvas. find the component in your library → drop it onto a captured frame of your live product → edit on canvas → ship it back as production code. Full fidelity, zero prompting theater. (this is in Modeinspect now, but the principle works anywhere: real components beat descriptions of components, every time.)

if you're learning git, code or devops as a designer, you wasting your time. setting up MCP servers, sharing your prototypes via git or fixing stuff directly in code will soon be a thing of the past. AI will have a hard time replacing craft if that's what you're great at. All the things above will be handled by actual design engineering tools.

Voice dictation to the AI agent is live! Design with your voice and build back to code in one-click.

they say the look of an office is a reflection of its culture. And since design is our passion, here are our new decorations to keep our engineers in line.

Design is dead. Design engineering is being born. Design engineering is going from an idea to pull request without the traditional design handoffs. Manipulating code with agents and visual controls, shipping production grade PRs. Here's the whole thing: 1. open the canvas - your codebase is wired straight into it. 2. grab a real component from the code, bring it to canvas. 3. tweak it visually. Resize, restyle, drag stuff around like in figma. 4. feeling lazy? Just prompt the agent: "make this top bar convert better" → done 5. preview live 6. check the diff, open a PR. no handoff, no rebuilding designs in code, no slack thread about a hex value. here's the part that breaks people's brains: the canvas and the code are the same thing. You're not designing a picture of the product, you're designing *the* product. that's the new design process without the translation tax. Once you work like this, going back feels ridiculous. Recorded the full loop on an example codebase, video below. try not to think about all the handoff meetings this replaces :)

Modeinspect Early Access Alpha is live. Most AI design tools start with a blank canvas. We built Modeinspect for the product you already have. Real UI. Real codebase. Real components. Real design system. Design visually on the actual product, share a live prototype, and turn the best changes into PRs for engineering review. Designers make the change visually. Engineering gets a PR, not another mockup to decode. If you’re working on real product UI and want to try the alpha, come build with us. go.modeinspect.com/hello-wor…

the new kind of morning technical standup: you can only talk as long as you hang. we’re hiring, in case you’ve got good grip strength..

engraved on every circuit board

If what you care about is high-fidelity, production quality visuals with adherence to your design system when prototyping with AI, using design.md is like carving sculptures with a sledgehammer.

I have yet to see an "it's over for designers" post about something like the recent Stitch launch that was actually written by a *designer*. tells you exactly where we are in the hype cycle..

We have released a great deal of updates recently focused around the design QA experience and extending design controls that enable our customers get to production quality 🚀 ✅ Open the code of any pull request in Modeinspect's visual editor. ✅ batch updates: make a bunch of design changes in code immediately, then apply the agent all at once. ✅ Now a lot of changes don't require the AI agent at all. Resize, change fonts using design tokens, set margins, all made directly in code instantly just like in Figma. ✅ Make breakpoint aware edits, test the behaviour of states in different viewports in realtime. ✅ Reference your @{design_component} in the chat when building new features. ✅ When pushing back a new PR, you can now provide additional context to your developer. No devops work + get to prod-quality fast = Efficient design-dev handoff. In the following weeks, we're cooking something very special 👀