Contents
Garden HandbookRecommended figures

Step diagram

Use this to explain something step by step, with room for detail inside a step

Schematic for Step diagram

Use this to explain something step by step, with room for detail inside a step.

This is not a time-scaled bar, not a checklist to follow, and not a stepper for watching state change.

Typora and VS Code / Cursor share this list. In the /garden picker, this row is the same figure and the same use case. Choosing it inserts a garden compose brief. Fill in your material and goal, then ask the AI to compile the post.

The built-in picker currently inserts that brief in Chinese. The English wording below is the same recommended brief, written for the English handbook so you can copy it when you write in English.

The recommended brief is a starting point, not a syntax lesson, and not the only valid form. You may still combine Markdown or safe HTML building blocks in the same garden compose fence.

```garden compose
Please make a "Step diagram" diagram in garden compose from the material and the communication goal I provide.

My material:
- (paste the original items and wording to keep)

My goal:
- (what the reader should see at a glance)

Please:
- Organize only from the material; do not invent facts or conclusions
- Handle the graphic syntax, layout, and mobile reading yourself; do not ask me to learn tags or write CSS
- "Step diagram" is the recommended starting point: Use a step diagram to make the order clear, and expand detail inside a step when needed. Do not turn it into a to-do list or a stepper unless the material really is that
- A recommended figure is not the only valid form; you may still combine necessary Markdown / HTML building blocks in the same compose fence
- Do not start a different author fence or a new syntax; use only garden compose
```