MockPilot

This sounds super interesting especially grabbing a sites design features, colours, fonts, icons etc... sounds like a much easier way than sending over a complete css file

The "no Figma needed" angle is smart – designers will use it anyway, but this opens it up to everyone else. How does it handle sites with heavy animations or scroll effects?

The live-site-to-editable-mockup flow is a great bridge for non-designers and fast product iteration. Auto-extracting typography, colors, and components is the practical bit. How clean is the exported HTML on complex responsive pages?

The PM-to-dev handoff use case is very real. A quick editable mockup from the actual live page would remove a lot of vague screenshot feedback and make small UI changes much easier to explain.

Bad and good news:Figma is releasing their chrome extension (have you heard?) which seems to do similar as MockPilot, except just exports to Figma.Bad news: competitor. Good news: validation??Anyways, congrats on the launch :)

Good one! The thing I'd want to stress-test is sites that render client-side or lazy-load on scroll. Does the capture wait for the DOM to settle? Do you end up grabbing half-loaded components?

This look good especially for demo presentation, I have a question, can't it be developed fully without the hassle of going through all these processes ?

The asset library extraction is the part that grabs me, pulling a live site's typography and colors into something reusable so edits stay on brand is really handy. Curious whether the exported HTML comes out as semantic markup or mostly positioned divs. Congrats on shipping.

Hey Product Hunt 👋

I built MockPilot for a very specific frustration I kept seeing on every team I've worked on: a PM (or designer, or support lead, or founder) has a clear idea for a feature or a tweak to an existing screen - but no fast way to show it. So they write a paragraph, drop in a screenshot with arrows, and hope the developer interprets it the way they meant. Half the time, they don't.

MockPilot fixes that. You point it at any URL - your own product, a competitor, anywhere - and it captures the page (or just one component) as a fully editable mockup. While it captures, it pulls the site's design system apart into a reusable asset library: typography, colors, components, icons.

Then you just describe what you want in plain English. "Add a second pricing tier between these two", "reuse the same card style", "Replace this empty state with a CTA to import data", "Make the nav sticky and add a search field." The AI does it, on-brand, using the assets it already extracted. No Figma. No CSS. No design background needed.

When you're happy, hand off a clean HTML export, deploy it, or just create a screenshot and send it to your developer. Suddenly "here's what I want" is a real artifact instead of a paragraph and a prayer.

It's an Electron app, fully local (captures never leave your machine), open source, and free. macOS and Windows builds are on the GitHub releases page.

A few things I'd love your feedback on:

1. PMs especially - what does your current "spec a UI change" workflow look like, and where does MockPilot fall short of replacing it?
2. What would make handoff to developers smoother - annotations? A diff view? Figma export?
3. Which sites break the capture? Bug reports very welcome.

Happy to answer anything - and thanks for checking it out! 🚀