Builder.io

I am SUPER excited to finally share this free tool I built: Paste a URL. Five seconds later, you have a design file — colors, typography, spacing, radii, components, YAML front matter — structured so your AI coding agent can actually use it. That's freedesign Here's the problem it solves: when you're building with AI coding agents, the model is rarely the bottleneck. Context is. Your agent doesn't know what your design looks like. It doesn't know your type scale, your brand radius, your spacing system. So it guesses — and you spend half your time correcting it. FreeDesign fixes the cold start. You give it any public URL, it extracts the visual system, and outputs a portable spec you can drop into any project as design context. One file. Readable by any agent. No Figma exports. No manual token hunting. No copying hex values out of DevTools at midnight. This is the first video in a series I'm putting together showing exactly how it works — what it extracts, how the output is structured, and how to use it with your coding workflow. Watch it, try a URL you care about, and let me know what comes out. Link in comments ↓

Introducing Clips - 100% free, open source, agent-native alternative to Loom Unlike Loom, agent's can fully understand Clips just from a URL. Every Clip comes with APIs and metadata for agents to explore their contents. Agents can "see and hear" anything in a Clip - not just transcripts, but everything visually in the video at any timestamp. Easily share bug reports, feedback, analyses, or anything else in a way that you can easily pass to agents to use to improve products, reports, reformat, or more. Also unlike Loom, you own the software, so no one can jack up prices on you suddenly like Loom did to us recently. Clips is made to be customized. The built-in agent can customize the app itself, so you can personalize the app to your needs and workflows. This, in my opinion, is the future of software. Open-source, forkable, customizable with agents, to make your own personal version of anything. You can also import Looms just from a URL and upload videos as well. I got so sick of telling people "don't send me feedback as looms, I can't pass those to agents, I need text and images" that I had to just solve this once and for all. There's a free hosted version you can use too, or fork and self host yourself. Will link to both in the comments.

Introducing /visual-plan - a skill to generate rich, interactive plans for Claude Code and Codex. Plan mode in Claude Code is incredible. But I always find my eyes glazing over when it gives me this huge markdown essay in my terminal. I found I can make much better visual plans with reusable components. So I made a skill called `/visual-plan`. It generates plans as MDX with visual, interactive components. Diagrams, interactive API specs, schema design changes, annotated code, and even pan and zoomable wireframes. So for any UI work, you can look at a wireframe first, comment on it, iterate, and then have the agent work. I’ve found this to be a much more intuitive interface for reasoning about what the agent is doing. It’s somewhat inspired by that popular post about how HTML is better than Markdown. But HTML can be slow and verbose to write. And it doesn’t look good checked into a repo. This has really made me feel like humans and engineering are entering a new abstraction phase, where we reason about things at the plan level. As long as the plan is good, agents are getting more and more reliable at executing on it. Almost to the degree that we trust the C compiler to compile to assembly reliably. Plans are the new intermediate representation. I also made a skill for the reverse of this, called `/visual-recap`. After the agent works, it gives you a recap of everything it did. Same idea: wireframes, interactive API specs and diffs, schemas, annotated code, etc. So now when you’re reviewing what the agent did for you, or looking at a pull request of somebody else’s code, you can see a visual recap instead of just reading a wall of text. It’s all free and open source. You can find it on my GitHub. Will link to it in the reply because we all know how dumb these algorithms are with links.

Been digging into Builder.io and how it’s shifting the way teams ship changes to production without turning everything into chaos. That collaboration layer is the real unlock. Take a closer look. ⬇️ ⬇️ ⬇️ https://removebg.techtaleempakistan.pk/_rb_origin/lnkd.in/eutcyh-N

This week we launched E.L.F. BEAUTY on Shopify. In builds like this, the storefront is the "easy" part. The hard part is working closely with teams representing dozens of different solutions and making them work in concert to deliver a cutting-edge customer experience. Shopify, Constructor, Talon.One, Builder.io, Braze, Ordergroove, poq, Omnivy, Sentry. Proud to build with all of you.