Andocs authoring

Find the documentation root from the request or repository before editing. If multiple roots remain plausible, ask which one to use. Follow the repository's language and preview rules.

Read the reference that matches the work:

• Markdown rendering — read when writing diagrams, math, interactive html-preview blocks, or Andocs-specific links.
• Prototypes — read when creating or editing prototype.json, HTML pages, shared assets, or prototype blocks.
• Review status and releases — read when a prototype uses screen review badges, releases.json, or <id>@<release>.html screen variants.
• Browser-local state — read when prototype data must survive refresh in the same browser.
• Web Components — read when a prototype uses Custom Elements or Shadow DOM.

For a requested local preview, first identify the documentation root and check that Bun is available. Use bunx andocs@latest --path <docs-root> only when starting a server is authorized by the user and the repository instructions. The CLI help is bunx andocs@latest -h.

Before finishing, check that referenced files exist, fenced blocks use the right language, and any prototype state handles unavailable storage. The public Andocs demo shows a complete prototype repository.