---
name: how-to-guide
description: Write problem-to-solution how-to guides with clear steps and practical advice.
---

# Skill: How-To Guide

Comprehensive how-to guides that take readers from problem to solution.

## Specifications

| Attribute | Value |
|-----------|-------|
| Default length | 1500-2500 words |
| Structure | Problem → Solution → Steps → Result |
| Tone | Helpful expert friend |
| FAQs | Required (5-8) |

## How-To vs Tutorial

**How-To Guide:** Focuses on achieving a goal. "How to speed up WordPress"
**Tutorial:** Focuses on learning a skill. "Setting up Redis caching step-by-step"

How-to guides are outcome-focused. Tutorials are process-focused.

## Article Structure

```markdown
[Opening - Problem identification + promise]

## Why This Matters / The Problem

[Context for why readers need this]

## The Quick Answer

[TL;DR solution for scanners]

## Method 1: [Best/Easiest Approach]

[Steps with expected outcomes]

## Method 2: [Alternative Approach]

[When to use this instead]

## Common Mistakes to Avoid

[What not to do]

## Troubleshooting

[If things go wrong]

## Frequently Asked Questions

[ACF Accordion block]
```

## Opening Template

Start with the problem, end with the promise:

**Good:**
> Your WordPress site takes 6 seconds to load. Visitors leave after 3. Here's how to fix it in under an hour, even if you're not technical.

**Bad:**
> In this comprehensive guide, we'll explore various methods for optimizing your WordPress website's loading speed.

### Opening Formula

```
[State the problem] + [Stakes] + [Promise] + [Qualifier if needed]
```

Examples:
> Google's indexing your site wrong. Your best content isn't showing up. Here's how to fix it in 15 minutes using Search Console.

> Your email list isn't growing. You're getting traffic but no subscribers. I'll show you 3 changes that doubled my conversion rate.

## Quick Answer Section

For readers who just want the answer:

```markdown
## The Quick Answer

**If you're in a hurry:** Install FlyingPress ($60/year), enable page caching, and turn on image optimization. That alone will cut your load time in half.

**For the full breakdown:** Keep reading.
```

This respects reader time while encouraging deeper engagement.

## Method Structure

Each method needs:

1. **When to use this method**
2. **What you'll need**
3. **Step-by-step process**
4. **Expected outcome**
5. **Time estimate**

```markdown
## Method 1: Using a Caching Plugin (Easiest)

**Best for:** Most WordPress sites, especially blogs and small business sites.
**Time needed:** 15-20 minutes
**Cost:** Free to $60/year

### Step 1: Choose Your Plugin

I recommend FlyingPress for most sites. WP Rocket if you want something simpler.

### Step 2: Install and Activate

Go to Plugins → Add New → Search "[Plugin]" → Install → Activate

### Step 3: Configure Basic Settings

[Specific settings with screenshots recommended]

### What to Expect

After enabling, run a speed test. You should see:
- Load time drop by 30-50%
- TTFB under 500ms
- PageSpeed score increase by 15-30 points
```

## Alternative Methods

Always provide at least one alternative:

```markdown
## Method 2: Server-Level Optimization (More Control)

**Best for:** Developers, VPS users, high-traffic sites
**Time needed:** 1-2 hours
**Cost:** Depends on hosting

Use this if Method 1 didn't give enough improvement or you need fine-grained control.

[Steps...]
```

## Common Mistakes Section

Prevent reader frustration:

```markdown
## Common Mistakes to Avoid

### Mistake 1: Installing Multiple Caching Plugins

I see this constantly. People install WP Rocket AND W3 Total Cache AND LiteSpeed Cache. They conflict. Pick one.

### Mistake 2: Not Clearing Cache After Changes

Changed something and don't see it? Clear your cache. Then clear your CDN cache. Then clear your browser cache.

### Mistake 3: Ignoring Image Optimization

Caching helps. But if your images are 2MB each, you're fighting uphill.
```

## Troubleshooting Section

