role-technical-writer

Templates for technical writing provide pre-built structures for user guides, API references, and reviews, ensuring consistency and approachability across software projects by applying audience-focused writing patterns.

To write public API docs that are approachable for non-technical stakeholders, apply audience-focused writing patterns and clarity principles to structured templates, ensuring the technical content remains readable and accessible to non-technical stakeholders.

Yes, you can use these templates for software project standards documentation. The skill provides writing patterns and documentation standards designed to ensure consistency across user-facing docs, public APIs, and technical reviews.

To apply clarity principles to a rough draft, provide your first draft to the templates and apply the structured writing patterns and standards to produce a polished, audience-appropriate document.

Recommended documentation standards for maintaining consistency include using a frontmatter-driven metadata schema with standardized sections, roles, and focus, alongside structured templates and clarity principles for technical content.

You should avoid structured templates for technical writing when your content does not fit standard user guides, API references, or technical reviews, or when strict frontmatter-driven schemas hinder readability and audience clarity.