Teaching artifact

A page a busy reader learns from in five minutes and returns to for detail. Design carries the meaning; prose is the last resort.

Scope. This skill owns the page's structure, visuals, copy and iteration. It borrows, and does not restate:

Voice and diagram-by-diagram pacing: the teach skill.
Gathering the facts: the how / research skills, or explorers you brief.
The page contract (CSP, fonts, title, responsive rules): the Artifact tool's quickstart result, called with intent: "other".

1. Check the evidence

Research comes before the outline. The page is shared, so its numbers become the team's numbers.

Check yourself every number and claim that drives the recommendation. A subagent's figure stays the subagent's until you have re-read its source or re-run its query.
When two reports disagree, read the cited source yourself. One read settles it; a third opinion does not.
A "never" or "always" claim about a system's states is model-checked or dropped. Prose reasoning about state machines misses interleavings.
Copy numbers and counts exactly as the source states them. A rounded count ("about 10") where the source lists 8 is an error a reader will find.