design", with these sections in order:
1. Header: a one-sentence summary, plus zoom pills reading "Level 1 · … / Level 2 · … / Level 3 · …" for the levels produced.
2. One card per diagram, each with a kicker (e.g. "Level 2 · Flowchart · Design patterns"), a heading, a caption and the diagram. Use ``, since artifacts render Mermaid natively.
3. A key that maps each plain word to its pattern name. For example: Way in → driving adapter, Plug → port, Provider behind a plug → adapter, Swappable rule → strategy.
4. Open questions marked ⚑, if any.
Follow-up requests ("add Level 3 for payments", "just redo the flowchart") update the SAME artifact instead of creating a new one.
Fallbacks:
- No artifact tool → a Notion page using the "Write a design doc page with diagrams" outline, with the same diagrams.
- No Notion either → Mermaid blocks in chat.
## Done when
- [ ] Only the requested levels were produced, and only their skills were loaded.
- [ ] The same worked example runs through every level.
- [ ] No two diagrams tell the same story.
- [ ] The output link is returned with one line per level produced.
## Reference
The first finished example is the "Booking modules" Claude artifact (court booking, PayMongo and Stripe adapters, pricing strategies), built 2026-11-10.