CtrlK
BlogDocsLog inGet started
Tessl Logo
PluginPublic

adobe/stardust

Redesign an existing website to make it better. Built on top of impeccable.

Quality

88%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide
SecuritybySnyk

Low

Low-risk findings worth noting

Overview
Quality
Evals
Security
Files

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

checksevfixfires whenrecommended move
landmark-mainP1PMno <main> in the delivered HTMLensure block output lands inside <main> (deploy anti-pattern 17)
img-altP2DPone or more <img> without alt=author alt text upstream; rollout can't synthesize it

seo

checksevfixfires whenrecommended move
title-missingP1PMno <title>add a metadata block; EDS derives <title> (deploy #34)
title-lengthP3PM<title> < 10 or > 70 chars~50–60 chars: brand + primary keyword
meta-descriptionP2PMno <meta name="description">add a Description row to the metadata block
single-h1P1PM<h1> count ≠ 1hero headline = single <h1>; others <h2> (deploy #35)
canonicalP2PMno <link rel="canonical">emit a self-canonical link at delivery
sitemap (site)P2PMrollout/site/sitemap.xml absentrun assemble.mjs and deploy the sitemap

ai-search

checksevfixfires whenrecommended move
jsonldP2PMno application/ld+jsonemit page-type JSON-LD in the head

cross-page (site-level)

checksevfixfires whenrecommended move
duplicate-titleP2DP≥2 pages share a <title>unique titles upstream (migrate metadata)
duplicate-descriptionP3DP≥2 pages share a descriptionper-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.

Source parity (informational)

When the page's capture exists (stardust/current/pages/<slug>.json plus its rendered sidecar pages/<slug>.html; optimize.mjs --current <dir> points elsewhere), a baseline finding whose condition the SOURCE shares is not a delivery defect:

checktagged when
title-missingthe source page has no <title> either
title-lengththe delivered <title> equals the captured one (entities decoded, whitespace collapsed)
meta-descriptionthe source page has no meta description either
jsonldthe source's rendered DOM has no application/ld+json either (no sidecar → unknown → not tagged)
duplicate-title / duplicate-descriptionthe captures of the same pages share the delivered value

The findings schema has no parity property, so the tag is fixability: out-of-scope (the schema's own "informational" value) plus the evidence prefix source parity: <evidence> — <shared condition>; autofix is set unavailable (a faithful migration is never rewritten). Tagged findings stay open under their stable id, are listed in the report's own "source parity" section, and are excluded from every dimension score, from the open P1/P2/P3 counts and from the gate. The tag follows each run: a finding the source stops sharing (a later capture, a changed title) routes normally again. A recorded hands-off run accepted 63 of these by hand — every JSON-LD, title-length, meta-description and duplicate-title finding of a faithful migration.

Scope & loop semantics

  • A page-level finding is id-keyed by layer|check|page-slug; site-level by layer|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 --slug run never marks another page's findings fixed.
  • accepted / wontfix are human decisions and are never auto-reopened.

skills

README.md

tile.json