tech-blog-writer

Generate formal Korean Tistory blog posts with diagrams, code blocks, and tables.

13|2|Updated Feb 21, 2026
One-click install
npx skills add https://github.com/mangowhoiscloud/geode --skill tech-blog-writer-mangowhoiscloud
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: tech-blog-writer
Source: https://github.com/mangowhoiscloud/geode/tree/main/.claude/skills/tech-blog-writer
Command: npx skills add https://github.com/mangowhoiscloud/geode --skill tech-blog-writer-mangowhoiscloud

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill helps users generate high-quality technical blog posts in a specific Korean formal writing style, complete with architectural diagrams, code explanations, and structured summaries.

Core Features & Use Cases

  • Structured Content Generation: Follows a defined template for introductions, body sections (including architecture, code, and design rationale), and conclusions.
  • Style Adherence: Maintains a formal, polite Korean tone ("합니다", "됩니다") and specific formatting rules for code and diagrams.
  • Use Case: Generate a detailed blog post explaining a new microservice architecture, including Mermaid diagrams, Python code snippets with design intent explanations, and a comparison table of different implementation choices.

Quick Start

Write a tech blog post about the 'LangGraph' library following the Tistory style guide.

Frequently Asked Questions about tech-blog-writer

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I generate a Korean technical blog post with architectural diagrams and code blocks?

To generate a Korean technical blog post with architectural diagrams and code blocks, provide your technical topic to get structured content featuring Mermaid diagrams, code snippets with design intent, and formal Korean text.

What is the best way to write a Tistory style tech blog post in Korean?

Writing a Tistory style tech blog post in Korean requires maintaining a formal tone using specific polite endings like 합니다 and 됩니다, while structuring content with introductions, comparison tables, and conclusions.

Can I include design rationale and comparison tables when generating technical documentation?

You can include design rationale and comparison tables when generating technical documentation by requesting structured sections that explain code design intent and compare different implementation choices side by side.

Does the generated Korean tech blog content follow a specific length and structure?

The generated Korean tech blog content follows a specific length and structure, adhering to defined guidelines for introductions, body sections detailing architecture and code, and structured summary conclusions.

How do I explain a microservice architecture using a formal Korean writing style?

To explain a microservice architecture using a formal Korean writing style, generate a post that incorporates architectural diagrams, Python code snippets with design intent explanations, and a comparison table of implementation choices.