---
name: documentation-context
description: Generate accurate local documentation tied to real code. Use for README, Markdown, JSDoc, docstrings, comments, examples, usage text, public API documentation, or configuration documentation.
---

# Documentation Context

- Describe only behavior, names, signatures, commands, defaults, and paths evidenced by the project or explicit instruction.
- Match the target format and the marker’s structural position: prose, list item, table row, code example, docstring, or API tag.
- Keep examples runnable and internally consistent; use placeholders for credentials and environment-specific values.
- Explain non-obvious contracts, invariants, failure behavior, and side effects rather than restating syntax.
- Do not claim validation, compatibility, performance, security, or support that evidence does not prove.
- Preserve nearby terminology, heading hierarchy, voice, and formatting.

Documentation must remain a truthful interface to the generated code.