Guide
Structured information guide
Well-structured information — tables, ordered procedures, explicit criteria — survives summarization far better than prose. Structure forces completeness and makes omissions visible.
01Tables for anything comparable
- Specs, plans and feature comparisons belong in HTML tables with header cells, not screenshots.
- One row per item; one column per attribute; no merged-cell ambiguity.
- State units and conditions next to numbers.
02Procedures as sequences
- Numbered steps for anything sequential; each step starts with a verb and names its target.
- State prerequisites and expected outcomes at the start and end.
- Keep branching logic explicit ('If X, do Y; otherwise Z') rather than implied.
03Criteria made explicit
- Turn vague guidance ('choose what suits you') into checkable criteria.
- List constraints and edge cases — these are exactly what synthesis tools need to answer follow-ups accurately.