playbooks

home / skills / ghostscientist / skills / turn-this-feature-into-a-blog-post

turn-this-feature-into-a-blog-post skill

/skills/turn-this-feature-into-a-blog-post

This skill converts code implementations into engaging Markdown blog posts, guiding readers from what and why to how with clear explanations and examples.

npx playbooks add skill ghostscientist/skills --skill turn-this-feature-into-a-blog-post

Review the files below or copy the command above to add this skill to your agents.

Files (1)
SKILL.md
2.8 KB
---
name: turn-this-feature-into-a-blog-post
description: Generates a technical blog post from code implementation. Use when asked to write a blog post about a feature, explain an implementation for a blog, document code as a blog article, or create technical content from source code. Triggers on phrases like "write a blog post about", "turn this into a blog", "create a technical article", or "explain this for a blog".
---

# Turn This Feature Into a Blog Post

Generate a Markdown blog post that explains a code implementation in an engaging, educational way.

## Process

1. **Analyze the implementation** - Read and understand all relevant code files, tracing the feature from entry point to completion
2. **Identify the narrative** - Find the core problem being solved and why it matters
3. **Structure the post** - Organize as What → Why → How (from first principles)
4. **Write accessibly** - Use friendly, conversational language while maintaining technical authority
5. **Output Markdown** - Create a complete `.md` file ready for publishing

## Blog Post Structure

### Title
- Clear, specific, and searchable
- Format: "How We Built [Feature]" or "Building [Feature]: A Deep Dive"

### Introduction (2-3 paragraphs)
- Hook the reader with the problem or outcome
- Briefly explain what the feature does
- Preview what readers will learn

### The What (1-2 sections)
- Describe the feature from the user's perspective
- Include screenshots or diagrams if applicable
- Keep technical jargon minimal

### The Why (1-2 sections)
- Explain the problem this solves
- Discuss alternatives considered and why this approach won
- Connect to broader engineering principles

### The How (2-4 sections)
- Walk through the implementation from first principles
- Include relevant code snippets with explanations
- Explain non-obvious decisions
- Build up complexity gradually

### Conclusion
- Summarize key takeaways
- Mention potential future improvements
- Invite engagement (questions, feedback)

## Writing Style

- **Friendly but authoritative** - Write like a knowledgeable colleague explaining over coffee
- **First-person plural** - Use "we" to create shared ownership
- **Active voice** - "We built" not "It was built"
- **Show, don't just tell** - Use code examples liberally
- **Explain the "why"** - Every code block should have context
- **Avoid jargon walls** - Define terms on first use

## Code Snippets

- Include only relevant portions, not entire files
- Add comments for non-obvious lines
- Use syntax highlighting with language tags
- Provide context before each snippet

## Output

Save the blog post as a Markdown file with:
- Kebab-case filename matching the title
- Frontmatter with title, date, author, and tags (if appropriate for the target platform)
- Properly formatted headers, code blocks, and lists

Overview

This skill generates a ready-to-publish technical blog post from a code implementation. It reads implementation files, identifies the core narrative, and produces a Markdown article organized as What → Why → How with code snippets and frontmatter. The output is a kebab-case .md file formatted for easy publishing. Use it to turn feature code into educational, shareable content.

How this skill works

We analyze the relevant source files and trace the feature from entry point to completion to understand behavior and intent. We distill the problem the code solves and choose a clear narrative, then structure the post into title, introduction, What, Why, How, and conclusion. The skill includes selective code snippets with explanatory comments, friendly first-person plural voice, and Markdown frontmatter for publishing. The final deliverable is a complete .md file ready to drop into a blog.

When to use it

  • You have a working feature and need an approachable blog post explaining it.
  • You want to document an implementation for teammates or the public as a narrative article.
  • A designer or product owner asks for a technical write-up of how a feature works.
  • You need a publishable Markdown file including frontmatter and code snippets.
  • You want to convert PR or commit content into an educational article.

Best practices

  • Provide all relevant source files or a clear entry point so we can trace the implementation end-to-end.
  • Point out the audience (engineers, product managers, new hires) to tune tone and detail level.
  • Highlight non-obvious decisions or trade-offs so the post can explain the why.
  • Flag any sensitive data or proprietary code that must be excluded before processing.
  • Request preferred length or snippet depth (high-level overview vs line-by-line walkthrough).

Example use cases

  • Convert a new authentication flow implementation into a ‘How We Built Authentication’ deep dive.
  • Document a complex refactor as a narrative showing problem, alternatives, and final approach.
  • Produce an explainer for a library integration, including code examples and migration tips.
  • Turn a small feature demo into a blog post for onboarding or marketing channels.
  • Create a technical how-to for an open-source contribution with runnable snippets.

FAQ

Can you include full source files in the post?

We include only relevant snippets with context and comments; we avoid dumping entire files to keep the article focused and readable.

How do you handle proprietary or sensitive code?

Flag any sensitive parts up front. We will omit or redact those sections and explain high-level behavior instead.