Tech Blog (Zenn)
Zenn向けの技術ブログ記事を作成するスキルです。プロジェクト紹介、チュートリアル、TIL(Today I Learned)など、様々な記事タイプに対応し、Zennのフォーマットに準拠した記事を自動生成します。
Overview
このスキルは、ユーザーの要望に応じて適切な記事タイプを判定し、コードベースの調査から構成決定、執筆、ファイル出力までを一貫してサポートします。Zennの規約に準拠したフロントマターと、読みやすい技術記事の構成を自動で生成します。
Article Types
| タイプ | 用途 | emoji 例 |
|--------|------|----------|
| project | 自作ツール/プロジェクト紹介 | 🛠️ 🚀 |
| tutorial | 技術解説/ハウツー | 📝 📚 |
| til | 今日学んだこと/ハマりポイント | 💡 🔍 |
Instructions
When the user requests to create a tech blog article, follow these steps:
1. Determine Article Type
Analyze the user's request to identify which article type is most appropriate (project, tutorial, or til)If unclear, ask the user to clarify their intentConsider the context: project introductions vs. technical explanations vs. learning notes2. Gather Information
If writing about a project, explore the codebase to understand: - Project structure and main features
- Technologies and frameworks used
- Unique implementation details or challenges
For tutorials, identify the technical topic and scopeFor TIL posts, focus on the specific learning point or problem encountered3. Reference Templates
Consult `references/templates.md` (if available in the project) for article structure templatesChoose the template that best fits the article typeAdapt the template structure to the specific content4. Generate Zenn Frontmatter
Create proper Zenn frontmatter with:
```yaml
---
title: "記事タイトル"
emoji: "🎯"
type: "tech" # Use "tech" for technical articles or "idea" for opinion pieces
topics: ["topic1", "topic2"] # Maximum 5 topics, use relevant technology names
published: false # Default to false for review
---
```
5. Write the Article
Follow these writing guidelines:
**Structure:**
Start with h2 (##) headings, never use h1 (#)Use conclusion-first approach: background → problem → solution → summaryTarget length: 1500-3000 characters (approximately 5-10 minutes reading time)**Code Blocks:**
Always specify language for syntax highlightingUse diff notation to show changes clearly: ```diff
- old code
+ new code
```
**Tone:**
Technical yet approachableWrite assertively and confidentlyBalance professional expertise with friendly readability**Content Focus:**
Lead with the conclusion or key takeawayProvide clear context and backgroundExplain the problem before diving into solutionsInclude concrete examples and code snippetsEnd with actionable summary or next steps6. Output the File
Save the article to `articles/<slug>.md` where `<slug>` is a URL-friendly identifierUse kebab-case for the slug (e.g., `my-awesome-project.md`)Confirm successful file creation with the userTriggers
This skill activates when users say:
"ブログを書いて" (Write a blog)"記事を作成" (Create an article)"Zenn記事" (Zenn article)"技術記事" (Technical article)"/tech-blog"Example Usage
**User:** "新しく作ったCLIツールについてZenn記事を書いて"
**Agent Response:**
1. Determines article type: **project**
2. Explores codebase to understand the CLI tool's features
3. Generates appropriate frontmatter with tool-related emoji and topics
4. Writes article following project introduction template
5. Saves to `articles/my-cli-tool-introduction.md`
Notes
Articles default to `published: false` for user review before publishingIf `references/templates.md` exists in the project, reference it for consistent structureFor Japanese content, maintain natural Japanese writing styleAlways validate Zenn frontmatter format before output