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

phase-3-sitewide-assets.mdskills/migrate/reference/

stardust:migrate: phase 3, sitewide assets and bundle finalisation

The text of this part of skills/migrate/SKILL.md, which keeps the heading and points here. "Above" and "below" refer to the order of the sections in that file.

Phase 3 — Sitewide assets and bundle finalisation

Per-page asset bundling already happened in Phase 2 (every referenced media subpath is on disk under stardust/migrated/assets/). Phase 3 fills in the sitewide assets that no individual page references explicitly:

  1. Copy stardust/current/assets/logo.<ext> to stardust/migrated/assets/logo.<ext> (only if missing or stale). Record under state.json.migrate.bundledAssets[].

  2. Verify favicon variants and font files were generated by prepare-migration Phase 4. If absent, log a warning and continue (the migrated site renders without them, just missing some platform-specific affordances).

  3. Add stardust/migrated/robots.txt and sitemap.xml derived from the migrated page inventory per reference/metadata-and-jsonld.md § Sitemap entry.

  4. If --clean was passed, compute stale = priorBundle.filter(p => !bundledAssets.has(p)) from state.json.migrate.bundledAssets[] and remove each stale subpath from stardust/migrated/assets/. Record the deletions under state.json.migrate.cleanedAssets[]. Per reference/asset-bundling.md § Stale asset cleanup.

  5. Verify portability. The bundle must work via file://, at a webserver root, and at any subpath — "one shape, works everywhere". Run every audit; any non-empty grep output or non-zero fixture exit fails the run with the cited error message:

    # No source-tree escapes
    find stardust/migrated/ -type f -name '*.html' -exec grep -l '\.\./current/' {} +
    # Error: "asset still points outside the migrated tree; rewrite via the
    #   asset-bundling pass per reference/asset-bundling.md § Detection"
    
    # No absolute internal references in attribute values (404 on file:// and subpath)
    grep -rE '(href|src)="/[^/]' stardust/migrated/ --include='*.html'
    # Error: "absolute href `/beers/` will 404 on file:// and on subpath hosts;
    #   rewrite via the page map per migration-procedure.md § Reference shape"
    
    # No absolute internal references in url() (inline style, <style> blocks, CSS)
    grep -rE 'url\(\s*["'\'']?\s*/[^/]' stardust/migrated/ --include='*.html' --include='*.css'
    # Error: "absolute url(/...) reference will 404 on file:// and on subpath hosts;
    #   rewrite via the asset-bundling pass per asset-bundling.md § Rewrite"
    
    # No directory-only nav (doesn't resolve on file://). Pattern accepts
    # only relative or root-absolute hrefs (./, ../, /, or bare segment)
    # so external URLs like https://google.com/ aren't false-flagged.
    grep -rE 'href="(\.{0,2}/|[a-zA-Z0-9_-])[^:"#?]*/"' stardust/migrated/ --include='*.html'
    # Error: "directory-only href `./beers/` won't resolve on file://;
    #   append the explicit index.html (or the source URL's .html leaf)
    #   per § Reference shape"
    
    # pageMap consistency — every internal href appears as an outputPath
    node skills/migrate/fixtures/pagemap-audit.mjs stardust/migrated/ stardust/state.json
    # Error: "internal href has no pageMap entry; link rewriting bypassed the
    #   page map per § Page map (build once, use everywhere)"
    
    # Headless file:// round-trip — the test that proves zip-and-deploy works
    node skills/migrate/fixtures/file-protocol-audit.mjs stardust/migrated/
    # Error: "<offending file> linked <ref> that 404s under file://; see the
    #   Playwright network log printed above"

    The audits are mandatory — there is no skip flag. The contract is "self-contained, zip-and-deploy" and these audits are the verifiers that back the claim.

Asset migration is idempotent — files are content-hashed and copied only when missing; per-page bundling deduplicates across the run.

skills

README.md

tile.json