/stardust

name: stardust
description: Guided multi-page redesign of an existing website through a four-phase pipeline — extract (crawl and capture the current site), direct (set a visual direction), prototype (generate redesigned HTML), and migrate (emit a deployable static site). Tracks progress incrementally per page in stardust/state.json so redesigns are resumable. Delegates the per-page design craft (typography, spacing, color, layout, motion) to the impeccable skill. Use when the user wants to redesign, revamp, modernize, or restyle an existing site they can point to by URL, run the extract/direct/prototype/migrate flow, or resume a multi-page redesign. Not for designing a brand-new site from scratch or one-off single-component edits.
license: Apache-2.0

stardust

You are operating the `stardust` skill: a guided redesign of an existing website. The user's job is to say what they want; your job is to reason about what that means, propose a plan, and execute it through a small set of sub-commands that delegate the actual design work to **impeccable**.

Setup (run before anything else)

1. **Verify impeccable is installed.** Stardust has a hard dependency on impeccable and ships no fallbacks. Look for the `impeccable` skill in any of the standard harness directories the project uses (`.claude/skills/`, `.agents/skills/`, `.cursor/skills/`, etc.). If it is not installed, stop and tell the user: > Stardust requires impeccable. Install it from > <https://github.com/pbakaus/impeccable> and re-run the command. 2. **Run impeccable's context loader once per session.** Execute the loader at `<harness>/skills/impeccable/scripts/load-context.mjs`. Its JSON output tells you whether `PRODUCT.md` and `DESIGN.md` exist at the project root (these are the *target* state for stardust). Skip the loader if it already ran in this session's history. 3. **Read stardust's state.** Read `stardust/state.json` if present (`reference/state-machine.md` defines the schema). Note which pages are `extracted`, `directed`, `prototyped`, `approved`, or `migrated`. 4. **Read impeccable's command registry.** Parse `<harness>/skills/impeccable/scripts/command-metadata.json`. This is the single source of truth for the 23 impeccable commands; never hardcode them in your reasoning. 5. **Status ledger.** Every stardust skill appends a phase-transition line to `stardust/status.jsonl` at each phase start/end, per `reference/run-status.md`.

Routing

Once setup is done, route on the user's input:

• **No argument.** Render the **state report** described in

`reference/state-machine.md`: project state, per-page status table, recommended next command, with reasoning. Do not write anything.

• **First word names a sub-skill.** Delegate to the matching

`stardust:<name>` skill and pass remaining args through. The master skill routes **all** sibling sub-skills:

| keyword | sub-skill | owns | |---|---|---| | `extract` | `stardust:extract` | crawl + capture the current site | | `direct` | `stardust:direct` | resolve the visual direction | | `prototype` | `stardust:prototype` | per-page redesign prototypes | | `migrate` | `stardust:migrate` | full-site platform-agnostic static HTML | | `prepare-migration` | `stardust:prepare-migration` | the migrate-prep cascade (prep phases, assets, dynamic-blocks gate) | | `deploy` | `stardust:deploy` | one page → EDS blocks + DA delivery | | `rollout` | `stardust:rollout` | whole migrated site → EDS, with coverage + delivery gates | | `diff` | `stardust:diff` | prototype ↔ build fidelity probes (pixel + structural) | | `audit` | `stardust:audit` | three-perspective site audit — design tensions, SEO/technical, LLM visibility — scored report + findings ledger | | `qa` | `stardust:qa` | read-only post-deploy QA sweep of the live site — routing, fidelity, template conformance, rendering, visual regression, SEO, links, a11y, perf — findings report only, never fixes | | `uplift` | `stardust:uplift` | one-shot presales orchestrator (3 variants) |

• `prototype` accepts `--cinematic` (or `--cinematic=<register>`)

to layer a brand-faithful motion register on top of the static prototype (per `skills/prototype/reference/motion-registers.md`).

• `uplift` is the one-shot presales orchestrator: takes a URL and

produces three differentiated variants (one fully cinematic) without further user coordination. Use when the user wants to skip the extract/direct/prototype chain (per `skills/uplift/SKILL.md`).

• **First word is anything else (a freeform phrase).** Treat it as a

redesign intent. Load `reference/intent-reasoning.md` and follow the procedure step by step. **Do not execute any impeccable or stardust command before showing the resolved plan to the user** (under hands-off mode, the plan is recorded in `stardust/direction.md` instead of awaiting confirmation — see § Hands-off mode).

Hands-off mode

Activated by `--hands-off` on **any** stardust invocation, or by an explicit user phrase ("fully hands-off", "no approval gates", "run autonomously"). On activation, stamp `state.json.handsOff: true` (schema note in `reference/state-machine.md` § Hands-off keys) and append an activation line to `stardust/direction.md`. The mode removes **waiting**, not **validation**: every quality gate in the pipeline still runs at full strength; what changes is who resolves the interactive pauses.

Under hands-off, every interactive gate across the pipeline auto-resolves:

| gate | hands-off resolution | |---|---| | `direct` clarifying questions | derive the answers from the captured evidence (`stardust/current/`), and state each as a **named assumption** in `direction.md` | | `prototype` brief-confirmation waits | skip; proceed on the authored brief | | prototype approval | granted by the agent's own judgment **only after all quality gates pass** (craft bar, validation loop, motion gates); recorded as