docs

To write markdown documentation for an SDK feature page, draft the content by adhering to the project's voice, structure, and terminology. Ensure the page explains the problem, shows the recommended path first, and maintains code-verified accuracy without inventing unsupported behavior.

The best way to keep technical writing consistent across reference docs is to apply the project's specific structure, voice, and cross-reference rules during the review process. This ensures all pages remain aligned and easy for developers to use.

You revise existing AI Transport SDK docs by requesting a markdown rewrite that follows the project style guide. This process focuses the page on a single developer intent while updating features, concepts, or internals with accurate cross-references.

Yes, the docs review process supports concept and internals pages. It applies strict terminology and structure rules to feature pages, concept pages, reference pages, quickstarts, and internals docs to keep the SDK documentation accurate and consistent.

You should not use an automated markdown doc generator when a feature requires strict code-verified accuracy and specific cross-reference rules. Inventing unsupported behavior or ignoring the project's voice will degrade the quality of SDK reference and internals documentation.