# Writing Skills Changelog

Track of changes, learnings, and evolution of writing skills for gauravtiwari.org.

---

## 2026-02-05

### Created

| File | Purpose |
|------|---------|
| `software-review.md` | Comprehensive review skill (3500+ words) based on Rank Math review structure. Includes "My Complete Setup", code snippets, active/inactive modules pattern. |
| `_common-patterns.md` | Centralized reusable patterns: Who Should/Shouldn't, My Setup, Pricing Tables, Paragraph Length (3-6 sentences), Image Placement, Internal Linking, Specific Numbers, Quick Answer, Verdict, Comparisons |
| `_acf-blocks-for-writing.md` | Quick reference for ACF blocks in content: Accordion, Pros/Cons, CTA, Product Review, Compare, Callout, Code, Steps, Checklist, Opinion Box |

### Updated

| File | Changes |
|------|---------|
| `blog-article.md` | Added image placement, ACF blocks reference, expanded checklist |
| `product-review.md` | Added "features you disable" pattern, ACF blocks, image guidance, link to software-review.md |
| `tutorial.md` | Added "What Doesn't Work" section, ACF blocks (Checklist, Callout, Code), expanded checklist |
| `how-to-guide.md` | Added ACF blocks, internal linking requirement, expanded checklist |
| `thought-leadership.md` | Added word count targets, internal linking, image guidance |

### Key Learnings

**From Rank Math Review Analysis:**
- Showing what you DON'T use builds more trust than listing what you do
- "My Complete Setup" with actual config screenshots = instant credibility
- Code snippets for technical products separate real users from press release rewrites
- Active/Inactive module tables show deliberate choices, not just feature dumps

**Writing Philosophy Reinforced:**
- Truth > polish. Admit limitations openly.
- Opinions must have technical backing. "I hate X" needs "because Y happens"
- Experience is the differentiator. Generic AI can't fake "I've used this on 12 sites for 3 years"

---

## Patterns Discovered

### The "What I Don't Use" Pattern
Showing disabled features/rejected tools builds trust faster than listing enabled ones. Readers think: "This person actually tested everything and made choices."

### The "3-6 Sentence Paragraph" Rule
Default for all content. 1-2 sentences for punch. Never 7+. Mix creates rhythm.

### The "Specific Numbers" Rule
Every claim needs a number. "It's faster" → "Load time dropped from 3.2s to 0.9s"

---

## Content Types by Depth

| Type | Words | Use Case |
|------|-------|----------|
| `how-to-guide.md` | 1500-2500 | Quick problem→solution |
| `tutorial.md` | 2000+ | Learning a skill step-by-step |
| `blog-article.md` | 2100+ | Informational, educational |
| `product-review.md` | 2500+ | Shorter product assessments |
| `software-review.md` | 3500+ | Comprehensive with setup details |

---

## Voice Reminders

From `voice-dna.md` - check before every piece:

1. **Would a generic AI write this?** If yes, add a sharp take or real preference.
2. **Did I use "I" and "you"?** Personal pronouns = connection.
3. **Is there a number?** Vague claims are AI tells.
4. **Did I recommend ONE thing?** Not five options. Pick a side.
5. **Is there something I hate or love?** Emotion = authenticity.

---

## Future Improvements

- [ ] Add ACF block examples to remaining skills (newsletter, deal-page, etc.)
- [ ] Create skill for comparison/vs pages
- [ ] Add "My Stack" pattern for tool recommendation articles
- [ ] Consider skill for "lessons learned" / post-mortem style content

---

*This log evolves with use. Update after significant skill changes or learnings.*
