Apply writing guidelines and templates

Use Settings → AI preferences to define reusable writing guidance for future generation. You can choose which generators receive it and, as a team owner, enforce it for your team.

Guidelines: how to write

Use short, concrete rules about terminology, audience and tone. For example:

Write for engineers joining our team.
Explain prerequisites before commands.
Use our product names consistently.
Describe only behavior supported by the source.

Guideline text supports up to 4,000 characters. You can type it or upload a supported Markdown/text file; the upload limit is 50 KB and the resulting text must fit the relevant content limit.

Template: how to organize

Use a Markdown template for the expected structure:

## Purpose
## Before you start
## Steps
## Expected result
## Troubleshooting

Template text supports up to 12,000 characters. Choose a structure appropriate to the output: the same headings may not suit both a release note and an API reference. Enable Strict template when you want closer adherence to the headings and order, then inspect the output; it does not guarantee every requested structure fits every source.

Apply the settings

Select the generators that should use the preferences and save. Changes apply to subsequent generation; they do not silently rewrite saved pages.

A team owner can enable Force team members to use these settings. Members then see the enforced settings as read-only. If you cannot edit them, ask your team owner rather than creating conflicting personal instructions.

Run a small, representative generation before a large documentation build. Review whether the preferences improve clarity and whether the generated structure still fits the source.