Slide it

Build the page as a presentation: a stack of screens, each answering one question. The question is set small, the answer in one or two sentences set large, and under it a live scene shows the thing happening: customers queueing, air flowing through an engine, money chasing goods. The reader plays with one control and watches the scene change, so they understand by seeing, and can stop at any screen understanding something. The page feels like a well-made app for its subject. artifact-design keeps the platform rules (themes, phone width, CDNs, the single check); the user installed this skill, so where its rules differ from artifact-design's defaults, read them as the user's own words.

1. Find the main point

Write one sentence: what the reader should understand or decide after the first screen.

2. Open the nearest example

Open the example closest to this content and read it whole before planning: examples/explainer.html (how something works), examples/decision.html (should we, which one), examples/plan.html (a plan, a trip, a timeline). It is the bar for the structure, the scenes and the code; build this page the same way.

3. Plan the screens

List the screens. Screen 1 lets the reader find the main point by watching and playing. Each next screen answers the question the one before raises (why, how, how much, what next); a new topic starts only when the content changes subject. Four to seven screens.