Anticipate problems:

```markdown
## If It's Not Working

### "My site is still slow"

Check these in order:
1. Is caching actually enabled? (Test with `/?nocache=1`)
2. Is your hosting the bottleneck? (Check TTFB)
3. Are images optimized? (Check total page weight)

### "My site looks broken after enabling"

JavaScript issue. Go to [Plugin] → Settings → Exclude from caching. Add problematic scripts one by one until you find the culprit.

### "Changes aren't showing up"

Clear in this order: Plugin cache → CDN cache → Browser cache
```

## Visual Guidance

When to suggest images:

```markdown
[IMAGE: Before/after PageSpeed scores showing improvement]
Alt: PageSpeed score improving from 45 to 92 after optimization

[IMAGE: Screenshot of FlyingPress settings panel with recommended options highlighted]
Alt: FlyingPress settings configuration
```

## Comparison Tables

When multiple options exist:

```markdown
| Method | Difficulty | Time | Cost | Best For |
|--------|------------|------|------|----------|
| Caching Plugin | Easy | 15 min | $0-60/yr | Most sites |
| Server Config | Medium | 1-2 hrs | $0 | VPS users |
| CDN Setup | Easy | 30 min | $0-5/mo | Global traffic |
```

## Results/Proof Section

Show what success looks like:

```markdown
## What Good Looks Like

After following this guide, you should see:

- **Load time:** Under 2 seconds (ideally under 1)
- **PageSpeed Mobile:** 80+ (90+ is excellent)
- **Core Web Vitals:** All green
- **TTFB:** Under 400ms

Here's what my site looks like after these optimizations:

[IMAGE: PageSpeed results]
```

## Voice Reminders

### Do:
- Use "you" constantly
- Include specific numbers
- Acknowledge when something is annoying
- Offer alternatives
- Be honest about difficulty

### Don't:
- Assume reader knows jargon
- Skip the "why"
- Provide only one way
- Ignore edge cases
- Oversimplify (but don't overcomplicate either)

## FAQ Section

Include these types:
1. "What if [common edge case]?"
2. "Is [alternative] better?"
3. "Do I need [related thing]?"
4. "How long does this last?"
5. "What's the cost?"

## Closing Template

End with clear next action:

```markdown
## Next Steps

You've fixed your site speed. Here's what to tackle next:

1. **Monitor it:** Set up free uptime monitoring with UptimeRobot
2. **Test monthly:** Run PageSpeed tests after major changes
3. **Optimize images:** Check out my [image optimization guide](link)

Questions? Drop them in the comments. I read every one.
```

## ACF Blocks for How-To Guides

See `_acf-blocks-for-writing.md` for full syntax.

| Situation | Block |
|-----------|-------|
| Quick answer/TL;DR | Callout block (info type) |
| Method comparison | Compare block |
| Warning about common mistake | Callout block (warning type) |
| Steps in a method | Steps block |
| FAQ section | Accordion block |

### Quick Answer Callout

```html
<!-- wp:acf/callout {"name":"acf/callout","data":{"callout_type":"info","callout_title":"Quick Answer","callout_content":"<p>Install FlyingPress, enable page caching, done. For details, keep reading.</p>"}} /-->
```

---

## Related Patterns

See `_common-patterns.md` for:
- Quick Answer / TL;DR pattern
- Image placement guidance
- Internal linking requirements (3-5 links)
- Specific numbers pattern
- Comparison section pattern

---

## Output Checklist

- [ ] Problem clearly stated in opening
- [ ] Quick answer for scanners (consider Callout block)
- [ ] Multiple methods provided
- [ ] Each step has expected outcome
- [ ] Image placeholders for visual steps
- [ ] Common mistakes section
- [ ] Troubleshooting section
- [ ] Results/success criteria defined
- [ ] 3-5 internal links
- [ ] FAQs (5-8) in ACF Accordion
- [ ] Clear next steps
- [ ] 1500-2500 words
- [ ] No banned phrases
