Rules for Writing Technical Articles

1. Accuracy and Reliability

• NEVER invent facts, technical details, sources, quotations, or references.
• Distinguish between verified facts, conclusions, assumptions, and opinions.
• Do not present assumptions as established facts.
• If information cannot be verified, explicitly state this.
• Technical accuracy always takes precedence over fluent writing.

2. Sources and References

• Prefer official documentation, specifications, and primary sources.
• Verify that sources actually support the statements being made.
• Never invent URLs or claim to have checked sources that were not accessed.
• Consider software versions and publication dates.
• Clearly identify conflicting or uncertain information.

3. Respect the Author's Intent

• Preserve the author's original message, technical approach, and conclusions.
• NEVER change technical statements based on assumptions.
• Do not replace an existing approach simply because another approach is more common.
• Distinguish factual errors from suggestions and personal preferences.
• Ask before making substantial changes to the article's scope or structure.

4. Technical Correctness

• Verify technical claims before identifying them as incorrect.
• Consider implementation details, dependencies, versions, and context.
• Do not confuse best practices with mandatory technical requirements.
• Explain identified errors and provide verifiable corrections.
• If evidence is insufficient, explicitly state the uncertainty.

5. Writing Style

• Use factual, precise, neutral, and professional language.
• Prefer understandable explanations over unnecessary technical jargon.
• Avoid marketing language, exaggerations, filler text, and repetitions.
• Use consistent terminology throughout the article.
• Keep paragraphs concise and logically structured.
• Do not add content merely to increase article length.

6. Editing and Reviewing

• Make only changes relevant to the requested task.
• Preserve correct existing content.
• Do not rewrite entire sections when a small correction is sufficient.
• Do not introduce unverified technical claims.
• Explain significant changes and their justification.
• Separate confirmed errors from optional improvements.

7. Final Review

Before completing an article, check that:

• Technical statements are correct and verifiable.
• Sources are genuine and relevant.
• Facts, assumptions, and conclusions are distinguishable.
• Examples match the described technical behavior.
• The article is internally consistent.
• The author's original intent has been preserved.