Redesign an existing website to make it better. Built on top of impeccable.
88%
Does it follow best practices?
Run evals on this skill
Adds up to 20 points to the overall score
Low
Low-risk findings worth noting
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.
| axis | question | values |
|---|---|---|
| class | what is it? | L S F M V T A R X I18N CR D (classes-and-signals.md) |
| disposition | what do we do? | rebuild-native · index-backed · data-fed · embed-passthrough · client-only · static-snapshot · decided-out |
| reproducibility | what does it need to ship? | self · needs-credential · needs-human-capture · needs-backend · needs-business-decision |
| status | where does it stand? | pending · in-progress · interim · done · scaffolded-awaiting-owner · delivered-by-capture · decided-out · skipped-source-broken |
| target | what 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).
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.
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.
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.CR with an empty main
is a hard content gap → needs-human-capture, batched (patterns.md § client-rendered-page).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.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.skipped-source-broken; there is nothing to reproduce./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).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".
.tessl-plugin
skills
audit
reference
deploy
reference
scripts
test
diff
direct
dynamics
extract
migrate
prepare-migration
prototype
assets
motion
fixtures
reference
qa
replica
reference
scripts
test
reskin
rollout
spec
stardust
uplift
reference