bloglisted

# Draft a tech blog post (velog, work-docs) Write a tight, visuals-first Korean tech blog post for **velog**, saved as a draft in the public work-docs repo. **velog does not render Mermaid**, so every diagram becomes an image here (you upload those images to velog when publishing). ## Step 0: Prereqs - work-docs cloned at `${WORK_DOCS_REPO:-$HOME/Devel/work-docs}` (shared with note/worklog). - `curl` (for Kroki diagram rendering). For data charts, the report skill's venv + `figures.py`. Optional: an Excalidraw skill for hand-drawn diagrams. ## Step 1: Scaffold the post folder ```bash bash <skill-base-dir>/assets/new_blog.sh <slug> ``` Creates `blog/<YYYY-MM-DD>-<slug>/index.md` + an `assets/` folder, and prints the draft's GitHub URL. ## Step 2: Ground it (do not write from memory) Verify facts before writing: **cubrid-manual**, **cmt-manual**, **Understand-Anything** (if installed), and the real code. A tech post must be correct. Cite sources in 참고. ## Step 3: Write the post (minimal text, visuals-first) Korean. Structure: 제목 → 요약(1~2줄) → 들어가며(왜 읽나, 무슨 문제) → 핵심 섹션들 → 정리 → 참고. - 핵심 텍스트만: 짧은 문단, 개조식. - 개념 설명은 **글보다 그림**으로 (다음 단계에서 이미지로). - 표는 비교·수치, 코드블록은 코드·로그. - em-dash(`—`)는 쓰지 않는다: 쉼표·콜론·괄호·마침표로 대체. ## Step 4: Make visuals as IMAGES (velog cannot render Mermaid) Put each source in `assets/`, render it to an image, and embed with ``. - **Diagram-as-code** (Mermaid / Graphviz / D2 / PlantUML): write `assets/diagram-N.mmd`, then render to PNG for