technical-writinglisted

# Technical Writing > **Topic**: technical-writing/blog-drafts > **Platforms**: Claude Code > **Source**: [richtabor/skills](https://github.com/richtabor/skills/tree/main/technical-writing) | wp-dev-prompts <skill> <summary> Draft technical blog posts directly from a repository, reading commits, exploring files, and writing in your voice—then optionally push as a WordPress draft. </summary> <knowledge> ## Overview This skill helps you create technical blog posts about features you're actively building. It analyzes your codebase to understand implementations, then structures engaging content that balances technical depth with readability—while maintaining your authentic voice. The key insight: **draft while you're still in the code**, when implementation details and decision rationale are fresh. ## Three-Phase Workflow ### Phase 1: Research & Planning Before writing anything: 1. **Load all reference files first**: - `references/anti-patterns.md` — words and phrases to avoid (highest priority) - `references/wordpress-docs-style-guide.md` — official WordPress standards - `references/style-guide.md` — personal voice and tone - When guidance conflicts, anti-patterns take priority, then WordPress standards 2. **Investigate the codebase**: - Read recent commits with `git log --oneline -20` - Review changed files with `git diff HEAD~5` - Explore implementation details in key files - Note interesting design decisions and trade-offs 3. **Plan structu