Now you can
,
& your best.

See how it works

Give every idea a little room.

Keep your original. Try another direction. Collect your landing pages and dashboards in one visual workspace, ready to explore.

The version library
Real pages. Real possibilities.
The version library
Explore

Give every idea a little room.

Keep your original. Try another direction. Collect your landing pages and dashboards in one visual workspace, ready to explore.

A workspace for possibilities

For the first idea, the fifth iteration,
and the one that finally clicks.

A little space to experiment. A better way to decide.

From your project. For your project.

Your next direction starts here.

Set up a local Lab with your coding agent, then make room for what comes next.

Freedom to try. Confidence to choose.

Explore freely.
Keep what matters.

Your original, your experiments, your decision.

A version worth keeping

Save where you are before exploring where you could go. Independent versions give every direction its own space.

Explore your workflow

A handoff you review

Choosing a favorite doesn’t overwrite your project. Review the source changes and check for drift before transferring them.

Made for people who make

Good ideas deserve
a second direction.

From a fresh landing page to a thoughtful redesign.

A designer sketching alternative interface layouts in a notebook
For designers

Find your landing page direction

Try a different first impression.

A frontend developer concentrating on his work in a daylight studio
For frontend developers

Give your redesign a fair comparison

Keep what works. Explore what could.

Two builders discussing ideas together over a sketchbook and laptop
For people who build

Build with your coding agent

More possibilities. A clearer next step.

A few things to know

Before your
first experiment.

A little clarity, before you get going.

What is Design Labs?

Design Labs is a local workspace for exploring and comparing frontend versions. Save a version of your Next.js landing page or dashboard, create alternatives with your coding agent, and compare working previews before choosing a direction.

Are these working websites or static screenshots?

Inside your Lab, previews are real interfaces you can scroll, click, and explore. The product captures on this page come from a running Design Labs workspace with three real versions of CleoStream.

Does Design Labs change my original project?

Snapshots and duplicates are independent copies. Choosing a production version changes the approval metadata. Moving source back into your project is a separate step with a reviewed diff and drift checks.

What can I use it with?

Design Labs currently supports Next.js frontends. Your coding agent prepares the preview dependencies and, when needed, frontend fixtures. Different framework, dependency, or authentication setups can need additional preparation.

Where does my Lab run?

On your machine. One managed launch command starts your workspace and prepared preview runtimes. Design Labs does not require you to publish your project to compare versions.

How do I get started?

Use Get Design Labs to copy the installation command and setup prompt. Run the command from your project root or give both to your coding agent.

Meet your next direction.

Bring your project. Keep your possibilities.
Make the next version your best one yet.

Explore the workspace
A little setup. A lot of possibilities.

Make space for your next idea.

Install Design Labs into your Next.js project. Your coding agent can take it from here.

Give this prompt to your agent

Set up Design Labs in this project using the installation command I provide. First read this project’s instructions and inspect its workspace structure. Run the command from the project root, then read the installed Lab’s AGENTS.md and .skills/design-labs/SKILL.md. Install dependencies using the project’s package manager and run the Lab doctor. Identify my Next.js landing page or dashboard, snapshot it as the initial production version, and prepare a frontend-only preview using fixtures where needed. Preserve source files, exclude secrets and never run a backend. Verify the preview and report the Lab launch command and any setup limitations. Use reviewed diffs and drift checks before transferring changes back to my project.

Copy the prompt and installation command separately.

Inside Design Labs