Skip to content

AgriciDaniel/claude-blog / skills/blog

Full-lifecycle blog engine with 31 sub-skills, 12 templates, 100-point scoring, and 5 agents. Routes requests to the right sub-skill: writing, rewriting, analysis, outlines, audits, schema, charts, images, repurposing, AI citation SEO, FLOW prompts, topic clusters, and multilingual publishing. Optimized for Google rankings, E-E-A-T, and AI citations. Supports any platform. Use when the user asks to create, revise, analyze, plan, translate, localize, audit, or repurpose blog content, or invokes a /blog subcommand. Do not activate merely because the word "blog" appears in an unrelated coding, theme-debugging, database, log-analysis, or definition request.

templates/comparison.md

View on GitHub
# Template: Comparison (X vs Y)

**Template Name:** Comparison (X vs Y Analysis)
**Target Word Count:** 1,500-2,000 words
**Description:** A structured, fair, category-by-category comparison of two (or occasionally three) competing products, tools, strategies, or approaches. Each category section is framed as a question the reader is actually asking, with a clear winner declared per category and an overall verdict. Designed to rank for "[A] vs [B]" queries, capture decision-stage traffic, and earn featured snippets for direct comparison questions.

## When to Use This Template

- **Content Goals:** Capture high-intent "[A] vs [B]" search traffic, help readers make confident purchase/adoption decisions, build authority as a fair evaluator, rank in "People Also Ask" boxes
- **Search Intent:** Commercial investigation: the reader has narrowed their options to 2-3 choices and needs help making the final decision
- **Best For:** Software comparisons, tool evaluations, framework decisions, platform migrations, methodology debates, service provider comparisons
- **Avoid When:** The two options aren't genuinely comparable (different categories), one option is clearly obsolete, or you need to evaluate more than 3 options (use the Listicle template instead)

---

## Section-by-Section Structure

---

### Title (H1)

**Format:** "[Product A] vs [Product B]: [Key Differentiator] Compared ([Year])"

**Examples:**
- "Next.js vs Astro: Performance and DX Compared (2026)"
- "PostgreSQL vs MySQL: Which Database Fits Your Stack? (2026)"
- "Tailwind CSS vs Styled Components: Styling Approaches Compared (2026)"

**Rules:**
- Put the more popular/searched product first (higher search volume = first position)
- Include a differentiating phrase that signals what the comparison covers
- Include the year for freshness signals
- Keep under 65 characters if possible
- Never use "Which is Better?": be more specific about the dimension of comparison

---

### TL;DR Box (concise; length follows the material)

[ANSWER-FIRST] Deliver the verdict immediately. The reader should be able to stop here and have a useful answer.

**Format:** A visually distinct callout box placed immediately after the title.

**Structure:**
1. **Quick verdict** (1 sentence): Name the overall winner and the single strongest reason.
2. **Exception** (1 sentence): Name the specific use case where the other option wins.
3. **Decision rule** (1 sentence): "Choose [A] if [X]. Choose [B] if [Y]."

**Example:**
> **TL;DR:** Astro wins for content-heavy sites: it's faster out of the box and ships zero JS by default. Next.js wins for interactive web applications where you need server-side rendering, API routes, and a mature ecosystem. Choose Astro if your site is mostly content. Choose Next.js if your site is mostly application.

---

### Introduction (100-150 words)

[ANSWER-FIRST] Open with the specific market context that makes this comparison relevant *right now*. What changed recently that makes people search for this?

**Structure:**
1. **Timeliness hook** (1-2 sentences): What happened recently (release, trend, shift) that makes this comparison urgent?
2. **The core tension** (1-2 sentences): What is the fundamental trade-off between these two options? Frame it as a genuine dilemma, not a strawman.
3. **Scope statement** (1 sentence): What specific dimensions will this comparison cover?
4. **Credibility anchor** (1 sentence): What qualifies you to make this comparison? (testing methodology, experience with both, etc.)

