adobe/stardust
Redesign an existing website to make it better. Built on top of impeccable.
71
89%
Does it follow best practices?
Run evals on this skill
Adds up to 20 points to the overall score
View guide
Low
Low-risk findings worth noting
checks.mdskills/rollout/reference/
optimize check catalog — rollout:baseline source
These are the deterministic detectors of the rollout:baseline source that
optimize.mjs runs over the delivered (or migrated) HTML. Baseline is one of
several audit sources — the others (impeccable, the marketing SEO skills,
stardust tensions) feed the same ledger via findings.mjs record; see
audit-sources.md. Findings reference a check by layer + check; this catalog
can grow without a schema change. Severity drives the gate (any open P1 fails
it); fixability routes the fix; a registered check is auto-fixed by autofix-aem.
fixability: PM = platform-migration (rollout re-deploys to fix) · DP =
design-pass (upstream — fix in migrate/prototype; rollout only surfaces) · OOS
= out-of-scope (informational).
accessibility
| check | sev | fix | fires when | recommended move |
|---|---|---|---|---|
landmark-main | P1 | PM | no <main> in the delivered HTML | ensure block output lands inside <main> (deploy anti-pattern 17) |
img-alt | P2 | DP | one or more <img> without alt= | author alt text upstream; rollout can't synthesize it |
seo
| check | sev | fix | fires when | recommended move |
|---|---|---|---|---|
title-missing | P1 | PM | no <title> | add a metadata block; EDS derives <title> (deploy #34) |
title-length | P3 | PM | <title> < 10 or > 70 chars | ~50–60 chars: brand + primary keyword |
meta-description | P2 | PM | no <meta name="description"> | add a Description row to the metadata block |
single-h1 | P1 | PM | <h1> count ≠ 1 | hero headline = single <h1>; others <h2> (deploy #35) |
canonical | P2 | PM | no <link rel="canonical"> | emit a self-canonical link at delivery |
sitemap (site) | P2 | PM | rollout/site/sitemap.xml absent | run assemble.mjs and deploy the sitemap |
ai-search
| check | sev | fix | fires when | recommended move |
|---|---|---|---|---|
jsonld | P2 | PM | no application/ld+json | emit page-type JSON-LD in the head |
cross-page (site-level)
| check | sev | fix | fires when | recommended move |
|---|---|---|---|---|
duplicate-title | P2 | DP | ≥2 pages share a <title> | unique titles upstream (migrate metadata) |
duplicate-description | P3 | DP | ≥2 pages share a description | per-page descriptions upstream |
Layers baseline does not assess
brand-tensions, design-ux, and content-conversion need judgment, not
deterministic parsing, so the baseline source leaves them unscored (null).
They are populated by the other sources — impeccable:critique (design-ux,
brand-tensions), stardust:tensions (brand-tensions, design-ux), and the
marketing skills (content-conversion via cro/copywriting if run) — recorded
through findings.mjs. Once a source records into a layer, the scorecard scores
it; until then it shows not-assessed rather than faking a number.
Scope & loop semantics
- A page-level finding is
id-keyed bylayer|check|page-slug; site-level bylayer|check|*(or the involved slug set). Re-runs match by id — no duplicates. - A finding is only resolved (→
fixed) when this run actually inspected its scope (the page was loaded, or site checks ran). A--slugrun never marks another page's findings fixed. accepted/wontfixare human decisions and are never auto-reopened.
.tessl-plugin
skills
audit
reference
deploy
diff
direct
extract
migrate
prepare-migration
prototype
replica
reskin
rollout
stardust
uplift
reference