docs-writer

To write a README with consistent style, apply standardized templates and frontmatter conventions that align terminology and tone across your project documentation. This ensures clarity and accessibility for user-facing guides.

Converting a product spec into a CONTRIBUTING.md involves refining the technical draft into a polished guide that aligns with your project style. This standardizes the structure and improves readability for contributors.

Yes, you can use markdown to standardize documentation across /docs directories by applying consistent layouts, terminology, and frontmatter conventions to maintain structural and tonal consistency throughout software projects.

Reviewing and editing technical documentation for tone and accuracy involves checking clarity, applying the project style guide, and refining the structure to ensure the content is accessible and consistent across all user-facing materials.

Yes, this documentation approach works for guides and API change notes by transforming them into polished, standardized drafts that align with the project's style guide and frontmatter conventions for technical accuracy.

You need to standardize in-doc style for software projects when you want to ensure consistent structure and tone across READMEs, guides, and CONTRIBUTING.md files, saving time and improving overall readability.