Introducing Pluck Studio: Mix Real UI into New Designs on a Canvas

For most of its life, Pluck was a one-way street. You clicked a component on a website, it landed in your clipboard, and from there it went into Cursor or Figma and was gone. If you wanted it again next week, you went back to the site and plucked it again.

Pluck Studio fixes that, and then does something with the pile of references you end up with. It is available now at studio.pluck.so and as a desktop app for macOS, Windows and Linux.

The library: every pluck, kept

Every pluck is now saved to your library automatically. Each entry keeps the screenshot, the source page URL, and the complete style data the extension captured: the element tree, computed styles for every node, and the responsive breakpoints. You can switch this off in the extension settings if you would rather keep the clipboard-only behaviour, and there is a "Save to Studio" mode that sends a pluck straight to the library without touching the clipboard at all.

The library is a list, newest first, filterable by site. That is deliberate for now. We would rather you have a dependable place to find the pricing table from last month than a tagging system you never fill in.

Boards: a canvas for mixing

The library is storage. Boards are where things happen.

A board is a canvas with four kinds of card:

• Pluck: a component from your library.
• Image: anything you upload, such as a logo, a photo or an existing mockup.
• Prompt: a text brief describing what you want.
• Generation: an image produced by running a prompt.

Plucks, images and generations connect into prompts as references. Drag a pluck onto the board, draw an edge from it into a prompt card, write the brief, and run. Generation cards appear to the right of the prompt. Those generations can in turn be connected into another prompt, so a board reads left to right as a chain of references, briefs and results.

This is the mixing model. A brief like "a SaaS landing page using the navigation from the first reference, the card style from the second and the colour palette from the uploaded logo" does what it says, because each reference is a real component with real values rather than a vague description.

Each and combine

When a prompt has two or more generations connected to it, it gains a mode switch:

• Each runs the prompt against every connected generation separately, so "make the headline larger" produces a revised version of each one.
• Combine merges the connected generations into a single result, which is how you take the layout from one attempt and the colour treatment from another and ask for both in one image.

We use Each for exploring variations and Combine for converging. There is a full post on the pattern in Each vs Combine.

Where a prompt runs

Every prompt card has a model setting:

• Auto picks a hosted model for you. Auto prefers models that render UI text well when the brief mentions headlines, buttons, pricing, navigation or dashboards, and it picks one that accepts all of your connected references.
• A hosted model by name: Nano Banana 2, Nano Banana Pro, GPT Image 2, Seedream 5 Pro, Seedream 5 Lite, Ideogram V4 or Recraft V4.1. Hosted runs spend credits, and Studio shows the cost before you run.
• Local runs the prompt through the Codex CLI on your own machine via the desktop app, free of credits. The board has to be open in the desktop app for a local run to pick it up.

Prompt cards also carry an aspect ratio and a quality tier, and your account has a prompt template that sets the framing for every run. Those are covered in Aspect Ratio, Quality and Model and Prompt Templates in Pluck Studio.

Board chat

Each board has a chat panel. You can ask about the board ("which plucks are connected to the second prompt?") or tell it what to change ("add the Linear pricing table from my library as a reference and run again at 16:9"). The chat edits the board with the same tools we expose to external agents over MCP, so it is a real operator rather than a help bot.

What a board produces

A generation is an image. We want to be clear about that, because it shapes how Studio is useful today. A board is for working out what a design should be: the layout, the hierarchy, the mood, the parts you are borrowing from where. Once you have a generation you like, the pluck that inspired it is still in the library with its full style data, and you can copy it as an AI prompt or Figma layers to start building for real.

In other words, Studio is for the thinking part, and the extension is still the handoff.

A short example

Here is a board we built last week for a fictional analytics product.

1. Plucked the navigation bar from a developer tools site, the three-column feature grid from a design agency, and a pricing table from a billing provider. All three landed in the library.
2. Opened a new board, added the three plucks and uploaded a logo.
3. Connected all four into a prompt: "A landing page for an analytics dashboard product. Use the navigation from the first reference, the feature grid layout from the second, the pricing table from the third. Palette from the logo. Dark theme."
4. Set the model to Auto and ran. Three generations appeared.
5. Connected the two best into a new prompt, switched it to Combine, and asked for the hero from one with the pricing section from the other.

Twenty minutes, and we had a direction to show rather than a paragraph describing one.

Try it

Studio comes with every account, including Free. Free includes the library, boards and local generation with the desktop app; hosted generation needs credits from a paid plan. If you already have the extension installed, open studio.pluck.so and your recent plucks are already there.