菜单
Technical blog post writing guide. rooftopsnow.tistory.com style — Korean formal technical prose, architecture diagrams, code blocks + design intent commentary, table comparisons, checklist wrap-up. Triggers on "blog", "포스팅", "블로그", "기술 글", "tech blog".
默认使用会先检查来源的 Prompt；你也可以切换为直接命令，或下载本地副本。
决定是否安装前，请先阅读 SKILL.md，以及 SkillsMP 当前展示的配套文件。
基于 SOC 职业分类
用 Codex 或 Claude 帮你安装 复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。
直接命令不会经过审查 Prompt；运行前请先检查来源。
npx skills add https://github.com/mangowhoiscloud/geode --skill tech-blog-writer命令会保持在同一行。复制前请横向滚动并检查完整内容。
想先保存到本地？可下载 SkillsMP 当前能够提供的文件。
正在显示 SKILL.md
| name | tech-blog-writer |
| description | Technical blog post writing guide. rooftopsnow.tistory.com style — Korean formal technical prose, architecture diagrams, code blocks + design intent commentary, table comparisons, checklist wrap-up. Triggers on "blog", "포스팅", "블로그", "기술 글", "tech blog". |
| Item | Rule |
|---|---|
| Tone | Formal Korean ("합니다", "됩니다", "입니다") |
| Perspective | First person ("In this post", "This is a design decision") |
| Code explanation | Design intent commentary in > quote blocks |
| Emphasis | Bold, inline code, > Note boxes |
| Emoji | Do not use (only when explicitly requested by user) |
# Title: [Technical Concept] — [Subtitle/Core Value]
> Date: YYYY-MM-DD | Author: geode-team | Tags: [tag1, tag2]
## Table of Contents
1. Introduction (Problem definition)
2~N. Body sections (Architecture → Implementation → Verification)
N+1. Wrap-up (Summary table + Checklist)
---
## 1. Introduction
Problem definition in 1 paragraph → Solution strategy in 1 paragraph.
Make clear "why the reader should read this."
## 2~N. Body
### Section title: "N. Concept Name + Detailed Description"
Each section pattern:
1. One-line concept summary
2. Architecture diagram (Mermaid or ASCII)
3. Core code block (Python, with type hints)
4. > Design intent commentary block
5. Comparison table (config values, trade-offs, etc.)
## N+1. Wrap-up
### Summary
| Item | Value/Description |
|---|---|
| ... | ... |
### Checklist
- [ ] Item 1
- [ ] Item 2
> quote block immediately after code block explaining "why this design"# geode/infrastructure/ports/llm_port.py# geode/infrastructure/ports/llm_port.py
class LLMClientPort(Protocol):
def generate(self, system: str, user: str, **kwargs) -> str: ...
def generate_json(self, system: str, user: str, **kwargs) -> dict: ...
By abstracting the concrete LLM call implementation (Claude, GPT), models can be swapped by simply replacing the adapter. This is a design decision following the Hexagonal Architecture Port/Adapter pattern.
fill:#3B82F6, fill:#10B981, etc.)| Type | Length | Code:Explanation ratio |
|---|---|---|
| Concept introduction | 3000-5000 chars | 3:7 |
| Architecture deep-dive | 6000-10000 chars | 4:6 |
| Implementation tutorial | 8000-12000 chars | 6:4 |
Docs 사이트 (`site/` Next.js) 의 본문/JSX/markdown 링크 audit. broken 내부 링크 탐지, build-time copy 인지, 옵트인 HTTP probe. 신규 페이지 추가 / slug 이전 / chapter 삭제 후 회귀 방지. Triggered by "broken link", "404", "docs link", "hyperlink", "링크 점검", "링크 깨짐", "audit links", "link checker" 키워드.
Scope, preregister, execute, audit, normalize, and publish GEODE evaluations with research-question, reproduction, attempt-lineage, trajectory, verifier-receipt, and immutable artifact contracts. Use for benchmark runs or comparisons, eval-artifact and cache-accounting audits, GPT or subscription result normalization, research question or hypothesis framing, retry diagnosis, trajectory publication, DPO or reward-data readiness reviews, and requests involving MCPMark, tau2, BFCL, Agent-World, HAL, Terminal-Bench, or Toolathlon.
GEODE evidence-first development workflow. Use for feature work, provider/model changes, GUI/computer-use work, PDF/document ingestion, observability/schema/event/state changes, verification planning, GitFlow merge prep, and requests to "follow the workflow" or "scaffold the process".