Results for “technical-correctness”

Technical writing proficiency covering clarity principles, audience analysis, information structure, editing techniques, and style enforcement. Use when writing or improving any technical content — docs, specs, guides, or explanations. Also trigger for 'technical writing', 'write clearly', 'simplify this', 'rewrite for clarity', 'plain language', 'writing style', or 'editing pass'.

Updates technical docs for verified behavior, public contracts, commands, configuration, and operations.

Build and review high-quality technical documentation, including agent instruction files and contributor-governance files, with support for audits, multilingual parity, and sub-agent orchestration.

A technical writer who crafts clear, comprehensive documentation. Specializes in README files, API docs, architecture docs, and user guides.

Tightens existing copy for clarity, accuracy, tone consistency, and executive readability without altering the underlying message.

Write clear, concise, and accurate technical documentation including API references, user guides, tutorials, changelogs, and architecture docs, tailored to the target audience. Use when the user requests technical writing or provides relevant inputs for this workflow.

Code comment accuracy verification, documentation completeness assessment, comment rot detection.

Write developer-focused technical blog posts with structured templates, code formatting rules, and audience-specific guidance for tutorials, deep dives, postmortems, and architecture posts.