Skip to content

Built so AI builds what you actually designed.

SpecShot turns a real design and its context into something an AI agent can build faithfully, instead of guessing from a screenshot and a paragraph.

Our mission

SpecShot began as a Chrome extension with one job. Capture a section you admire and turn it into a prompt an AI could build from. That solved a real problem, and it revealed a bigger one.

Most AI builds start from a screenshot and a paragraph. The agent guesses the layout, invents the spacing, and picks colors that were never yours. The result looks close and works wrong. We built SpecShot so the agent stops guessing.

Today SpecShot is a workspace for shipping websites with an AI agent. You brief a project, collect the real references and brand, lay out the pages, and connect your agent over MCP. It builds full multi-page designs inside SpecShot, your client reviews them section by section, and you hand off a build-ready spec. Capture. Brief. Build. Review. Ship.

From a brief to a build-ready spec

One project holds the whole job, from the first reference to the final handoff. Here is the path a site takes inside SpecShot.

  1. 01Projects

    Start a project and write the brief. Set the goal, the audience, and what the site has to do.

  2. 02Collect

    Capture reference sections with the extension, save inspiration, and define the brand. Colors, type, and spacing.

  3. 03Pages

    Lay out the pages the site needs. Each page gets its own board so the work stays organized.

  4. 04Agent build

    Connect any AI agent over MCP, a hosted endpoint or the npm package. It reads the whole project and builds real, full-fidelity, multi-page designs, filed under each page.

  5. 05Canvas

    Every version lands on a live build canvas, side by side, so you compare instead of guess.

  6. 06Client review

    Share a design through a portal. Your client pins feedback on the exact section, and the thread flows back to the agent.

  7. 07Handoff

    Hand off a build-ready spec. Sections with stable ids, real copy, brand tokens, and a ready-to-paste build instruction.

The original capture-to-prompt flow still ships too. Generate a builder-specific prompt for any of the 17 targets, including Cursor, Claude Code, Codex, Framer, Webflow, React + Tailwind and EtchWP + ACSS, then export it as Markdown or JSON.

How we build SpecShot

A few principles guide every decision. They keep the product honest and the workflow simple.

Context over guesswork

An agent is only as good as its brief. We give it the real design, the brand tokens, and the whole project, so what it builds matches what you meant.

Documentation, not duplication

SpecShot documents a design so you can build your own. We never reproduce or republish a site, and captured DOM is stored as data, never as a running page.

Fits your workflow

Connect any agent over MCP. Generate prompts for 17 builders, export Markdown and JSON, and hand off to the tools you already run.

Built with focus

Small, sharp, and shipped with care. We would rather do a few things excellently than everything adequately.

What SpecShot does not do

The boundaries are the point. They are what make SpecShot safe to use on any site you admire.

  1. 01No duplication.

    SpecShot does not reproduce or republish a website. It documents the design context so your agent builds your own version.

  2. 02No hosting.

    SpecShot does not host, mirror, or serve captured pages. It stores designs and captures as data, never as a running site. The build lives wherever you ship it.

  3. 03No saved form values.

    Captured DOM is stored as JSON, never as runnable code, and we never save the form input values from a captured page.

Capture. Brief. Build. Review. Ship.