[STAT: Market context statistic: adoption rates, npm downloads, GitHub stars, survey data that frames both options]

[INFO-GAIN: hands-on experience] Include only when the author supplies what was
built, the test period, scale, methodology, evidence, and results. Otherwise
state that the comparison is research-only.

[INTERNAL-LINK] Link to individual deep-dive posts on each product: "For standalone reviews, see our [Product A Guide] and [Product B Guide]."

---

### Quick Comparison Table (H2)

[VISUAL: comparison-table]

**Format:** A comprehensive feature matrix as a markdown table, placed early in the post for scanners.

**Required rows (adapt to your category):**

| Category | [Product A] | [Product B] |
|----------|-------------|-------------|
| **Best For** | [Primary use case] | [Primary use case] |
| **Pricing** | [Specific tiers] | [Specific tiers] |
| **Learning Curve** | [Specific assessment] | [Specific assessment] |
| **[Key Metric 1]** | [Specific value] | [Specific value] |
| **[Key Metric 2]** | [Specific value] | [Specific value] |
| **[Key Metric 3]** | [Specific value] | [Specific value] |
| **[Key Metric 4]** | [Specific value] | [Specific value] |
| **Community / Ecosystem** | [Specific data point] | [Specific data point] |
| **Our Verdict** | [Win/Lose/Tie per row] | [Win/Lose/Tie per row] |

**Rules:**
- Use specific, measurable values: never "Good" or "Fast"
- Bold the winner in each row
- Include a "Best For" row at the top and "Our Verdict" row at the bottom
- Keep to 8-12 rows: enough to be comprehensive, not so many that it's overwhelming

[STAT: Include a benchmark only when its source or supplied test methodology,
evidence, and results are available]

[INFO-GAIN: original benchmark] If you ran your own performance tests, note the methodology in a footnote below the table.

**Benchmark data sourcing.** Every material statistic must be traceable to a
source or supplied test record that supports it. Record dates, methodology,
limitations, and retrieval details when they affect interpretation. Do not
force one citation format.

---

### Category 1: Which Has Better [Core Feature]? (150-200 words)

[ANSWER-FIRST] Open by naming the winner of this category and the single strongest reason in the first sentence.

**H2 format:** Use a clear question or declarative category heading according to
reader intent, such as `## Performance comparison`.

**Structure for EVERY category section:**
1. **Winner declaration** (1 sentence): "[Product A/B] wins on [category] because [specific reason]."
2. **Product A evaluation** (2-3 sentences): How Product A performs in this category with specific details, metrics, or examples.
3. **Product B evaluation** (2-3 sentences): How Product B performs in this category with specific details, metrics, or examples.
4. **Nuance** (1-2 sentences): When does the losing product actually come close or even win in a sub-scenario?
5. **Verdict** (bold, 1 sentence): Restate the winner with a qualifier.

[STAT: Specific metric comparing both products in this category]

[IMAGE] Side-by-side screenshot, benchmark result, or visual comparison showing the difference in this category.

**Example:**
> ## Which Has Better Build Performance?
>
> **[PRODUCT] leads in [DEFINED TEST CONDITION]**, based on [SUPPLIED TEST
> RECORD OR VERIFIED SOURCE].
>
> Describe the environment, versions, sample, repetitions, measurement method,
> and result. If no hands-on record exists, attribute each benchmark to its
> original source and label the comparison research-only.
>
> **Verdict: [CONDITIONAL DECISION BASED ON THE VERIFIED EVIDENCE].**

---

### Category 2: Which Has Better [Second Feature]? (150-200 words)

[Follow the same structure as Category 1]

[STAT: Comparative metric for this category]

[INFO-GAIN: real-world observation] Include only a supplied, documented usage
observation. Otherwise use a sourced comparison or omit it.

---

### Category 3: Which Has Better [Third Feature]? (150-200 words)

[Follow the same structure as Category 1]

[STAT: Comparative metric for this category]

[IMAGE] Visual comparison for this category.

---

