Reactive Checklist
The objectives your components carry — authored once, checked on every target.
Objectives: a component's test list
The reactive checklist is built from objectives — the concrete things worth checking whenever a component shows up on a target. For a file upload, an objective might be "Test for unrestricted file type acceptance".
Objectives are authored on the component, in its Checklists tab:
- Open the component and switch to Checklists.
- Click Add Objective.
- Fill in the Objective title and an optional Description (supports lists, inline code, and headings for context, links, or examples).
For bulk entry, switch to Paste multiple — one objective per line becomes one objective each. Objectives can be drag-reordered, and the order is shared across every asset the component appears on.
For stateful quirks, each objective also carries a State: Present or Absent — and the panel filters by the same values, so a quirk's test list stays coherent with how the quirk actually behaves.
Where objectives surface
They travel with the component. When it's linked to an asset, its objectives appear in that asset's Suggestions → Checklists → Reactive section — the checklist for what you can check, as opposed to the proactive side, which asks for what's missing.
Checking them off
Check an objective once you have verified it on the asset. The check is recorded in the asset's History → Checklists → Reactive Checks — the durable record of what was verified, on this asset, by hand.
Entries stay in history until you remove them. Removing one makes it eligible to surface again. That's the escape hatch for mistakes, not the default — the record is meant to be trustworthy.
Why objectives matter
- They make component knowledge actionable. An objective is what a colleague — or future you — actually does with the component on a new target.
- They compound. Write the test once on the component, and every asset it ever appears on inherits it.
- They discipline review. A checklist beats trying to remember what mattered last time.
What's next
- Work a Prompt — working both checklist sides in practice.
- Probes — the how-to notes that make each check concrete.