docs-writer

Technical documentation is crafted by writing, reviewing, and editing Markdown files, primarily within a `/docs` directory, ensuring content accuracy and clarity by referencing code and adhering to a specified style guide.

Yes, you can modify existing Markdown documentation like a README file by integrating new content sections, reviewing for clarity, and ensuring consistency with your project's style guide.

Ensuring documentation follows a style guide involves reviewing and editing Markdown content specifically for clarity, grammar, and consistency, aligning all new and existing text with established project standards.

Yes, the documentation writer works without external dependencies, relying solely on internal reference components to review code and edit Markdown files within your project directory.

Technical writing handles code references by directly cross-referencing source code during the content creation and editing process, ensuring the documented steps, features, and technical details remain strictly accurate.