Your first redesign,
end to end.
Install Stardust and run your first redesign. From any URL to a complete redesigned static site — every page, not just the home.
Set upInstall.
From inside Claude Code, add the two marketplaces and install both plugins:
$claude plugin marketplace add adobe/skills $claude plugin install stardust@adobe-skills $claude plugin marketplace add pbakaus/impeccable $claude plugin install impeccable@impeccable
Built on impeccable. Which is, frankly, brilliant.
Both plugins need to be installed for Stardust to run. Once installed, the /stardust:* slash commands are available in any Claude Code session. The commands reference lists every sub-command and flag.
ShortcutOne URL, three variants.
The fastest way to get started. Skip the four-step pipeline and run a single command:
›/stardust:uplift https://example.com
uplift collapses extract → direct → prototype × 3 into a single opinionated command. It picks every variability axis from the captured brand surface — palette and typography are pinned, the cinematic register is read from the brand personality, and the "what if…" candidates for variants B and C are walked from a closed catalog so nothing improvises. Output: variant A ("tomorrow's version of the site you have today"), B ("what if we amplified <captured trait>?"), and C ("what if motion was part of the identity?").
Or follow the long form below when you want a full multi-page migration with explicit direction.
Main flowFour sub-commands. One pipeline.
Stardust is opinionated about which redesign to make and runs it as a chain of commands. Each command writes its own artifacts; the next reads them. Reading the artifacts back, you'll see the whole reasoning trace — palette picks, divergence inputs, the seed for today.
Math, not mysticism. Every choice has a provenance. The walkthrough below focuses on the home page; running each command without a slug fans out to the rest. You can stop after any step and pick up later — Stardust does not lock you into a pipeline.
# the four commands you'll meet today ›/stardust:extract — capture the current site ›/stardust:direct — resolve a redesign direction ›/stardust:prototype — generate three variants per page ›/stardust:migrate — ship deployable static HTML
New site, not a redesign? Stardust also designs new sites from a brief. Redesigning an existing source is the main use case today; new-site design works but is less battle-tested.
Step 1Capture the current state.
Point Stardust at a URL:
›/stardust:extract https://example.com
If the project hasn't been set up yet, extract starts with a short interview that writes PRODUCT.md at the project root. You answer in your own words; the file captures what you're building and who it's for. Then the crawl begins.
It crawls five pages by default — the home plus four pillar pages — captures the brand surface (palette, typography, voice, motifs), and writes everything under stardust/current/. The crawl runs in a real browser, so JavaScript-rendered sites work the same as server-rendered ones.
When it finishes, open the eyeball-check artifact:
›open stardust/current/brand-review.html
You'll see a self-contained visual review of what was captured — colors, type, logo, motifs, voice samples, and any tensions the detector surfaced. Spend a minute here. If something looks wrong, re-run extract with --refresh <slug> on the misread page before moving on. Misreads are cheap to fix here and expensive later.
Step 2Direct the redesign.
This is the only step where you say what you want. A short phrase is enough.
›/stardust:direct "more editorial. lean into typography. keep the existing palette."
Stardust restates your phrase in dimensional vocabulary, asks at most two clarifying questions if anything is underspecified, and resolves a target direction. It writes the target PRODUCT.md, DESIGN.md, and DESIGN.json at the project root, plus a full reasoning trace at stardust/direction.md.
The trace is worth reading. It tells you which axes the phrase moved, what the seed picked from md5(brand · date), which font deck and palette were chosen, and why. If you disagree, rerun with --re-direct.
Pin what matters to you. You can lock the type stack and palette by saying so in the phrase: "keep typography and palette." Stardust enters brand-faithful mode and only rolls the dimensions you didn't lock.
Step 3Prototype the home page.
›/stardust:prototype home
Two things happen. First, Stardust writes a per-page composition brief at stardust/prototypes/home-shape.md — the section list, layout strategy, content sources, anything the brief reviewer would want to challenge before the render. You'll be asked to confirm.
Once you confirm, the proposed redesign renders into stardust/prototypes/home-proposed.html, and a viewer opens automatically — your current home on the left, the proposed redesign on the right. Review it. If something needs adjusting, edit home-shape.md and re-run prototype to refresh.
For the rest of the site, drop the slug. Run /stardust:prototype without a slug and Stardust prototypes every directed page in turn — same direction, same brand surface, page-aware composition for each.
Step 4Approve and migrate.
When the home prototype reads the way you want, signal approval — click the Approve button in the viewer, or just say "approve home" in the chat.
Then ship the home page:
›/stardust:migrate home
The output is a deployable static HTML file. Drop it on GitHub Pages, your CDN, or any host that serves files. No build step. No framework lock-in.
For the whole site, drop the slug:
›/stardust:migrate
Migrate runs over every approved page in stardust/state.json and emits a complete static site, ready to publish.