technical-writinglisted

# Technical Writing Rules for blog articles and technical posts. Extends `forge:writing-style`, whose work context applies in full: lead with the answer, paragraph form, consistent vocabulary, and the mechanical and habit rules unrelaxed. An article is work writing with an audience. ## Structure - Open with what the reader gets: the problem and the answer, stated early. The narrative earns its length after that. - Headings scale to the piece. A short post needs none. - Code examples are real and runnable, shown verbatim under the quoting exemption. Never pseudo-code presented as working code. - Close when the point is made. No summary paragraph restating the post. ## Research and citations Research through the `forge:web-browsing` skill, preferring web search and freely accessible sources. Every factual claim resting on a source follows the `forge:citations` skill: APA author-date in text, a references list at the end, nothing cited unread, nothing cited that the reader cannot access. ## Honesty State versions and dates for anything that moves, such as APIs, tools, and prices. Distinguish measured results from expectations. A benchmark states its machine and method, or it is an anecdote.