Redesign the Web.

Extract

Read the site you already have.

Point it at a URL. Stardust renders each page in a real browser and writes down the palette, the type scale, the motifs, the voice and every block of copy. Five pages by default, the whole site on request. It invents nothing at this stage. The capture is the evidence the next steps argue from.

https://www.example.com/

5 pages

Brand surface

Aa

serif display

1.25 scale

radius 12px

voice: assured

5 pages

gradient blob hero

• Real browser render, not view-source
• Palette, type scale, motifs, voice
• Every line of copy, counted
• PRODUCT.md and DESIGN.md as output

Direct

One sentence in. A direction out.

Tell it what you want in plain words: warmer, more editorial, keep our type. Direct reads the capture, keeps your palette and fonts unless you ask for a rebrand, researches references when it can, and rolls the seed for whatever is still open. It writes the target spec and its reasoning, so you can argue with it.

/stardust:direct

seed ·

md5("example.com" · today)

a3f7c92e

8b1d488a

0c5ef691

3427bbd1

→ resolves to

decade

1970s

a3

craft

letterpress

f7

register

editorial

c9

ground

inherited

—

• Brand-faithful by default, rebrand on request
• References first, seed for the rest
• Decade, craft, register from the roll
• A target spec and its reasoning trace

Prototype

Before and after, side by side.

Prototype renders one page of the redesign as a single HTML file and puts it next to the capture. Then it runs impeccable's craft loop: critique, audit, adapt to six viewports, check the motion. It rejects template-looking output. You pick, annotate, and re-run. Approve it, and migrate carries the design to every page as static HTML.

Before

After

6 viewports

• Critique, audit, adapt, motion
• Checked at six viewports
• Optional cinematic motion register
• Approve, then migrate to every page

Replica

The site you have, rebuilt clean.

Replica reads the live site and recreates one page per template as clean HTML and CSS, never a DOM copy. It gates each one against the original at two breakpoints: structure, visuals, a stitched pixel diff. The only design changes allowed are the ones you list. Then migrate clones the rest of the pages.

gate · 2 breakpoints

diff < 2% ✓

live

replica

structure ✓

visuals ✓

pixel diff ✓

• One archetype per page type
• Clean HTML and CSS, no DOM copy
• Pixel diff gate at two breakpoints
• migrate clones the sibling pages

Deploy

One page into blocks.

Deploy takes one page of static HTML and turns each section into an Edge Delivery block with its own CSS, and the copy into authorable content. It writes both through the Document Authoring API, previews, publishes, then reads the live page back and checks it. A page counts as deployed only when that check passes.

index.html → blocks

preview · publish · check

hero

cards

text

quote

• Each section becomes one block
• Copy stays editable in Document Authoring
• Internal links rewritten to the new origin
• Live page checked before it counts

Rollout

The whole site, then the check.

Rollout runs deploy across the migrated tree. It keeps a ledger of what shipped and what is left, shares blocks across pages instead of forking them, adds the sitemap and redirects, and audits every link. When it is done, qa sweeps the live site and reports what it finds. It never edits.

stardust/rollout/ledger.json

delivered 112 / 134

/

delivered

/about

delivered

/products

delivered

/products/beans

delivered

/news/2026

deploying

/contact

pending

shared blocks ✓ · sitemap ✓ · redirects ✓ · links ✓

• A ledger of shipped and pending pages
• Blocks shared, not forked per page
• Sitemap, redirects, link audit
• qa reports on the live site