Skip to content
how-to-guide logo

How-To Guide Creator

how-to-guide

Create comprehensive how-to guides and tutorials. Use when the user needs step-by-step instructional content, tutorials, documentation, or educational guides.

SKILL.md

Full skill instructions

How-To Guide Creator

Create clear, actionable how-to guides that help readers achieve specific outcomes through step-by-step instructions.

Before Writing

  1. Read context profiles:

    • /​context/​voice-dna.json - Maintain authentic voice
    • /​context/​icp.json - Match reader's skill level
    • /​context/​business-profile.json - Align with expertise areas
  2. Determine guide scope and reader prerequisites

Guide Types

Type 1: Quick Tutorial (500-1,000 words)

For simple, focused tasks

- Title: How to [Do Specific Thing]
- Intro: 2-3 sentences
- Prerequisites: Bulleted list
- Steps: 3-7 steps
- Conclusion: 1-2 sentences

Type 2: Comprehensive Guide (1,500-3,000 words)

For complex processes

- Title
- Introduction (why this matters)
- Prerequisites
- Overview of what we'll cover
- Main content (sectioned steps)
- Troubleshooting common issues
- Next steps
- Resources

Type 3: Ultimate Guide (3,000+ words)

For deep-dive educational content

- Title
- Table of contents
- Introduction
- Background/​Context
- Prerequisites
- Detailed sections with substeps
- Examples and case studies
- Common mistakes
- FAQ
- Resources and tools
- Conclusion and next steps

Guide Structure Template

# How to [Achieve Specific Outcome]

[One-paragraph introduction: what they'll learn and why it matters]

## Prerequisites

Before you start, make sure you have:
- [Requirement 1]
- [Requirement 2]
- [Requirement 3]

## Overview

In this guide, you'll learn:
1. [What they'll accomplish in section 1]
2. [What they'll accomplish in section 2]
3. [What they'll accomplish in section 3]

**Time required**: [Estimate]
**Difficulty**: [Beginner/​Intermediate/​Advanced]

---

## Step 1: [Action-Oriented Title]

[Brief context for why this step matters]

### What to do:

1. [Specific action]
2. [Specific action]
3. [Specific action]

### Example:

[Concrete example of this step]

### Common mistakes:

- [Mistake to avoid]
- [Mistake to avoid]

---

## Step 2: [Action-Oriented Title]

[Continue pattern...]

---

## Troubleshooting

### Issue: [Common Problem]
**Solution**: [How to fix]

### Issue: [Common Problem]
**Solution**: [How to fix]

---

## Next Steps

Now that you've [accomplished goal], you can:
- [Next logical step 1]
- [Next logical step 2]
- [Advanced option]

---

## Resources

- [Useful tool or link]
- [Useful tool or link]
- [Related guide]

Writing Guidelines

Titles

  • Start with "How to"
  • Include the specific outcome
  • Be specific, not vague
  • Examples:
    • ✓ "How to Set Up a Claude Code Writing System in 30 Minutes"
    • ✗ "How to Use AI for Writing"

Prerequisites

  • Be explicit about what's needed
  • Include skill level
  • List tools/​accounts required
  • Link to prerequisite guides if needed

Steps

  • One action per step
  • Start with action verb
  • Include the "why" briefly
  • Show don't just tell
  • Include examples/​screenshots where helpful

Examples

  • Use real, specific examples
  • Show before/​after when possible
  • Include edge cases
  • Make them relatable to ICP

Formatting

  • Plenty of white space
  • Headers for scanability
  • Numbered steps for sequences
  • Bullets for unordered items
  • Bold key terms
  • Code blocks for technical content

Output Format

TITLE: How to [Specific Outcome]
TYPE: [Quick/​Comprehensive/​Ultimate]
TARGET LENGTH: [Word count]
SKILL LEVEL: [Beginner/​Intermediate/​Advanced]
TIME TO COMPLETE: [Estimate]

---

[FULL GUIDE CONTENT]

---

SUMMARY:
- Steps covered: [Number]
- Key outcome: [What they can now do]
- Next recommended guide: [If applicable]

Quality Checklist

Before delivering:

  • Clear, specific title
  • Prerequisites listed
  • Logical step progression
  • Each step is actionable
  • Examples included
  • Common mistakes addressed
  • Troubleshooting section
  • Next steps provided
  • Matches voice DNA
  • Appropriate for ICP skill level

Common Mistakes to Avoid

  • Assuming knowledge not in prerequisites
  • Steps that are too big (break them down)
  • Missing the "why" behind steps
  • No examples or visuals
  • Jargon without explanation
  • Skipping edge cases
  • No troubleshooting help
  • Weak conclusion

More Other skills

Delegate independent tasks to specialized agents working concurrently with isolated context.

295.4K 206.3K
View

Applies Anthropic's official brand colors and typography to any sort of artifact that may benefit from having Anthropic's look-and-feel. Use it when brand colors or style guidelines, visual formatting, or company design standards apply.

179.7K 100.1K
View

Toolkit for styling artifacts with a theme. These artifacts can be slides, docs, reportings, HTML landing pages, etc. There are 10 pre-set themes with colors/fonts that you can apply to any artifact that has been creating, or can generate a new theme on-the-fly.

179.7K 89.5K
View

A set of resources to help me write all kinds of internal communications, using the formats that my company likes to use. Claude should use this skill whenever asked to write some sort of internal communications (status reports, leadership updates, 3P updates, company newsletters, FAQs, incident reports, project updates, etc.).

179.7K 76.1K
View

Fundamental design principles for writing maintainable, testable Python code.

40.2K 21.9K
View

Modern responsive layouts using container queries, fluid typography, CSS Grid, and mobile-first strategies.

40.2K 20K
View

Generate Playwright tests from scenarios using interactive browser exploration and validation.

39.7K 18.2K
View

Modern React state management with Redux Toolkit, Zustand, Jotai, and React Query for every state category.

40.2K 14.7K
View

GDPR-compliant data handling with consent management, data subject rights, and privacy controls.

40.2K 14.3K
View

Python error handling patterns including input validation, exception hierarchies, and partial failure handling. Use when implementing validation logic, designing exception strategies, handling batch processing failures, or building robust APIs.

40.2K 13.5K
View

Detailed multi-file refactor planning with safety checks and rollback guidance.

39.7K 13K
View