### Category 4: Which Has Better [Fourth Feature]? (150-200 words)

[Follow the same structure as Category 1]

[STAT: Comparative metric for this category]

[INFO-GAIN: ecosystem or community insight] Use documented first-hand evidence
when supplied; otherwise attribute the observation to current public sources.

---

### Category 5: Which Has Better [Fifth Feature]? (150-200 words)

[Follow the same structure as Category 1]

[STAT: Comparative metric for this category]

---

### Categories 6-7: [Additional categories as needed] (150-200 words each)

[Follow the same structure. Use 5-7 categories total. Common categories include:]
- Performance / Speed
- Developer Experience / Learning Curve
- Ecosystem / Plugins / Integrations
- Documentation / Community Support
- Scalability
- Security
- Customization / Flexibility
- Pricing / Value

**Note:** Choose categories based on what your audience actually cares about, not what's easiest to compare. Survey your readers or check "People Also Ask" boxes for guidance.

---

### Pricing Comparison (150-200 words)

[ANSWER-FIRST] Open with the bottom line: "For [typical use case], [Product A] costs [X] and [Product B] costs [Y]."

**Structure:**
1. **Direct cost comparison** (2-3 sentences): Side-by-side pricing for the most common tier or usage pattern.
2. **Free tier analysis** (1-2 sentences): What's actually usable in each free tier? What are the real limits?
3. **Scaling costs** (2-3 sentences): How does pricing change as usage grows? Where are the inflection points?
4. **Hidden costs** (1-2 sentences): Any costs not immediately obvious: migration effort, required add-ons, lock-in implications.
5. **Value verdict** (bold, 1 sentence): Which provides better value and for whom.

[VISUAL: pricing-comparison-table] A simple table showing pricing tiers side by side.

| Tier | [Product A] | [Product B] |
|------|-------------|-------------|
| Free | [Details] | [Details] |
| Starter / Pro | [Price + details] | [Price + details] |
| Enterprise | [Price + details] | [Price + details] |

[STAT: Total cost of ownership for a specific scenario (e.g., "For a 10-person team with 100K monthly users")]

[INFO-GAIN: hidden cost insight] Use a supplied billing record or verified
source. Do not imply discovery through actual usage without evidence.

---

### Who Should Choose What (100-150 words)

[ANSWER-FIRST] Open with the simplest possible decision rule: "If [condition], choose [Product]. If [condition], choose [Product]."

**Format:** 2-4 reader profiles, each as a bolded persona with a 1-2 sentence recommendation.

**Structure:**
1. **Persona 1** (bold): "[Profile description]" -> Recommendation + reason
2. **Persona 2** (bold): "[Profile description]" -> Recommendation + reason
3. **Persona 3** (bold): "[Profile description]" -> Recommendation + reason
4. **Edge case** (1 sentence): When neither option is right and what to consider instead.

[INTERNAL-LINK] Link to a detailed guide for each recommended product: "Getting started with [Product A]? Read our [Setup Guide]."

**Example:**
> **Solo developers building content sites:** Choose Astro. You'll ship faster, spend less time configuring, and get better performance out of the box.
>
> **Teams building SaaS applications:** Choose Next.js. The API routes, authentication patterns, and middleware ecosystem will save you months.
>
> **Agencies managing multiple client sites:** Choose Astro for marketing/content sites, Next.js for web applications. Most agencies end up using both.
>
> If neither fits: you need a full-stack framework with batteries included: look at Remix or SvelteKit.

---

### Optional Reader Questions (count by reader need)

[FAQ]

**Format:** Each question as an H3, answer in 2-4 sentences.

**Question selection criteria:**
1. "Is [Product A] better than [Product B]?" (Restate verdict with nuance)
2. "Can I migrate from [A] to [B]?" (Address switching costs and feasibility)
3. "Can I use [A] and [B] together?" (Address hybrid approaches if applicable)
4. "[Specific feature] question" (Address the most searched feature-specific question)
5. "Is [Product] still worth using in [Year]?" (Address relevance and future trajectory)

