Plate Docs

Own Plate's public documentation experience: house style, page composition, example coverage, setup, API teaching, MDX and navigation. Use pstack:technical-writing for prose, voice and document modes. Its general rules serve this project's house style. A docs edit keeps code, commands, identifiers, frontmatter and link targets unchanged unless the change covers them, and keeps numbers, versions and names tied to their source. It also keeps obligation words (must, may, never), uncertainty and meaningful scope limits as strong as the source says; never turn a possibility into a guarantee, whatever technical-writing says about hedging. Code snippets follow the repository formatter's two-space indentation, not technical-writing's tab rule.

Handle the requested page, feature or documentation audit. An audit reports source-backed gaps; edits stay within the requested scope. General prose in plans, reports, READMEs and PR descriptions goes directly to pstack:technical-writing. For a tiny copy edit, read the text and resolve changed links without loading unrelated docs mechanics; an English page edit still rebuilds the docs registry where the verify table's registry row applies.