docs: extract guide design into reusable skills

2026-09-04 02:57:42 +00:00
parent 5ff258ded5
commit a7034db94b
11 changed files with 307 additions and 0 deletions
@@ -0,0 +1,16 @@
+# Page anatomy
+
+Use this as a compact design contract for a new AI For Dummies chapter.
+
+1. **Orientation** — eyebrow, chapter number, title, short promise, language control.
+2. **Thesis** — one sentence that changes how the reader sees the topic.
+3. **Model** — a pipeline, tree, timeline, or comparison that makes the relationship visible.
+4. **Practice** — a copy-ready prompt, command, example, or tiny exercise.
+5. **Proof** — source paths, checks, observed behavior, and the boundary between advice and enforcement.
+6. **Transfer** — a small “use this next” link to the next chapter or deeper source.
+
+Keep the first screen editorial and calm. Let code, diagrams, and controls earn their space by teaching something. Avoid a generic hero followed by an undifferentiated card grid.
+
+## Section contract
+
+Each new section should answer: what does the reader learn, what is the visible proof, what can they copy or try, and what source supports it? Add its copy to the language map before adding a control. Add its slug to navigation only after the section has a stable purpose.