---
name: structure_guide
description: Best practices for structuring technical documentation
---

# Structure Guide

When structuring technical documentation:

1. **Introduction first**: Start with what the document covers and why it matters (1-2 sentences).

2. **Prerequisites**: List what the reader needs to know before reading.

3. **Logical flow**: Arrange content from simple to complex. Each section should build on the previous.

4. **Headings**: Use descriptive headings that summarize the section content. Avoid vague titles like "Overview" or "Details".

5. **Code before explanation**: When mixing code and prose, show the code first, then explain it.

6. **Summary or next steps**: End with a summary of key takeaways or links to related topics.

When applying this skill, evaluate whether the content follows this structure and suggest how to reorganize it.
