Blog structure patterns for tutorials, deep-dives, research summaries, and development journals
Generates structured blog post templates for tutorials, deep-dives, research summaries, and development journals.
npx claudepluginhub arustydev/aiThis skill inherits all available tools. When active, it can use any tool Claude has access to.
Organizational patterns for different types of technical blog posts.
This skill provides structural templates for the four primary blog post types: tutorials, deep-dives, research summaries, and development journals. Each pattern is optimized for its specific purpose and reader expectations.
This skill covers:
This skill does NOT cover:
| Type | Purpose | Typical Length | Reader Goal |
|---|---|---|---|
| Tutorial | Teach a skill | 1500-3000 words | Complete a task |
| Deep-dive | Explain concepts | 2000-4000 words | Understand deeply |
| Research Summary | Synthesize findings | 1000-2000 words | Learn key insights |
| Dev Journal | Share experience | 800-1500 words | Learn from journey |
Tutorials guide readers through completing a specific task.
# Title: "How to [Action] [Thing] [Context]"
## Introduction (100-150 words)
- What you'll build/learn
- Prerequisites
- Time estimate
## [Setup/Prerequisites] (if significant)
- Required tools
- Environment setup
- Starting point
## Step 1: [First Action]
- Single focused action
- Code example
- Expected result
## Step 2: [Second Action]
- Single focused action
- Code example
- Expected result
## [Additional Steps...]
## [Troubleshooting] (optional)
- Common errors
- Solutions
## Conclusion (50-100 words)
- What was accomplished
- Next steps
- Related resources
Deep-dives explain concepts, architectures, or technologies in depth.
# Title: "[Concept]: [Subtitle with Hook]"
## Introduction (150-200 words)
- Hook: Why this matters
- What you'll learn
- Who this is for
## Background/Context
- History or motivation
- Problem being solved
- Prior approaches (optional)
## Core Concept 1
- Explanation
- Diagrams/visuals
- Examples
## Core Concept 2
- Explanation
- How it relates to Concept 1
- Examples
## [Additional Concepts...]
## Practical Application
- How to apply this knowledge
- Code examples
- Real-world scenarios
## Trade-offs and Considerations
- When to use this
- When NOT to use this
- Alternatives
## Conclusion (100-150 words)
- Key takeaways (bullet points)
- Further reading
Research summaries synthesize multiple sources into actionable insights.
# Title: "[Topic]: [Key Finding or Trend]"
## Key Takeaways (100 words)
- 3-5 bullet points
- Most important findings
- Actionable insights
## Introduction (100-150 words)
- Research question or topic
- Why it matters now
- Scope of research
## Findings
### Finding 1: [Headline]
- Evidence/data
- Source attribution
- Implications
### Finding 2: [Headline]
- Evidence/data
- Source attribution
- Implications
## Analysis
- Patterns across findings
- What this means
- Remaining questions
## Recommendations
- Actionable next steps
- Who should care
- Timeline considerations
## Methodology (brief)
- Sources reviewed
- Time period
- Limitations
## Sources
- Linked references
Dev journals share personal experiences building or learning something.
# Title: "[What I Did/Learned]: [Context or Outcome]"
## TL;DR (50 words)
- What happened
- Key lesson
## Context (100 words)
- What I was trying to do
- Why it mattered
- Starting point
## The Journey
### Challenge 1
- What went wrong
- What I tried
- What worked
### [Additional Challenges...]
## What I Learned
- Key insights (bulleted)
- What I'd do differently
- Resources that helped
## Next Steps (optional)
- What's next
- Open questions
| Element | Purpose | Length |
|---|---|---|
| Hook | Grab attention | 1-2 sentences |
| Value proposition | Why read this | 1 sentence |
| Prerequisites/scope | Set expectations | 1-2 sentences |
| Overview | What's coming | 1 sentence or list |
| Element | Purpose |
|---|---|
| Summary | Reinforce key points |
| Next steps | Guide further learning |
| CTA | Encourage action (subscribe, try, share) |
See code-example-best-practices skill for detailed guidance.
technical-writing-style skill - Voice and clarity guidelinescode-example-best-practices skill - Code snippet standardstutorial-format style - Tutorial output styledeep-dive-format style - Deep-dive output styleActivates when the user asks about AI prompts, needs prompt templates, wants to search for prompts, or mentions prompts.chat. Use for discovering, retrieving, and improving prompts.
Search, retrieve, and install Agent Skills from the prompts.chat registry using MCP tools. Use when the user asks to find skills, browse skill catalogs, install a skill for Claude, or extend Claude's capabilities with reusable AI agent components.
This skill should be used when the user wants to "create a skill", "add a skill to plugin", "write a new skill", "improve skill description", "organize skill content", or needs guidance on skill structure, progressive disclosure, or skill development best practices for Claude Code plugins.