Technical writing
Use only authoritative context already present or explicitly supplied. Leave research, investigation, debugging, and
fact-checking to the main agent. Produce a supportable partial result and identify material gaps instead of inventing
facts, causes, requirements, risks, examples, or conclusions.
Apply these invariants in order:
- Preserve supported technical meaning and requirement strength.
- Preserve terminology, certainty, conditions, exceptions, causality, commands, identifiers, paths, values, and units.
- Follow explicit user instructions, then project guidance, nearby conventions, existing structure, and minimal
generic organization.
- Improve precision, concision, ambiguity, and information density.
Apply grammar, punctuation, certain clarity improvements, terminology consistency, and removal of semantic duplication
inline. Return additions, removal of distinct information, examples, analogies, major restructuring, changed emphasis,
and ambiguous claims as author-judgment suggestions.
Remove unnecessary throat-clearing, generic introductions or conclusions, unsupported significance claims, repetitive
generic transitions, synonym cycling, immediate paraphrastic repetition, and empty generic sections. Retain useful
repetition and predictable structure. Optimize for clear technical prose, not detector evasion or artificial
humanization.
For documentation, use technical-docs. For reader-oriented technical articles, use tech-blog.
1---2name: technical-writing3description: Compose, edit, or review concise technical prose while preserving supported claims, terminology, certainty, conditions, causality, commands, identifiers, and values. Use directly for technical notes, comments, issues, explanations, and other small technical-writing tasks; use technical-docs or tech-blog for substantive workflows.4---56# Technical writing78Use only authoritative context already present or explicitly supplied. Leave research, investigation, debugging, and9fact-checking to the main agent. Produce a supportable partial result and identify material gaps instead of inventing10facts, causes, requirements, risks, examples, or conclusions.1112Apply these invariants in order:13141. Preserve supported technical meaning and requirement strength.152. Preserve terminology, certainty, conditions, exceptions, causality, commands, identifiers, paths, values, and units.163. Follow explicit user instructions, then project guidance, nearby conventions, existing structure, and minimal17 generic organization.184. Improve precision, concision, ambiguity, and information density.1920Apply grammar, punctuation, certain clarity improvements, terminology consistency, and removal of semantic duplication21inline. Return additions, removal of distinct information, examples, analogies, major restructuring, changed emphasis,22and ambiguous claims as author-judgment suggestions.2324Remove unnecessary throat-clearing, generic introductions or conclusions, unsupported significance claims, repetitive25generic transitions, synonym cycling, immediate paraphrastic repetition, and empty generic sections. Retain useful26repetition and predictable structure. Optimize for clear technical prose, not detector evasion or artificial27humanization.2829For documentation, use `technical-docs`. For reader-oriented technical articles, use `tech-blog`.
sandipb