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

classes-and-signals.mdskills/dynamics/reference/

Classes and detection signals

The class axis says what a feature is. It is read from evidence, never guessed from screenshots: a site's dynamic surface is invisible to a block-scoped, pixel-verified pipeline.

Classes

classmeaningsignals the detector readsusual disposition
L listinga block that lists other pagesrepeated same-site card groups in the content area, dates in cardsindex-backed or static-snapshot (curated) — the choice stays human
S searchsite search, autocomplete, resultsform[role=search], q/s/query inputs, first-party XHR with `searchautocomplete
F formany submission<form> with or without action, form-less control groups (modern CMS front ends render forms without a form tag), token-like hidden names, form-vendor hostsrebuild-native with a configurable endpoint; client-only when the form is pure compute
M modal / interactiveoverlays, dialogs, tabs, accordions, chrome interactions`modaldialog
V mediaplayers, embeds, mapsvideo-js, data-video-id/data-account, player hosts, iframe (an iframe without src is a runtime-injected embed)embed-passthrough (the player URL is the content)
T tag / consentanalytics, tag managers, consent, RUM, pixels, review/chat widgetsvendor table by host; first-party collector subdomains are tags that need a CNAME; mount divs with vendor data-* attributes and zero script tags = tag-manager-injectedembed-passthrough, scaffolded disabled, owner-enabled
A API / personalisation / settingsfirst-party XHR that renders content, experimentation, CMS settings objects`/api/graphql
R relationshipmany-to-many listingscard groups keyed by taxonomystatic-snapshot until modelled (listings.md Tier 3)
X auth / commercesign-in, account, cart, prices, session-bound features`loginsign-in
I18N localelanguage treeslink[rel=alternate][hreflang] (primary — sitemaps are not), language path prefixesa tree, not a feature: every other class recurs inside it (locale-trees.md)
CR client-renderedslots or whole pages filled after loadplaceholder/skeleton/js-/data-endpoint nodes with content, DOM added after load, main empty at loadstatic-snapshot from the settled DOM; a blank capture is a hard content gap, never migrated silently
D sheet / data filecopy and settings from spreadsheets or JSON files.json GETs that are not APIs, placeholders.json, fetchPlaceholders in a librarydata-fed by syncing the files from the source origin

Detection procedure

  1. Depth on archetypes. scripts/dynamics-detect.mjs --from-state stardust/state.json probes one page per type plus the home page (or --urls). Per page it accepts consent, settles, scrolls, settles again — tags and lazy players fire late — and records the network log by host, first-party API paths with status, POST bodies, third-party XHR, scripts, forms and control groups, the trigger → dialog → content graph, media ids, iframes, mount divs, globals and settings keys, framework, auth/commerce/locale signals, client-rendered slots and listing candidates. Findings are deduped across pages and keyed class|feature.
  2. Reach on every page. extract --dynamics records cheap per-page signals in the crawl (endpoints, forms, triggers, players); --reach stardust/current folds them into each finding as reach: pages/of. Features come from archetypes; reach comes from the roster — the two are never the same pass.
  3. Chrome once. Header and footer interactions (dropdowns, search overlay, sticky banner, switcher) are M findings marked chrome only; their evidence is the header contract (dynamics-plan --chrome), not the detector.

Vendor table

scripts/vendors.json maps host/URL patterns to a class and a role and is the classification engine. Grow it by adding rows, never by editing detector code. Unknown third-party hosts are never dropped: they stay visible as unknown third-party host — inspect (class A when the host answered XHR, T otherwise) until a row classifies them. Product names only — a customer's own hosts and account ids never enter the table.

Origin-bound probe

scripts/dynamics-plan.mjs --target-origin <host> requests every recorded first-party API path on the target. A 4xx or network error marks the finding host-bound: the feature exists in code but is dead off-origin. A pixel gate reports this as "band shorter"; the probe is what names it. Run it whenever a target host exists, with the site auth header scoped to that origin.

Known noise

aria-controls on nav dropdowns counts as a dialog trigger only when the target has role=dialog; media-CDN edge hosts and geo lookups appear as unknown hosts until the table knows them; four archetypes give features but not reach.

skills

README.md

tile.json