docs-writer

You can review and edit markdown files for documentation accuracy by analyzing code and existing docs. This ensures documentation accurately reflects the current codebase state while adhering to specific voice, tone, grammar, and formatting standards.

Maintain consistent voice and tone in project documentation by applying established structural and language standards. Reviewing text against specific style guidelines ensures clarity, accuracy, and consistency across all files within the docs directory.

This documentation writer works directly with standard markdown files. It specifically targets any `.md` files in the repository or files located within the `/docs` directory to ensure structural and formatting standards are met.

The best way to document a new feature is to investigate the codebase first, then write the user guide. This ensures all technical details are covered accurately and the language remains precise, clear, and aligned with project standards.

You should not use an automated documentation editor when code and existing documentation cannot be carefully investigated beforehand. Accurate writing and editing require understanding the current codebase state to prevent outdated or incorrect technical details.