# Prompt: Create a Doc in API Format

Create a concise technical documentation page for the given code, module, or feature.

Requirements:
- Use the smallest document that fully answers the task.
- Prefer tables for methods, functions, classes, options, or fields.
- Use ordered lists for flows, lifecycles, call sequences, and setup steps.
- Keep descriptions to 5 words or fewer unless more detail is required.
- Do not explain concepts that are already obvious from the code.
- Focus on inputs, outputs, defaults, flags, and special behavior.
- Include only the sections that add value for the target doc type.
- If there are overrides, variants, or theme-specific implementations, explain how to overwrite them with a basic generic example (do not use real code but <placeholders>).
- Add short human notes only when needed to explain flow, refactors, or extension points.
- Match existing repo doc style and naming.
- Keep wording technical and compact.

Output rules:
- Write the final content directly in Markdown.
- Use short headings.
- Prefer one table per API area or method group.
- Prefer numbered `1. 2. 3.` steps for ordered behavior.
- Avoid examples unless they are necessary.
- Avoid redundant prose.
- If the doc needs a source path, include it once near the top.

Template:

# <Doc Title>

<One short summary sentence.>

## <Section>

| Item | Inputs | Description |
|---|---|---|
| `<name>` | `<inputs>` | `<short description>` |

## Flow

1. `<first ordered step>`
2. `<second ordered step>`
3. `<third ordered step>`

## Notes

| Item | Note |
|---|---|
| `<name>` | `<short note>` |

## Variants

- `<file or variant>`
- `<file or variant>`