technical-articles
Technical Articles
All articles must follow writing-voice rules. This skill owns article shape; writing-voice owns house voice and punctuation.
Core Principles
Title should BE the takeaway, not a topic. "Write Context to a File, Not a Prompt" not "Context Management in Agent Workflows".
Lead with a strong opening paragraph that states the key insight in plain language. Reader should get it in 5 seconds. Then go straight into code. Don't force a blockquote or pull-quote after the opening; if the insight needs a quotable summary, the opening paragraph already is one.
Code speaks louder than prose. Show real examples from actual codebases, not abstract foo/bar illustrations. If the code is self-explanatory, don't over-explain.
Preserve the article's altitude. If the draft is a general lesson with a real code example, do not recenter it around the current project problem. The code is evidence for the lesson, not automatically the subject. Keep the reusable insight in the foreground and put project-specific mechanics in specs, reference docs, or implementation notes.