blog-writing

name	blog-writing
description	Convert Obsidian notes or curated study material into public MDX blog posts for this Next.js portfolio blog. Use when the user asks to publish notes, move notes to the blog, write a post from existing notes, revise a blog article, choose blog category/tags, or prepare MDX content under content/blog.

Blog Writing

Overview

Write public blog posts only after reading the relevant private notes or source material. The blog is a polished synthesis layer; notes/ is the working knowledge layer.

Required Context

Before writing a post:

1. Read relevant files under notes/.
2. Read nearby posts in the target category under content/blog/.
3. Check app/lib/posts.ts slug/category behavior if creating a new folder or filename pattern.
4. Confirm whether the content is public-safe if notes include personal, private, or uncertain material.

Do not generate a blog post from generic knowledge when related notes exist.

Destination

Create posts under:

content/blog/<topic>/<slug>.mdx

The current slug logic prefixes the folder name unless the filename already starts with that folder name. Example:

content/blog/quant/return.mdx -> /blog/quant-return
content/blog/os/introduction.mdx -> /blog/os-introduction

Frontmatter

Every post needs:

---
title: "0x01. 글 제목"
publishedAt: "YYYY-MM-DD"
category: "Category"
tags: "Tag A, Tag B, Tag C"
summary: "목록, 검색, SEO에 쓰이는 짧은 요약."
---

Use category names that the blog sidebar can group when possible:

• Data Engineering: Kafka, Spark, Flink, Airflow, dbt, Data Engineering, Elasticsearch, OpenTelemetry
• AI: LLM, RAG, AI Agent
• CS: 컴퓨터 보안, 컴퓨터 네트워크, 운영체제, 데이터베이스 시스템, 알고리즘 분석
• PS: 바킹독 강의

For finance/quant posts, use Finance for basic financial literacy and Quant for quant research/system topics until the category system is expanded.

Writing Style

Match existing posts:

• Korean primary prose with English technical terms in parentheses when helpful.
• Start with a concrete motivation or problem, not a table of contents.
• Explain concepts from first principles.
• Use H2/H3 headings.
• Use lists for definitions or comparisons.
• Use code blocks only when they clarify implementation.
• Keep tone educational, direct, and grounded.
• Avoid pretending uncertain claims are facts.

Good post flow:

Opening motivation
Why the concept matters
Core definition
Concrete example
Common pitfalls
Connection to adjacent concepts
Short closing summary

MDX Rules

• Use markdown images with absolute public paths: ![alt](/images/blog/.../image.png).
• Move publishable images to public/images/blog/<post-slug>/.
• Convert Obsidian links [[Note]] to public links only when the target post exists.
• Remove private note scaffolding such as 상위:, raw source comments, or unresolved TODOs.
• Keep math compatible with remark-math and rehype-katex.
• Keep code blocks language-tagged.

Workflow

1. Select source notes.
2. Decide target category, slug, title, and post angle.
3. Draft the MDX post.
4. Check internal links and image paths.
5. Run pnpm build.
6. Record completed work in done.md.

If the user only asks for a draft, do not publish into content/blog; provide the draft or place it in notes/10. Inbox/ depending on the request.