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

triage.mdskills/dynamics/reference/

Triage — the four axes and the inventory

One row per feature in stardust/dynamic-features.md. Four axes per row; each answers a different question and none can be inferred from another. A fifth column, target, names the delivery form.

axisquestionvalues
classwhat is it?L S F M V T A R X I18N CR D (classes-and-signals.md)
dispositionwhat do we do?rebuild-native · index-backed · data-fed · embed-passthrough · client-only · static-snapshot · decided-out
reproducibilitywhat does it need to ship?self · needs-credential · needs-human-capture · needs-backend · needs-business-decision
statuswhere does it stand?pending · in-progress · interim · done · scaffolded-awaiting-owner · delivered-by-capture · decided-out · skipped-source-broken
targetwhat form ships it?block · widget · runtime · content · embed

Flags, when they apply: regulated-pii (forms), host-bound (APIs dead on the target), source-nonfunctional (the source itself fails for a real user), environment-limit (the test network cannot reach a hand-off target).

Dispositions

  • rebuild-native — behaviour rebuilt in block, widget or runtime JavaScript with no external data: modal loaders, chrome interactions, search results, forms, clock-dependent strings.
  • index-backed — fed by the site's own query index: listings, related rails, search.
  • data-fed — fed by data that lives outside the page: an API kept same-origin, a snapshot served from the code bus or a sheet, endpoint indirection for an existing library (off-origin-data.md).
  • embed-passthrough — a third-party surface kept as-is: players, iframes, form services, tags and CMPs. Re-authored from live-DOM ids where needed, never re-implemented.
  • client-only — pure client compute (calculators, filters, comparisons): inline JS, controls, no network. Cheapest, highest-fidelity migration; never flatten it into prose.
  • static-snapshot — the settled DOM ships as content, with the reason and the unfreeze condition recorded.
  • decided-out — cannot or must not exist off-origin (session-bound, regulated capture, no consumer on the migrated pages). A register row with the production statement, never a silent gap.

Target. Widget when the section carries no authored content — configuration only, or everything arrives from code, index, API or user input; block when authors fill rows. widget (widgets/<path>/<name>, ../../stardust/reference/data-attributes.md) wherever the disposition leaves no authored rows: client-only tools, the search box and its results, definition-driven forms with no authored copy, locators, the chrome's sign-in/account UI when kept. runtime = page-wide JS (modal loader, chrome), content = snapshot or player URL, embed = passthrough iframe or tag. A block whose only rows are key-value config is a widget smell.

Reproducibility — the axis that bounds the phase

Only self ships autonomously. Everything else is emitted as one decision batch — one message listing every credential, capture, backend and business decision — never one question at a time. Under hands-off mode the batch is recorded, each decision becomes a named assumption, and the interim path ships (interim or scaffolded-awaiting-owner). An assumption is the run's, never the owner's: it cannot set decided-out. Naming every external gate up front is what turns dynamics from an open-ended stall into a bounded phase.

Rules

  1. Reconcile against the migrated output first. Scan stardust/migrated/ for the feature's evidence before scheduling work (dynamics-plan.mjs --migrated). The capture pipeline had already baked review text on 48 of 64 detail pages that a source-only scan flagged as a gap.
  2. Never fabricate legal or financial copy for a page captured empty. CR with an empty main is a hard content gap → needs-human-capture, batched (patterns.md § client-rendered-page).
  3. Never auto-wire a regulated form. regulated-pii (SSN, date of birth, account numbers, minors, document upload) → rebuild the UI with submission blocked until a human configures the secured endpoint; surface as a mandatory decision. Most intake help pages deep-link to an authenticated app — migrate the link, do not manufacture a form.
  4. A search box implies a results page. Class S over the site's own pages is self once the index exists: it ships over the migrated corpus (a smaller corpus than the source's is a parity note, not a reason to exclude). Emit the paired deliverable or mark the form non-functional; the header form never keeps the source origin's results URL.
  5. Source-live-check. If the source surface fails for a real logged-in user, mark skipped-source-broken; there is nothing to reproduce.
  6. Decided-out is explicit, with reason and production statement, so "not migrated" and "cannot exist here" are never confused.
  7. Static first, then wire. Every feature degrades to a working static page before any phase replaces one degradation with the live behaviour. The inventory never blocks the static path.
  8. A missing query index is a yaml file, not a service. /query-index.json → 404 on the target means no helix-query.yaml in the code branch (listings and search, class L / S): author it, push, publish live, poll (no more often than every 5 s, bounded) — listings.md § Getting an index at all. The sheet-backed interim index ships only when the code branch is not writable; a 403 from the configuration service is never the reason (patterns.md § search-index-backed).
  9. Search parity is count and titles — expectCount / expectTitles per probe term on the search-query check in parity.json (patterns.md § search-index-backed).

stardust/dynamic-features.md

# Dynamic features — <site>

## Listings contract
<per content type: the `<meta name>` fields each page must emit; index each listing reads —
listings.md. "none" when there are no listing blocks.>

## Features
| # | id | feature | class | reach | disposition | target | reproducibility | status | pattern | decision / owner | evidence |
|---|---|---|---|---|---|---|---|---|---|---|---|

## Decision batch
<every non-self row, grouped by what it needs, one message to the owner>

## Register (decided-out)
| feature | reason | production statement |

dynamics-plan.mjs drafts the table; the run curates it (merge duplicates, drop noise, keep every axis honest) and writes stardust/dynamic-features-plan.md: phases with deliverables, authoring contract, verification, owner decision, effort. The gate (prepare-migration 4.5, replica Phase 2, rollout B2) fails on a row without a disposition — "I don't know yet" is spelled static-snapshot with reason "undecided — revisit at rollout".

skills

README.md

tile.json