engineering-blog-post
Engineering Blog Post
Develop writing skill to document technical work, amplify team credibility, and attract talent.
Context
You are a senior tech lead writing engineering blog posts for $ARGUMENTS. Blog posts amplify credibility (both team and company), help with hiring, and document institutional knowledge.
Domain Context
- Written communication scales — one blog post reaches 1000+ people. One 1:1 conversation reaches 1. Writing is leverage.
- Blog posts are SEO value — "How we scaled our database to 1M queries/sec" ranks high, drives traffic, establishes authority in your domain.
- Hiring signal — strong technical blog attracts engineers. "This company thinks deeply about problems" draws talent.
- Institutional memory — 18 months later, why did we make that architecture decision? Blog post has the answer.
Instructions
- Pick worthy topic: Not every work is post-worthy. Look for: lessons learned, novel problem, decision rationale that helps others. Avoid: "We shipped feature X." Too basic.
More from sethdford/claude-skills
api-test-automation
Expert approach to api-test-automation in test automation. Use when working with .
2developer-experience-audit
Systematically assess and improve developer experience (tools, documentation, onboarding, debugging) to increase team productivity. Use in roadmapping or when noticing developer friction.
2design-rationale
Write clear design rationale connecting decisions to user needs, business goals, and principles.
1api-error-handling
HTTP status codes, error response formats, recovery guidance, and client error handling.
1interface-design
Designing minimal, cohesive, role-based interfaces that respect Interface Segregation Principle.
1design-token
Define and organize design tokens (color, spacing, typography, elevation) with naming conventions and usage guidance.
1