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

Included with Lifetime

$97 forever

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".

Writing & Docs

What this skill does


# 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

Files: 1

Size: 2.8 KB

Complexity: 9/100

Category: Writing & Docs

Source: https://github.com/ghostscientist/skills/tree/main/skills/turn-this-feature-into-a-blog-post

Related in Writing & Docs

jax-development

Included

Use this skill when the user is writing, debugging, profiling, refactoring, reviewing, benchmarking, parallelising, exporting, or explaining JAX code, or when they mention JAX, jax.numpy, jit, grad, value_and_grad, vmap, scan, lax, random keys, pytrees, jax.Array, sharding, Mesh, PartitionSpec, NamedSharding, pmap, shard_map, Pallas, XLA, StableHLO, checkify, profiler, or the JAX repo. It helps turn NumPy or PyTorch-style code into pure functional JAX, fix tracer/control-flow/shape/PRNG bugs, remove recompiles and host-device syncs, choose transforms and sharding strategies, inspect jaxpr/lowering/IR, and benchmark compiled code correctly.

Writing & Docsscripts

nature-article-writer

Included

Drafts, rewrites, diagnostically critiques, and style-calibrates primary research manuscripts for Nature and Nature Portfolio journals. Use when the user wants a Nature-style title, summary paragraph or abstract, introduction, results, discussion, methods, figure legends, presubmission enquiry, cover letter, reviewer response, or when a scientific draft sounds generic, jargon-heavy, structurally weak, or AI-ish and needs precise, broad-reader-friendly prose without inventing data, analyses, or references. Best for primary research articles and letters rather than reviews or press releases unless explicitly adapting one.

Writing & Docsscripts

deckrd

Included

Document-driven framework that derives requirements, specifications, implementation plans, and executable tasks from goals through structured AI dialogue. Use when user says "write requirements", "create spec", "plan implementation", "derive tasks", "structure this feature", "break down into tasks", or "document this module". Also use for reverse engineering existing code into docs (/deckrd rev). Do NOT use for direct code writing — use /deckrd-coder after tasks are generated. Do NOT use when the user only wants to run or fix existing code without planning.

Writing & Docsscripts

clinical-decision-support

Included

Generate professional clinical decision support (CDS) documents for pharmaceutical and clinical research settings, including patient cohort analyses (biomarker-stratified with outcomes) and treatment recommendation reports (evidence-based guidelines with decision algorithms). Supports GRADE evidence grading, statistical analysis (hazard ratios, survival curves, waterfall plots), biomarker integration, and regulatory compliance. Outputs publication-ready LaTeX/PDF format optimized for drug development, clinical research, and evidence synthesis.

Writing & Docsscripts

handling-sf-data

Included

Salesforce data operations with 130-point scoring. Use this skill to create, update, delete, bulk import/export, generate test data, and clean up org records using sf CLI and anonymous Apex. TRIGGER when: user creates test data, performs bulk import/export, uses sf data CLI commands, needs data factory patterns for Apex tests, or needs to seed/clean records in a Salesforce org. DO NOT TRIGGER when: SOQL query writing only (use querying-soql), Apex test execution (use running-apex-tests), or metadata deployment (use deploying-metadata).

Writing & Docsscripts

accelint-ac-to-playwright

Included

Convert and validate acceptance criteria for Playwright test automation. Use when user asks to (1) review/evaluate/check if AC are ready for automation, (2) assess if AC can be converted as-is, (3) validate AC quality for Playwright, (4) turn AC into tests, (5) generate tests from acceptance criteria, (6) convert .md bullets or .feature Gherkin files to Playwright specs, (7) create test automation from requirements. Handles both bullet-style markdown and Gherkin syntax with JSON test plan generation and validation.

Writing & Docsscripts