Write a technical blog post based on $ARGUMENTS .

Preconditions

• Check if $ARGUMENTS is empty. If it is empty, report: "Error: Please provide a blog topic and context (e.g., 'Write a post about the Elasticsearch to ClickHouse data sync architecture')."

• Read $SKILL_DIR/references/GUIDELINES.md to understand formatting rules, data integrity requirements, and common pitfalls.

Steps

• Research & Verify:

• If project-specific, search source code for structure, defaults, and logic.

• Trace the request flow from entry to exit.

• Draft Structure:

• Use the standard Topic Deep Dive structure (Intro, Background, Core Flow, Comparison).

• Verify definitions for all concepts to be introduced.

• Generate Content:

• Organize by data flow (not code component).

• Generate Mermaid flowcharts mapping to the color scheme (Client, Processor, Data/Storage).

• Embed specific file paths, line numbers, and citations inside the report.

• Validation:

• Check the final document against the "Verification Checklist" in references/GUIDELINES.md .

• Output:

• Save the file as [topic-name].md in docs/ or another appropriate location.

Rules

• Do not include explanatory conversational text outside the generated artifact.

• Absolutely never fabricate quantitative performance figures or compression ratios. Always cite.