zenn-article-writer

Technical articles on Zenn should center on problem-solving narratives, explaining how a solution addresses a real-world developer problem. This Skill automates article generation with a structured template covering target readers, problem statements, solution overview, detailed What/Why/How sections, tested code samples, and actionable next steps, ensuring adherence to Zenn best practices and Japanese technical writing guidelines.

Document solutions by structuring content around the problem statement, solution overview, and detailed explanation of what, why, and how. Include relatable examples, tested runnable code, and results demonstrating the fix. This Skill enforces best practices like one idea per sentence, active voice, term definitions, and complete frontmatter to create articles that resonate with technical readers.

Yes. This Skill automates high-quality Zenn article generation while enforcing best practices: problem-solving focus, Japanese writing guidelines, one idea per sentence, active voice, clear definitions, What/Why/How explanations for major points, tested code samples, and mandatory follow CTAs. It adheres to Zenn's ARTICLE_TEMPLATE.md structure, saving hours of writing and formatting effort.

Zenn articles should use active voice, define terms on first use, explain concepts with What/Why/How reasoning, include tested runnable code samples, and follow a problem-solution narrative structure. This Skill integrates these standards—including Japanese technical writing best practices—into automated article generation, ensuring consistent quality and reader engagement across documentation.

Provide your problem-solving scenario and this Skill generates structured articles following Zenn's template and best practices. It handles frontmatter completion, enforces clear writing (one idea per sentence, active voice, term definitions), incorporates What/Why/How explanations, validates code samples, and adds follow CTAs—eliminating manual formatting and adherence checks.