[STAT when useful: a verified metric that materially improves an FAQ answer]

**Example:**

#### Is Next.js better than Astro?

[2-4 sentence answer reframing as "it depends on your use case" with specific criteria.]

#### Can I migrate from Next.js to Astro?

[2-4 sentence answer with migration feasibility, estimated effort, and key considerations.]

#### Can I use Next.js and Astro together?

[2-4 sentence answer addressing monorepo setups or hybrid architectures if applicable.]

#### Which has better SEO?

[2-4 sentence answer with specific SEO-relevant differences and metrics.]

#### Is [Product] still relevant in 2026?

[2-4 sentence answer addressing trajectory, recent releases, and community momentum.]

---

### Verdict with Category Winners (50-100 words)

**Format:** A summary table followed by an overall recommendation.

| Category | Winner |
|----------|--------|
| [Category 1] | [Product] |
| [Category 2] | [Product] |
| [Category 3] | [Product] |
| [Category 4] | [Product] |
| [Category 5] | [Product] |
| **Pricing** | [Product] |
| **Overall** | **[Product] (for [specific use case])** |

**Overall verdict** (2-3 sentences): Restate the decision rule from the TL;DR with any additional nuance earned through the detailed analysis.

**CTA** (1 sentence): "Disagree? Share your experience in the comments" or "Subscribe for more head-to-head comparisons."

[INTERNAL-LINK] Link to 2-3 related posts: getting-started guides for the winner, alternative comparisons, or the listicle that includes both products.

---

## Template Checklist

Before publishing, verify:

- [ ] Title includes both product names, a differentiator, and the current year
- [ ] TL;DR box delivers a clear verdict in under 60 words
- [ ] Introduction establishes timeliness: why this comparison matters *now*
- [ ] Quick comparison table uses specific metrics, not vague ratings
- [ ] Every category section opens by naming the winner (answer-first)
- [ ] Every category section evaluates both products with comparable depth and fairness
- [ ] Every category section includes a nuance statement (when the loser might win)
- [ ] 5-7 categories cover the dimensions that matter most to the target audience
- [ ] Pricing comparison includes free tiers, scaling costs, and hidden costs
- [ ] "Who Should Choose What" provides clear persona-based recommendations
- [ ] Any [INFO-GAIN] elements contain supported testing data or observations
- [ ] Statistics are optional, material to the decision, and verified when used
- [ ] At least 2 [IMAGE] markers with side-by-side visual comparisons
- [ ] FAQ addresses migration, hybrid use, and product relevance
- [ ] Verdict table summarizes category winners clearly
- [ ] All [INTERNAL-LINK] zones have contextual links to related content
- [ ] Coverage is complete for the comparison intent without padding
- [ ] Both products are treated fairly: no strawman arguments
- [ ] Meta description accurately summarizes the visible comparison
rea-analysis-optimizationmorluto/reaOptimize REA providers and shared analysis workflows for agent context, latency, CPU, and memory while preserving correctness and Evidence. Use for analysis bottlenecks and cache or query design; CI/test-suite optimization belongs to rea-ci-tests-audit.Stars: 472kUpdated Claude CodeCodexVerifiedInstall
rea-ci-tests-auditmorluto/reaAudit REA CI and test suites for correctness, fixture drift, false passes, and measured performance; use for suite or workflow investigations and efficiency changes, rather than ordinary feature testing or a single test failure.Stars: 472kUpdated Claude CodeCodexVerifiedInstall
rea-tool-designmorluto/reaAudit, investigate, design, or change REA investigation tools, CLI/MCP contracts, provider capabilities, and Evidence semantics.Stars: 472kUpdated Claude CodeCodexVerifiedInstall
ponytail-auditDietrichGebert/ponytailQuality audit of the whole repo: bugs, security, real load, missing tests, speed, and what to delete. Most important first.Stars: 194kUpdated Claude CodeCodexVerifiedInstall