redesigned, fixed, migrated. Or all three.
Redesign
the Web.
Two ways in.
Say what you want in a sentence and the master skill picks the route. Or open a door yourself.
Redesign
New design on the site you have.
extract → direct → prototype → migrate
Shortcut
/stardust:uplift <url>
one URL, three pitch variants, one cinematic
Take a live site.
Bring it back redesigned.
Three skills, three steps. Each writes its files and the next one reads them. Or say what you want in a sentence and the master skill picks the route.
“You can go from global brand to regionalized site in Edge Delivery Services in under a day.”
A guest on Thursday Frequency · aem-live live session, 18 June 2026
Extract
/stardust:extract <url>
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.
In this step
- Real browser render, not view-source
- Palette, type scale, motifs, voice
- Every line of copy, counted
- PRODUCT.md and DESIGN.md as output
Direct
/stardust: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.
In this step
- 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
/stardust: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.
In this step
- Critique, audit, adapt, motion
- Checked at six viewports
- Optional cinematic motion register
- Approve, then migrate to every page
Frescopa,
before and after.
White-label demo site. Redesigned with extract, direct, prototype.
Frescopa · before
Frescopa · after
Keep the design.
Change the platform.
Same site, new origin. Replica rebuilds it as clean HTML and proves the match. Deploy and rollout carry it to AEM Edge Delivery, one page first, then the whole site. When one site becomes many markets, with in-place authoring, drafts, translations and scheduled releases, this is the route to production.
“The ROI on being able to do that... it's undeniable.”
Thursday Frequency, aem-live
- Static HTML every page, tokens, provenance · any host
- stardust:deploy one page → EDS blocks + authorable content
- AEM Edge Delivery rollout the site · qa the live pages
Replica
/stardust:replica <url>
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.
In this step
- One archetype per page type
- Clean HTML and CSS, no DOM copy
- Pixel diff gate at two breakpoints
- migrate clones the sibling pages
Deploy
/stardust: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.
In this step
- 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
/stardust: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.
In this step
- A ledger of shipped and pending pages
- Blocks shared, not forked per page
- Sitemap, redirects, link audit
- qa reports on the live site
Install it.
Then ask it.
Stardust is a set of AI skills. It needs impeccable for the design craft and Playwright to render pages. Install both, then say what you want in your own words. Slash commands are optional.
Built on impeccable.
“One of the most incredible open source skills I've ever seen.”
Thursday Frequency, aem-live
~/project ›
/plugin marketplace add adobe/skills
/plugin install stardust@adobe-skills
installed stardust 0.19.8 · 14 skills
/plugin marketplace add pbakaus/impeccable
/plugin install impeccable@impeccable
installed impeccable · design craft
~/project ›
/stardust make example.com feel like a magazine, keep our type
reading example.com · 5 pages
brand-faithful mode · palette and type pinned
decade ✓ rolled → 1970s craft ✓ rolled → letterpress
plan written to stardust/direction.md · confirm to run