Kostja Zhang

---
name: media-kit-page-generator
description: When the user wants to create, optimize, or audit media kit or press page. Also use when the user mentions "media kit," "press kit," "press page," "press resources," "brand assets," "logo download," "press assets," "media resources," or "brand kit." For PR outreach, use public-relations.
metadata:
  version: 1.0.1
---

# Pages: Media Kit

Guides media kit and press page content, structure, and accessibility for journalists. Media kits provide self-service brand assets; consistent presentation builds trust (companies with strong guidelines are 20% more valuable). **Distinct from press-coverage-page-generator**: Media kit = assets for journalists; press coverage = aggregation of third-party mentions for visitor trust.

**When invoking**: On **first use**, if helpful, open with 1-2 sentences on what this skill covers and why it matters, then provide the main output. On **subsequent use** or when the user asks to skip, go directly to the main output.

## Initial Assessment

**Check for project context first:** If `.claude/project-context.md` or `.cursor/project-context.md` exists, read it for company story, metrics, key messages, and Section 12 (Visual Identity).

Identify:
1. **Audience**: Journalists, bloggers, analysts
2. **Update frequency**: Before launches, events, announcements
3. **Assets**: Logos, brand guidelines, favicon, photos, videos

## Best Practices

### Essential Elements

**Evergreen content:**
- Company overview (background, mission, origin)
- Key team bios and headshots
- High-res logos (multiple sizes, light/dark backgrounds, transparent PNG)
- Brand guidelines document (typography, colors, logo usage)
- Key statistics (customers, growth, metrics)

**Regularly updated:**
- Recent press releases
- Product photos and video clips
- Link to press coverage page (or "As Seen In" section) for media mentions
- Contact for press inquiries

**Note**: Press coverage (third-party mentions) is often a separate page or section. See **press-coverage-page-generator** for aggregating "As Seen In" / "In the News" content.

### Logo Assets (per Alignify-style media kit)

| Asset | Format | Use |
|-------|--------|-----|
| **Main logo** | PNG, SVG; light and dark bg | Primary branding |
| **Icon** | PNG; light and dark bg | Favicon, social, compact use |
| **Brand pattern** | PNG | Visual identity element |
| **Brand guidelines** | PDF or PNG | Typography, colors, usage rules |

### Usage Guidelines

**Allowed**: Media coverage, blog posts, social sharing, product comparisons, educational use. Assets free to download without additional authorization.

**Requirements**: Maintain logo proportions and colors; ensure adequate white space; do not use in contexts that harm brand. For commercial or special use, contact for authorization.

### Media Assets

| Asset | Format |
|-------|--------|
| **Logos** | PNG (transparent), SVG; horizontal and square |
| **Photos** | High-res; horizontal for web, square for social |
| **Videos** | Product demos, interviews |
| **Credits** | Photo credits, usage rights |

### Structure

- **Dedicated page**: Press/Media section on website
- **Self-service**: Journalists find what they need without emailing
- **Concise**: 3-4 pages typical; each element adds value
- **Downloadable**: ZIP or individual asset downloads

### Timing

- **Update before**: Launches, events, announcements
- **Keep current**: Stale info damages credibility

### Placement

- **Discoverable**: Link in footer, About, or dedicated Press section
- **Clear label**: "Press," "Media Kit," "For Journalists"

## Output Format

- **Structure** outline
- **Asset** checklist (logos, brand guidelines, favicon, photos, bios)
- **Copy** for company overview
- **Usage guidelines** (allowed, requirements)
- **Contact** for press inquiries
- **SEO**: Often noindex; or index for "company name press" queries

## Related Skills

- **press-coverage-page-generator**: Aggregation of third-party coverage ("As Seen In"); media kit can link to it; distinct (media kit = assets for journalists; press coverage = social proof for visitors)
- **about-page-generator**: Media kit extends About for press
- **contact-page-generator**: Press contact info
- **customer-stories-page-generator**: Press may reference case studies
- **logo-generator**: Logo assets, placement rules; media kit hosts logo files
- **favicon-generator**: Favicon for browser/app; media kit can link or include
- **brand-visual-generator**: Typography, colors, spacing; brand guidelines document
- **indexing**: noindex vs. index for press page
- **directory-submission**: Media kit required for Product Hunt and directory submissions

---
name: landing-page-generator
description: When the user wants to create, optimize, or audit campaign landing pages for paid ads, email, or other traffic. Also use when the user mentions "landing page," "PPC landing page," "SEM landing page," "conversion page," "campaign page," "lead capture page," "landing page optimization," "LP conversion," "single-page funnel," or "squeeze page." Not for the main site homepage; use homepage-generator.
metadata:
  version: 1.4.0
---

# Pages: Landing Page

Guides campaign landing page structure, conversion flow, and optimization. **Primary use**: **Paid ads (PPC/SEM)** — landing pages are typically built to receive paid traffic; ad-to-page alignment is critical for conversion. See **paid-ads-strategy** for when to use paid ads and ad-to-page alignment principles. Also applies to affiliate signup, product launch, lead capture, webinar registration, and other single-goal conversion pages. **Scale**: When building many landing pages (city-specific, product-specific, integration-specific), use **programmatic-seo** (template + data) and **template-page-generator** for template design. Differs from homepage (multi-purpose) and product pages (catalog).

**When invoking**: On **first use**, if helpful, open with 1–2 sentences on what this skill covers and why it matters, then provide the main output. On **subsequent use** or when the user asks to skip, go directly to the main output.

## Paid Ads: LP Requirements

When LP receives paid traffic: ad promise on page immediately; mobile-first (CTA above fold, fast load); minimal form (fewer fields); trust above fold. See **paid-ads-strategy** for full ad-to-page alignment and Quality Score.

## Initial Assessment

**Check for project context first:** If `.claude/project-context.md` or `.cursor/project-context.md` exists, read it for product, audience, and value proposition.

Identify:
1. **Page goal**: Signup, purchase, lead capture, webinar, download
2. **Traffic source**: Paid ads, email, affiliate, organic
3. **Audience**: Cold vs warm; segment if known

## Landing Page Structure (5-Step Flow)

| Step | Purpose | Elements |
|------|---------|----------|
| **1. Stop the scroll** | Capture attention in ~2.6 seconds | Headline, subheadline, hero image or video |
| **2. Earn trust** | Social proof before the ask | Logos, testimonials, ratings, customer count |
| **3. Explain value** | Benefits, features, use cases | Clear copy; who it's for, what it does |
| **4. Remove doubt** | Objection handling | FAQ, guarantees, comparison |
| **5. Make the ask** | Single primary CTA | One clear action; repeat at logical points |

Every element should serve one of these five functions. Pages with multiple competing offers get ~266% fewer leads.

## Headline Formula

**[Who it's for]** + **[Specific outcome]** + **[Time/qualifier]**

- **Avoid**: Abstract promises ("Unlock your potential," "Transform your business")
- **Prefer**: Concrete ("Cut invoice processing by 70%—without new software")

## CTA Best Practices

- **One primary CTA**: No competing actions; create a "one-way street" toward conversion
- **Above the fold on mobile**: Thumb-reachable; ~65%+ traffic is mobile
- **Value-focused copy**: "Start Free Trial" not "Submit"
- **Pair with trust signals**: Customer count, logos, or stats next to the button
- **Remove or minimize navigation**: Can increase conversion 2–28%

## Programmatic Landing Pages (Scale)

When you need **many landing pages** (e.g., city-specific, product-specific, integration-specific), use **programmatic-seo**: one template + data = hundreds or thousands of LPs. Apply landing page structure (5-step flow, CTA, trust) to the template; see **template-page-generator** for template design. Example: "[Product] for [City]" LPs with local data; "[App A] + [App B]" integration signup pages.

## Page Types

| Type | Use | CTA Destination |
|------|-----|-----------------|
| **Click-through** | Warm audience before sending to offer; best for SaaS, subscriptions | pricing-page, products-page, signup |
| **Lead capture** | Collect email for nurture; forms 5 fields or fewer (longer forms cause ~81% abandonment) | newsletter-signup, contact-page |
| **Product-focused** | Deep-dive features and benefits; product launch | products-page, features-page |
| **Comparison** | X vs Y; competitor brand keyword ads; commercial intent | alternatives-page, features-page, pricing-page |
| **Use cases / Solutions** | For integrated products hard to split into tools | features-page, services-page |
| **Free tools** | Standalone utilities; lead gen; same ICP; excerpt from product | tools-page-generator; tool page as LP when gated |
| **Bridge/bonus** | Extra incentive to purchase through your link | pricing-page, products-page |
| **Webinar/event** | Event registration; collect signups before live | resources-page (webinar as resource) |

## Landing Page ↔ Page Types (Content & Flow)

**Pull content from** (step 2–4):
- **customer-stories-page-generator**: Testimonials, case studies for social proof; Challenge→Solution→Results snippets
- **faq-page-generator**: Objection-handling FAQ section; reuse conversion-related Q&A
- **features-page-generator**: Benefit-first feature copy for "Explain value" step
- **resources-page-generator**: Lead magnet (ebook, template) as exchange for email; webinar as resource

**CTA sends to**:
- **pricing-page-generator**: Click-through LP → pricing; signup, trial
- **products-page-generator**: Product LP → product detail or catalog
- **services-page-generator**: Service LP → contact, quote, booking
- **contact-page-generator**: Lead capture LP → contact form; B2B demo request
- **affiliate-page-generator, creator-program**: Partner signup = landing page type

**Internal linking**:
- Link LP to **homepage** (brand anchor); **about-page** (trust); **privacy-page** (form compliance)
- Avoid orphan LPs: ensure at least one internal link from sitemap, nav, or campaign hub

## Performance and Design

- **Load time**: Under 2.5 seconds; each extra second can cost ~7% conversion
- **Mobile-first**: Responsive; CTA visible without scrolling
- **Visuals**: Hero image or video can improve conversion up to 80%
- **Frontend aesthetics**: For distinctive typography, motion, spatial composition, backgrounds—see **brand-visual-generator** Frontend Aesthetics
- **Disclosure**: FTC-compliant affiliate/paid disclosure when applicable

## Pre-Delivery Checklist

Before shipping a landing page, verify:

| Category | Check |
|----------|-------|
| **Visual** | No emojis as icons (use SVG); icons from consistent set (Heroicons/Lucide); hover states don't cause layout shift |
| **Interaction** | All clickable elements have `cursor-pointer`; hover provides clear feedback; transitions 150–300ms |
| **Accessibility** | Images have alt text; form inputs have labels; color not sole indicator; `prefers-reduced-motion` respected |
| **Layout** | No horizontal scroll on mobile; content not hidden behind fixed nav; responsive at 375px, 768px, 1024px |
| **Performance** | Load time under 2.5s; LCP optimized; images use WebP/lazy loading where appropriate |
| **Images** | See **image-optimization** for alt, format, responsive, lazy loading |

## Output Format

- **Headline** and subheadline
- **Structure** (5-step flow sections)
- **Trust signals** placement
- **CTA** copy and placement
- **Objection handling** (FAQ, guarantees)
- **Internal links** (destination pages)
- **SEO** metadata (if page is indexed)

## Related Skills

- **hero-generator**: Hero section (step 1)
- **grid, list**: Content layout below hero; sections, features, testimonials
- **cta-generator**: CTA button design and placement
- **image-optimization**: Alt, WebP, LCP, responsive, lazy loading
- **pricing-page-generator**: Click-through LP destination; signup CTA
- **faq-page-generator**: Objection-handling FAQ section
- **homepage-generator**: Multi-purpose home vs single-goal landing; similar structure
- **paid-ads-strategy**: Ad-to-page alignment; when to use paid ads
- **alternatives-page-generator**: Competitor brand keyword ads → comparison LP (not blog)
- **programmatic-seo**: Scale landing pages via template + data
- **template-page-generator**: Template structure for programmatic LPs
- **title-tag, meta-description, page-metadata**: Landing page metadata

---
name: integrations-page-generator
description: When the user wants to create, optimize, or audit integrations, plugins, or extensions pages. Also use when the user mentions "integrations page," "plugins," "extensions," "add-ons," "API integrations," "connect with X," or "marketplace." For sitewide page planning, use website-structure.
metadata:
  version: 1.0.1
---

# Pages: Integrations / Plugins

Guides integrations, plugins, and extensions pages. Shows how the product connects with Canva, Slack, Zapier, and other platforms. Common for SaaS, tools, and developer products.

**When invoking**: On **first use**, if helpful, open with 1–2 sentences on what this skill covers and why it matters, then provide the main output. On **subsequent use** or when the user asks to skip, go directly to the main output.

## Initial Assessment

**Check for project context first:** If `.claude/project-context.md` or `.cursor/project-context.md` exists, read it for product, integrations, and target platforms.

Identify:
1. **Type**: Native integrations, plugins, extensions, API, webhooks
2. **Platforms**: Which to feature (Slack, Notion, Figma, etc.)
3. **Format**: Single page vs. per-integration pages
4. **Primary goal**: Install, connect, sign up

## Page Structure

| Section | Purpose |
|---------|---------|
| **Headline** | "Integrate with [Platforms]" or "Connect [Product] to Your Stack" |
| **Value** | Why integrations matter; workflow benefits |
| **Catalog** | Grid or list: logo, name, short description, "Connect" or "Install" |
| **Categories** | By use case (Productivity, Design, Dev) or platform type |
| **API** | Link to api-page or docs if developer-focused |
| **CTA** | Browse all, request integration, build your own |

## Best Practices

### Organization

- **By category**: Productivity, Design, Marketing, Dev tools
- **By platform**: Slack, Notion, Figma, Zapier
- **Search/filter**: For 20+ integrations
- **Featured**: Highlight top 5–10; rest in catalog

### Content

- **Per integration**: Logo, 1–2 sentence benefit, "Connect" CTA
- **Use cases**: "Use with Slack to get notifications"
- **Screenshots**: Show connected workflow when possible

### SEO

- **Intent**: Informational + commercial; "X integration," "X plugin"
- **Title**: "Integrations | Connect [Product] to [Platforms]" or "[Product] + Slack"
- **Internal links**: API, docs, features, pricing

## Output Format

- **Headline** and value proposition
- **Catalog structure** (categories, layout)
- **Per-integration** copy (name, benefit, CTA)
- **Internal links** (API, docs)
- **SEO** metadata

## Related Skills

- **card**: Integration card structure; logo, name, description, CTA; catalog grid
- **grid, list**: Catalog layout; grid or list format
- **api-page-generator**: API overview; link for developer integrations
- **docs-page-generator**: Integration setup guides in docs
- **category-page-generator**: Catalog layout for many integrations
- **landing-page-generator**: Integration-specific landing pages

---
name: download-page-generator
description: When the user wants to create, optimize, or audit a download page for desktop or mobile app. Also use when the user mentions "download page," "app download," "desktop download," "mobile app download," "App Store," "Play Store," "get the app," "install app," or "download CTA." For app install ads, use app-ads.
metadata:
  version: 1.0.1
---

# Pages: Download Page

Guides download page structure and optimization for desktop and mobile app downloads. Purpose: convert visitors into installers by clearly presenting value, platform options, and trust signals.

**When invoking**: On **first use**, if helpful, open with 1–2 sentences on what this skill covers and why it matters, then provide the main output. On **subsequent use** or when the user asks to skip, go directly to the main output.

## Initial Assessment

**Check for project context first:** If `.claude/project-context.md` or `.cursor/project-context.md` exists, read it for product, audience, and value proposition.

Identify:
1. **App type**: Desktop (Windows, macOS, Linux) or mobile (iOS, Android, both)
2. **Traffic source**: Organic, paid, email, referral
3. **Distribution**: App Store / Play Store only, direct download, or both

## Page Purpose

| Purpose | Goal |
|---------|------|
| **Download** | Guide users to install desktop or mobile app |
| **Trust** | Build confidence before download (security, privacy, reviews) |
| **Conversion** | Maximize download rate, store visits, install conversion |

## Download Page Structure

| Step | Purpose | Elements |
|------|---------|----------|
| **1. Value proposition** | Why download | Headline, benefit-focused copy, key features |
| **2. Platform selection** | Clear path | Desktop: OS detection or manual pick; Mobile: App Store / Play Store buttons |
| **3. Trust signals** | Reduce friction | Ratings, download count, security badges, privacy note |
| **4. Visual proof** | Show the app | Screenshots, app previews, video |
| **5. CTA** | Primary action | Single, prominent download button |

## Platform-Specific Layout

### Desktop App

- **OS detection**: Auto-detect OS or show "Download for Windows / macOS / Linux"
- **Direct download**: One-click .exe / .dmg / .deb etc.
- **Alternatives**: Optional "Other platforms" or "Command line" for power users

### Mobile App

- **Dual store**: App Store + Play Store buttons side by side
- **Smart redirect**: Detect device and show relevant store first; still show both
- **QR code**: Optional for desktop visitors to scan and install on phone

## Optimization Best Practices

### Performance

- **Load time**: Under 3 seconds; each extra second can cost ~7% conversion
- **Mobile-first**: Most app download traffic is mobile; responsive, thumb-reachable CTAs
- **Image optimization**: WebP, lazy loading, compression (e.g. TinyPNG, ImageOptim)

### Conversion

- **Single primary CTA**: "Download Free Now," "Get on App Store," "Get for Windows"
- **Above the fold**: CTA visible without scrolling
- **Repeat CTA**: On longer pages, repeat at logical points
- **A/B test**: CTA color, size, copy, placement

### Trust & Social Proof

- **Star ratings**: Show App Store / Play Store ratings
- **Download count**: "10M+ downloads," "Trusted by X users"
- **Testimonials**: User quotes, media logos
- **Security**: Security badges if collecting sensitive info

### Content

- **Top 3–5 features**: Benefit-focused, scannable bullet points
- **Screenshots**: High-quality, show app in action
- **Video**: App preview or demo video

### Alignment with Traffic

- **Ads**: If from PPC, ensure message matches ad (offer, platform); see **paid-ads-strategy**
- **Email**: Match campaign message and CTA

## Output Format

- **Headline** and subheadline
- **Structure** (5-step flow sections)
- **Platform layout** (desktop vs mobile)
- **CTA** copy and placement
- **Trust signals** placement
- **SEO** metadata (if page is indexed)

## Related Skills

### Pages

- **landing-page-generator**: Download page is a type of landing page; apply LP principles
- **homepage-generator**: Homepage often links to download page
- **features-page-generator**: Feature copy for "Explain value" section

### Components

- **hero-generator**: Hero section (value proposition)
- **cta-generator**: Download button design
- **trust-badges-generator**: Social proof, ratings
- **testimonials-generator**: User testimonials

### SEO

- **title-tag, meta-description, page-metadata**: Download page metadata

---
name: customer-stories-page-generator
description: When the user wants to create, optimize, or audit customer stories or case study pages. Also use when the user mentions "case studies," "customer stories," "success stories," "testimonials page," "case study," "customer proof," "social proof page," or "results page." For testimonial components, use testimonials-generator.
metadata:
  version: 1.0.1
---

# Pages: Customer Stories

Guides customer story and case study page content, structure, and conversion.

**When invoking**: On **first use**, if helpful, open with 1-2 sentences on what this skill covers and why it matters, then provide the main output. On **subsequent use** or when the user asks to skip, go directly to the main output.

## Initial Assessment

**Check for project context first:** If `.claude/project-context.md` or `.cursor/project-context.md` exists, read it for product, proof points, and customer language.

Identify:
1. **Story format**: Full case study, quote snippet, video
2. **Industries/use cases**: Who to showcase
3. **Metrics**: What results to highlight

## Best Practices

### Structure (Challenge -> Solution -> Results)

| Section | Content |
|---------|---------|
| **Headline** | Benefit-driven; lead with outcome |
| **Challenge** | Client's problem, pain points |
| **Solution** | How your product helped |
| **Results** | Quantifiable metrics, before/after |
| **Quote** | Direct testimonial from client |
| **CTA** | Next step (demo, contact, read more) |

### Content Principles

- **Lead with results**: Outcomes first, not background
- **Specific metrics**: "Increased revenue 40%" not "great results"
- **Quotes**: Direct, attributed, credible
- **Scannable**: Consistent template; easy to skim
- **Concise**: Enough value without losing interest

### Visual Elements

- **Logos**: Client branding (with permission)
- **Charts/graphs**: Before-after, metrics
- **Video**: Testimonials, interviews
- **Expandable sections**: For deeper detail

### Why It Matters

- 54% of buyers review case studies before purchasing
- 73% of successful content marketers use them
- Builds credibility, justifies pricing, shortens sales cycles

### Storytelling

- **Problem** = beginning
- **Solution** = climax
- **Results** = resolution
- **Hard facts**: Statistics for impact

## Output Format

- **Template** structure
- **Story** outline (challenge, solution, results)
- **Metrics** to capture
- **SEO** metadata and schema (if indexing)
- **Internal linking** to product/pricing

## Related Skills

- **landing-page-generator**: Case studies and testimonials for LP social proof (step 2)
- **url-slug-generator**: URL slug for case study pages (e.g. /customers/case-slug); 3-5 words
- **about-page-generator**: Social proof complements About
- **pricing-page-generator**: Case studies support pricing justification
- **homepage-generator**: Customer stories on homepage
- **schema-markup**: CaseStudy schema

---
name: contest-page-generator
description: When the user wants to create, optimize, or audit a giveaway, contest, or promotional campaign page. Also use when the user mentions "giveaway," "contest," "sweepstakes," "promo," "Gleam," "Woobox," or "viral campaign." For sitewide page planning, use website-structure.
metadata:
  version: 1.0.1
---

# Pages: Giveaway / Contest

Guides giveaway and contest pages for promotional campaigns. Drives signups, engagement, and viral sharing. Often uses Gleam, Woobox, Viralsweep, or similar. Common for e-commerce, SaaS launches, and community growth.

**When invoking**: On **first use**, if helpful, open with 1–2 sentences on what this skill covers and why it matters, then provide the main output. On **subsequent use** or when the user asks to skip, go directly to the main output.

## Initial Assessment

**Check for project context first:** If `.claude/project-context.md` or `.cursor/project-context.md` exists, read it for product and campaign goals.

Identify:
1. **Type**: Giveaway, contest, sweepstakes, referral campaign
2. **Prize**: Product, discount, cash; value and appeal
3. **Tool**: Gleam, Woobox, Viralsweep, custom
4. **Primary goal**: Email signup, social follows, referrals

## Page Structure

| Section | Purpose |
|---------|---------|
| **Headline** | "Win [Prize]" or "Enter the [Contest Name]" |
| **Prize** | What they win; image, value, appeal |
| **Rules** | How to enter; eligibility; end date |
| **Actions** | Required actions (email, follow, share) |
| **Countdown** | Urgency; end date visible |
| **Legal** | Official rules link; disclosure |

## Best Practices

### Conversion

- **Low friction**: Email only for entry; optional bonus entries for shares
- **Urgency**: Countdown; limited spots or time
- **Social proof**: "X people entered"; "Last day"

### Legal

- **Official rules**: Required; link to full terms
- **Eligibility**: Age, region, exclusions
- **Disclosure**: FTC-compliant; no purchase necessary

### Tools

- **Gleam, Woobox, Viralsweep**: Embed or link
- **UTM**: Track campaign source
- **Landing page**: Custom page + embed; or tool's hosted page

## Output Format

- **Headline** and prize copy
- **Rules** summary
- **Entry actions** (required, bonus)
- **Legal** checklist
- **Tool** integration notes

## Related Skills

- **discount-marketing-strategy**: Contest prize = discount; promo campaign design
- **landing-page-generator**: Contest page is a landing page; apply LP principles
- **disclosure-page-generator**: Affiliate/sponsor disclosure if applicable
- **popup-generator**: Contest popup to drive traffic

---
name: category-page-generator
description: When the user wants to create, optimize, or audit e-commerce category pages or listing pages. Also use when the user mentions "category page," "product category," "faceted navigation," "filter URLs," "e-commerce listing," "category SEO," "category structure," "product filters," or "listing page." For programmatic SEO at scale, use programmatic-seo.
metadata:
  version: 1.0.1
---

# Pages: Category Pages

Guides e-commerce category page structure, content, and SEO optimization. Category pages organize products by attributes and drive 3x more organic revenue than product pages by ranking for broad, high-volume keywords.

**When invoking**: On **first use**, if helpful, open with 1-2 sentences on what this skill covers and why it matters, then provide the main output. On **subsequent use** or when the user asks to skip, go directly to the main output.

## Initial Assessment

**Check for project context first:** If `.claude/project-context.md` or `.cursor/project-context.md` exists, read it for product catalog and site structure.

Identify:
1. **Catalog**: Product count, categories, subcategories
2. **Facets**: Filters (size, color, price, brand, etc.)
3. **URL structure**: Current hierarchy, parameter handling

## Category Structure

### Hierarchy

| Principle | Practice |
|-----------|----------|
| **Logical grouping** | General -> specific (e.g., Furniture -> Bedroom furniture -> Beds) |
| **User search intent** | Match how users search (e.g., "bedroom furniture" vs "furniture") |
| **Crawl depth** | <=4 clicks from homepage; shorter paths improve indexing |
| **Long-tail categories** | Niche categories convert better (36% vs 11.5% for broad) |

### URL Structure

- **Subfolders**: `example.com/shoes/sneakers`, `example.com/shoes/outdoor-shoes`
- **Slugs**: Descriptive, keyword-rich; lowercase; no stop words
- **Avoid**: Dates, timestamps, `/category/` prefix
- **Breadcrumbs**: Show path; help users and crawlers

## Faceted Navigation (Filters)

Filters create many URL combinations (size + color + price). Manage to avoid duplicate content and crawl waste:

| Strategy | Use |
|----------|-----|
| **Canonical** | Point all faceted URLs to base category URL |
| **robots.txt** | Block faceted URLs from indexing if needed |
| **nofollow** | Add to internal links to faceted URLs |
| **JavaScript** | Keep filters client-side; single URL for category |

## On-Page Content

### Content Requirements

- **150-300 words** unique copy; pages with this rank ~2.7x higher than product-only grids
- **Placement**: After hero/H1; FAQ block at bottom
- **Purpose**: Help users decide; answer curation, materials, recommendations
- **Avoid**: Manufacturer copy; crowding product grid

### SEO Elements

| Element | Practice |
|---------|----------|
| **H1** | One per page; primary keyword; clear purpose |
| **Title tag** | 50-60 chars; keyword; compelling for CTR |
| **Meta description** | 150-160 chars; value props (free shipping, returns) |
| **Schema** | ItemList, Product; AggregateRating if reviews; FAQ if applicable |

### Trust & Conversion

- **Reviews**: Star ratings in SERPs; 99.9% of users read reviews; see **serp-features** for review rich results
- **FAQ**: Answer materials, quality, recommendations; +157% conversion when used
- **Guides**: Link to product guides; internal linking for SEO

## Technical

- **Consistent layout**: Same template across categories; predictable UX
- **Mobile**: Responsive; touch targets >=44x44px
- **Redirects**: 301 to category when product pages move; avoid breaking hierarchy

## Output Format

- **Structure** (hierarchy, URL paths)
- **Facet strategy** (canonical, nofollow, robots)
- **Content** (H1, intro copy, FAQ)
- **SEO** (metadata, schema)
- **Checklist** for audit

## Related Skills

- **programmatic-seo**: Programmatic SEO strategy; category pages as template-based scale
- **card**: Card layout; product card structure, grid design
- **grid**: Product grid layout; responsive columns
- **products-page-generator**: Product cards, grid layout
- **canonical-tag**: Faceted URL canonicalization
- **schema-markup**: ItemList, Product, FAQ schema
- **internal-links**: Category linking
- **breadcrumb-generator**: Breadcrumb trail for category hierarchy
- **url-structure**: URL hierarchy

---
name: alternatives-page-generator
description: When the user wants to create, optimize, or audit alternatives or comparison content (page or blog article). Also use when the user mentions "alternatives page," "alternatives listicle," "X alternatives," "competitor comparison," "vs page," "compare page," "best alternatives to X," "switch from X," "competitor brand traffic," "brand keyword ads," or "intercept competitor search." For competitor research, use competitor-research.
metadata:
  version: 1.2.1
---

# Pages: Alternatives / Compare

Guides alternatives and comparison content that target "X alternatives" and "X vs Y" search intent. **Purpose**: Intercept competitor brand traffic—organic (SEO) and paid (brand keyword ads). High-intent, bottom-of-funnel; users searching alternatives are ready to switch. **Content format**: Standalone page (/alternatives, /alternatives-to-notion) or blog article (/blog/notion-alternatives). Same structure; blog builds topical authority.

**When invoking**: On **first use**, if helpful, open with 1–2 sentences on what this skill covers and why it matters, then provide the main output. On **subsequent use** or when the user asks to skip, go directly to the main output.

## Purpose & Keywords

| Goal | Use |
|------|-----|
| **SEO** | Rank for "[Competitor] alternatives," "alternatives to [Competitor]," "[Competitor] vs [You]" |
| **PPC** | Bid on competitor brand + "alternative"/"vs"; send to alternatives landing page |
| **Intent** | High-intent; short sales cycle; users already understand the category |

**Keyword patterns**: alternatives, alternative, vs, comparison, compare, "best [X] alternatives." Include name variants (e.g., "SuccessBox" and "Success Box") in metadata.

## Competitor Types

| Type | Description | Example |
|------|-------------|---------|
| **Direct** | Obvious rivals | FreshBooks vs QuickBooks |
| **Bundlers** | Large platforms; users want lighter/cheaper | Salesforce, HubSpot → "cheaper Salesforce for SMB" |
| **Indirect** | Same problem, different solution | "Spreadsheet alternative" for accounting software |

Target all three for long-tail growth; don't only target the biggest competitor.

## Content Format: Page vs Blog Article

| Format | Path | Use |
|--------|------|-----|
| **Standalone page** | /alternatives, /alternatives-to-[competitor] | Dedicated hub; strong for your own product as alternative; **preferred for paid ads** (competitor brand keyword ads) |
| **Blog article** | /blog/[product]-alternatives, /blog/best-[x]-alternatives | Listicle format; common for affiliate, challenger brands; builds topical authority; **SEO/organic only** |

Both formats use the same structure (quick verdict, comparison table, individual reviews, FAQ). **For competitor brand keyword ads (Google Ads, etc.)**: use a **dedicated landing page**, not a blog. Users searching competitor brands expect direct alternatives; a blog increases bounce; a comparison page matches intent and converts better. Blog is for organic traffic and topical authority.

### URL Structure

- **Hub**: /alternatives
- **Per-competitor**: /alternatives-to-[competitor] or /[competitor]-alternative
- Short, keyword-rich, crawlable; no keyword stuffing

## Initial Assessment

**Check for project context first:** If `.claude/project-context.md` or `.cursor/project-context.md` exists, read it for product, competitors, and differentiators.

Identify:
1. **Format**: Standalone page vs. blog article; single hub vs. per-competitor pages
2. **Competitors**: Who to include; avoid over-promoting direct rivals
3. **Primary goal**: Sign up, trial, demo; position as fair comparison
4. **Tone**: Objective, helpful; avoid disparaging competitors

## Page / Article Structure

| Section | Purpose |
|---------|---------|
| **Headline** | "Best [Product Category] Alternatives in [Year]" or "[Product] vs [Competitor]"; plain promise, avoid cute titles |
| **Problem-focused intro** | Empathy for pain; validate why they're searching; tease the payoff |
| **Quick verdict** | 5–8 lines above the fold: who it's for, top picks, decision shortcut |
| **Pros/cons of original** | Build trust; acknowledge why someone might leave; who should still keep it |
| **Comparison table** | Place early, not hidden; 4–6 columns (best for, price, ease, key limit); **HTML table** (not image)—required for AEO/GEO; scannable |
| **Alternatives list** | 6–10 picks; each with "best for" label, proof, tradeoff, pricing snapshot |
| **Migration** | Link to migration-page if applicable |
| **FAQ** | "Is X better than Y?"; "Can I migrate from X?"; pricing, trials |
| **CTA** | Try free, start trial, book demo; one CTA above fold, one near end |

## Best Practices

### SEO

- **Intent**: Commercial; "alternatives to X," "X vs Y," "best X"
- **Title**: "[Product] Alternatives: Top [N] Options Compared | [Your Product]" or "Top [Competitor] Alternatives for [Year]: Better & Cheaper"; under 60 chars
- **Meta**: Lead with pain point or question; weave keyword early; end with benefit; max 160 chars
- **Content**: 1500+ words for alternatives hub; 800+ for single comparison
- **Internal links**: Link to features, pricing, migration, use cases

### Fairness & Trust

- **Objective tone**: Acknowledge competitor strengths; avoid FUD
- **Transparent criteria**: Explain how you compare (features, pricing, use case)
- **Update regularly**: Pricing and features change; date the comparison
- **Verifiable claims**: Link to pricing pages, docs; cite sources; add "as of [date]" for prices

### Conversion

- **Soft sell**: Position your product as one option; let value speak
- **Migration CTA**: "Switch in minutes" if migration is easy
- **Social proof**: Customer quotes from switchers

### AEO / GEO (AI Search)

- **HTML tables**: Use plain HTML for comparison tables; AI engines parse structured data; avoid images or fancy JS sliders
- **Structured data**: Objective entity mappings; bullets over prose for scannability; see **entity-seo**
- **Third-party validation**: G2, niche blogs mentioning you as alternative help AI cite you

### Brand Keyword Ads (PPC)

- **Use case**: Bid on "[Competitor] alternative," "[Competitor] vs [You]" when allowed by platform
- **Landing page**: Use a **dedicated alternatives/comparison page**, not a blog article. High-intent users expect direct alternatives; blog increases bounce. See **google-ads** Competitor Brand Keywords.
- **Ad-to-page alignment**: H1 mirrors search intent ("X vs [You]"); comparison table; one-line differentiator; strong CTA; see **landing-page-generator**, **paid-ads-strategy**

### Programmatic SEO (Scale)

- **When**: 50+ competitors; can't write manually
- **Data schema**: Price, key features, support level; store in API or headless CMS
- **Template**: One structure; populate per competitor; verify data quarterly (pricing changes)
- **Name variants**: Include "SuccessBox" and "Success Box" in metadata

### Measurement

| Metric | Purpose |
|--------|---------|
| **Assisted conversions** | User may convert later; attribution |
| **Bounce + pricing click** | Bounce to pricing = intent signal |
| **GEO share of voice** | Search "[Competitor] alternative" on Perplexity; are you cited? |
| **CTA clicks** | "Switch Now" button performance |

## Output Format

- **Competitor list** (Direct, Bundlers, Indirect)
- **Keyword list** (alternatives, vs, comparison; name variants)
- **Headline** and problem-focused intro
- **Comparison structure** (table columns, criteria; HTML table)
- **Per-competitor** summary (2–3 sentences each)
- **Your product** positioning
- **Internal links** (migration, features, pricing)
- **SEO** metadata (title, meta; under 60/160 chars)
- **PPC** (if applicable): ad-to-page alignment

## Related Skills

- **article-page-generator**: Alternatives as blog listicle; same structure, different path
- **migration-page-generator**: Migration guides for switchers; link from alternatives
- **landing-page-generator**: When alternatives page is used for paid ads (PPC), apply LP principles; ad-to-page alignment
- **google-ads**: Competitor brand keyword campaigns; LP (not blog) for competitor ads; see Competitor Brand Keywords section
- **paid-ads-strategy**: When to use paid ads; ad-to-page alignment; channel selection; competitor brand bidding
- **programmatic-seo**: Scale alternatives pages across 50+ competitors; template + data
- **features-page-generator**: Feature comparison content
- **pricing-page-generator**: Pricing comparison
- **customer-stories-page-generator**: Switcher testimonials
- **entity-seo**: Entity mappings; Organization, Person; GEO citation

---
name: affiliate-page-generator
description: When the user wants to create, optimize, or audit affiliate program page content. Also use when the user mentions "affiliate program," "affiliate page," "partner program," "referral program page," "affiliate landing," "partner landing," "commission page," or "affiliate signup." For affiliate program strategy, use affiliate-marketing.
metadata:
  version: 1.0.1
---

# Pages: Affiliate Program

Guides affiliate program page content and structure for conversion and quality affiliate signups.

**When invoking**: On **first use**, if helpful, open with 1-2 sentences on what this skill covers and why it matters, then provide the main output. On **subsequent use** or when the user asks to skip, go directly to the main output.

## Initial Assessment

**Check for project context first:** If `.claude/project-context.md` or `.cursor/project-context.md` exists, read it for product, audience, and proof points.

Identify:
1. **Commission model**: Percentage, flat rate, recurring, one-time
2. **Target affiliates**: Bloggers, influencers, agencies, etc.
3. **Product fit**: Why affiliates would promote you

## Best Practices

### Four Key Questions Affiliates Ask

1. **How much can I earn?** ? Be specific upfront
2. **Is this product worth promoting?** ? Product value, audience fit
3. **Will I be set up for success?** ? Resources, support, tracking
4. **Can I trust you to pay me?** ? Payment terms, proof

### Commission Structure (Transparency)

| Item | Include |
|------|---------|
| Commission rate | Percentage or flat |
| Recurring vs. one-time | Duration of recurring |
| Cookie/tracking window | How long the cookie lasts |
| Minimum payout | Threshold to receive payment |
| Payment schedule | When payouts occur |
| Payment methods | PayPal, bank transfer, etc. |
| Refund/chargeback policy | How they affect commissions |

### Value Proposition

- **Specific numbers**: "Earn 30% recurring--up to $147/month per customer"
- **Earning calculator**: Help affiliates visualize income
- **Avoid vague**: "Great commissions" ? "30% recurring for 12 months"

### Product Information

Affiliates stake their reputation; convince them it's worth promoting:
- What it does (clear, jargon-free)
- Who it's for (audience, use cases)
- Why it's superior (differentiators)
- Social proof (customers, testimonials, logos)

### Design

- Treat like a product landing page—professional, engaging; same quality as main marketing pages
- **Single-focused offer**: One primary goal (signup); pages with multiple offers get ~266% fewer leads
- **Minimal navigation**: Remove or reduce nav links; can increase conversion 2–28%
- **Mobile-first**: Thumb-reachable CTA above fold; ~70% of users consider page speed
- **Hero image/video**: Visuals can improve conversion up to 80%
- **FTC-compliant disclosure**: Affiliate relationship disclosure required

### Post-Launch

- Submit to affiliate program directories for discoverability
- Add affiliate page link to main nav or footer

## Output Format

- **Headline** and value proposition
- **Commission** section structure
- **Product** summary for affiliates
- **FAQ** for common affiliate questions
- **CTA** and signup flow
- **SEO** metadata

## Related Skills

- **affiliate-marketing**: Affiliate marketing strategy, recruitment, channels
- **landing-page-generator**: Generic landing page structure, CTA, conversion flow; apply to affiliate signup
- **pricing-page-generator**: Commission structure clarity
- **customer-stories-page-generator**: Social proof for product
- **homepage-generator**: Link from homepage
- **hero-generator, cta-generator**: Hero and CTA design for affiliate page
- **title-tag, meta-description, page-metadata**: Affiliate page metadata

---
name: terms-page-generator
description: When the user wants to create, optimize, or structure Terms of Service page. Also use when the user mentions "terms of service," "terms and conditions," "terms of use," "user agreement," "ToS," "legal terms," "service agreement," or "terms page." For legal overview page, use legal-page-generator.
metadata:
  version: 1.0.1
---

# Pages: Terms of Service

Guides Terms of Service page content, structure, and compliance.

**When invoking**: On **first use**, if helpful, open with 1–2 sentences on what this skill covers and why it matters, then provide the main output. On **subsequent use** or when the user asks to skip, go directly to the main output.

## Initial Assessment

Identify:
1. **Product type**: SaaS, e-commerce, content, marketplace
2. **Jurisdiction**: Governing law, dispute resolution
3. **User types**: B2B, B2C, both
4. **Indexing**: Typically noindex for legal pages

## Best Practices

### Required Sections

| Section | Content |
|---------|---------|
| **Acceptance** | How agreement is formed (signup, use) |
| **Service description** | What you provide |
| **User obligations** | Acceptable use, account security |
| **Intellectual property** | Who owns what |
| **Payment** | If applicable; billing, refunds |
| **Liability** | Limitations, disclaimers |
| **Termination** | When and how accounts end |
| **Governing law** | Jurisdiction, dispute resolution |
| **Changes** | How you'll notify of updates |
| **Contact** | How to reach you about terms |

### Content Principles

- **Clear language**: Plain English where possible
- **Structure**: Headings, table of contents
- **Updates**: Date; version if needed
- **Legal review**: Have lawyer review

### Placement

- **Footer**: Link on every page
- **Signup**: Require acceptance (checkbox)
- **Checkout**: Link before purchase

### SEO

- **Noindex**: Common for terms
- **Canonical**: If multiple versions

## Output Format

- **Outline** (sections)
- **Key points** per section
- **Acceptance** flow (signup, checkout)
- **Disclaimer**: Recommend legal review

## Related Skills

- **legal-page-generator**: Terms is a legal page type
- **privacy-page-generator**: Often linked together
- **contact-page-generator**: Contact for terms questions
- **indexing**: noindex for terms

---
name: shipping-page-generator
description: When the user wants to create or optimize a shipping or delivery information page. Also use when the user mentions "shipping," "delivery," "shipping policy," "delivery times," "shipping page," "free shipping," "shipping rates," "delivery options," or "shipping info." For legal overview, use legal-page-generator.
metadata:
  version: 1.0.1
---

# Pages: Shipping / Delivery

Guides shipping and delivery information page content for e-commerce.

**When invoking**: On **first use**, if helpful, open with 1–2 sentences on what this skill covers and why it matters, then provide the main output. On **subsequent use** or when the user asks to skip, go directly to the main output.

## Initial Assessment

Identify:
1. **Regions**: Domestic, international
2. **Carriers**: Options, costs
3. **Timelines**: Standard, express, cutoff times

## Best Practices

### Essential Elements

| Element | Purpose |
|---------|---------|
| **Regions** | Where you ship; restrictions |
| **Options** | Standard, express; costs |
| **Timelines** | Processing; delivery estimates |
| **Cutoffs** | Order-by for same-day, etc. |
| **Tracking** | How to track orders |
| **Issues** | Lost, damaged; contact |

### Content

- **Clear**: No ambiguity on costs or times
- **Up to date**: Reflect current carriers, rates
- **FAQ format**: Common questions; easy to scan

### Placement

- Footer; checkout; product pages
- Link from cart when relevant

## Output Format

- **Outline** for shipping page
- **Key sections** (regions, options, timelines)
- **FAQ** structure if applicable

## Related Skills

- **refund-page-generator**: Often paired in footer
- **faq-page-generator**: Shipping questions in FAQ
- **legal-page-generator**: Sometimes grouped with policies

---
name: refund-page-generator
description: When the user wants to create or optimize a refund or return policy page. Also use when the user mentions "refund policy," "return policy," "money-back guarantee," "returns and refunds," "refund page," "return process," "refund terms," or "satisfaction guarantee." For legal overview, use legal-page-generator.
metadata:
  version: 1.0.1
---

# Pages: Refund / Return Policy

Guides refund and return policy page content for e-commerce and digital products.

**When invoking**: On **first use**, if helpful, open with 1–2 sentences on what this skill covers and why it matters, then provide the main output. On **subsequent use** or when the user asks to skip, go directly to the main output.

## Initial Assessment

Identify:
1. **Product type**: Physical, digital, subscription, or mixed
2. **Policy**: Time window, conditions, process
3. **Jurisdiction**: Consumer rights (EU, etc.)

## Best Practices

### Essential Elements

| Element | Purpose |
|---------|---------|
| **Eligibility** | What can be returned; time limits |
| **Process** | How to request; steps |
| **Refund method** | Original payment; timeline |
| **Exclusions** | Non-refundable items |
| **Contact** | Support for returns |

### Content

- **Clear**: Simple language; no legalese
- **Scannable**: Headings, bullets
- **Complete**: Answer common questions
- **Up to date**: Review when policy changes

### Placement

- Footer; checkout; product pages
- Link from FAQ when relevant

## Output Format

- **Outline** for refund/return policy
- **Key sections** and content
- **Disclaimer**: Recommend legal review

## Related Skills

- **legal-page-generator**: Refund is often a legal page
- **faq-page-generator**: FAQ may link to refund policy
- **privacy-page-generator**: Footer grouping

---
name: privacy-page-generator
description: When the user wants to create, optimize, or structure Privacy Policy page. Also use when the user mentions "privacy policy," "privacy page," "data protection," "GDPR compliance," "privacy notice," "data privacy," "CCPA," "cookie policy," or "personal data." For legal overview page, use legal-page-generator.
metadata:
  version: 1.0.1
---

# Pages: Privacy Policy

Guides Privacy Policy page content, structure, and compliance.

**When invoking**: On **first use**, if helpful, open with 1–2 sentences on what this skill covers and why it matters, then provide the main output. On **subsequent use** or when the user asks to skip, go directly to the main output.

## Initial Assessment

Identify:
1. **Jurisdiction**: GDPR, CCPA, other regional requirements
2. **Business model**: SaaS, e-commerce, content, ads
3. **Data collected**: Cookies, forms, analytics, third parties
4. **Indexing**: Typically noindex for legal pages

## Best Practices

### Required Sections

| Section | Content |
|---------|---------|
| **What we collect** | Types of data (name, email, usage, etc.) |
| **Why we collect** | Purposes (service, marketing, analytics) |
| **How we use** | Processing, storage, sharing |
| **How long we keep** | Retention periods |
| **Your rights** | Access, correction, deletion, opt-out |
| **Cookies** | Types, purposes, how to manage |
| **Third parties** | Who receives data (analytics, payment) |
| **Contact** | How to exercise rights, data protection contact |

### Content Principles

- **Clear language**: Plain English; avoid legalese where possible
- **Structure**: Headings, table of contents, scannable
- **Updates**: Date of last update; version if needed
- **Legal review**: Have lawyer review for compliance

### Placement

- **Footer**: Link on every page
- **Forms**: Link near signup, contact, checkout
- **Cookie banner**: Link to Privacy and Cookie policy

### SEO

- **Noindex**: Common for legal pages
- **Canonical**: If multiple versions (e.g., by region)

## Output Format

- **Outline** (sections)
- **Key points** per section
- **Cookie** disclosure approach
- **Rights** section (GDPR/CCPA)
- **Disclaimer**: Recommend legal review

## Related Skills

- **legal-page-generator**: Privacy is a legal page type
- **terms-page-generator**: Often linked together
- **contact-page-generator**: Privacy link near forms
- **indexing**: noindex for privacy

---
name: legal-page-generator
description: When the user wants to create, optimize, or structure legal pages (Privacy, Terms, etc.). Also use when the user mentions "privacy policy," "terms of service," "legal pages," "cookie policy," "terms and conditions," "legal footer," "legal section," "compliance pages," or "legal requirements." For Privacy Policy content, use privacy-page-generator. For Terms of Service, use terms-page-generator. For Cookie Policy, use cookie-policy-page-generator.
metadata:
  version: 1.1.0
---

# Pages: Legal

Guides legal page content, structure, and SEO handling.

**When invoking**: On **first use**, if helpful, open with 1–2 sentences on what this skill covers and why it matters, then provide the main output. On **subsequent use** or when the user asks to skip, go directly to the main output.

## Initial Assessment

Identify:
1. **Page type**: Privacy Policy, Terms of Service, Cookie Policy, etc.
2. **Jurisdiction**: GDPR, CCPA, etc.
3. **Business model**: SaaS, e-commerce, content site
4. **Indexing**: Index or noindex (often noindex for legal)

## Common Legal Pages

| Page | Purpose |
|------|---------|
| **Privacy Policy** | Data collection, use, sharing, rights |
| **Terms of Service** | User agreement, limitations, termination |
| **Cookie Policy** | Cookie types, consent, management |
| **Acceptable Use** | Prohibited uses, enforcement |
| **Refund Policy** | Refund conditions (e-commerce) |

## Best Practices

### Content

- **Clear language**: Avoid legalese where possible
- **Structure**: Headings, sections, table of contents
- **Updates**: Date of last update; version if needed
- **Legal review**: Have lawyer review for compliance

### SEO

| Approach | When |
|----------|------|
| **Index** | If you want legal pages discoverable (rare) |
| **Noindex** | Common for legal; reduces low-value indexed pages |
| **Canonical** | If multiple versions (e.g., by region) |

### Placement

- Footer links to all legal pages
- Consent flows (cookie banner) link to Privacy/Cookie Policy
- Sign-up/checkout link to Terms

## Structure

- **Privacy Policy**: What data, why, how long, rights, contact
- **Terms**: Acceptance, use, IP, liability, termination, governing law
- **Cookie Policy**: Types, purposes, how to manage

## Output Format

- **Outline** for each legal page type
- **Section** structure and key points
- **SEO** recommendation (index vs. noindex)
- **Footer** link placement
- **Disclaimer**: Recommend legal review

## Related Skills

- **privacy-page-generator**: Privacy Policy page
- **terms-page-generator**: Terms of Service page
- **indexing**: noindex for legal pages
- **title-tag, meta-description, page-metadata**: Legal page metadata
- **homepage-generator**: Footer links to legal

---
name: cookie-policy-page-generator
description: When the user wants to create or optimize a cookie policy page. Also use when the user mentions "cookie policy," "cookies," "cookie consent," "GDPR cookies," "cookie banner," "cookie notice," "tracking cookies," or "cookie settings." For legal overview, use legal-page-generator.
metadata:
  version: 1.0.1
---

# Pages: Cookie Policy

Guides cookie policy page content for GDPR and transparency. Often separate from Privacy Policy.

**When invoking**: On **first use**, if helpful, open with 1–2 sentences on what this skill covers and why it matters, then provide the main output. On **subsequent use** or when the user asks to skip, go directly to the main output.

## Initial Assessment

Identify:
1. **Cookie types**: Essential, analytics, marketing, etc.
2. **Consent**: Banner, preferences, management
3. **Jurisdiction**: GDPR, ePrivacy, CCPA

## Best Practices

### Essential Elements

| Element | Purpose |
|---------|---------|
| **What are cookies** | Brief explanation |
| **Types used** | Essential, analytics, marketing |
| **Purpose** | Why each type; duration |
| **Third parties** | Who sets cookies (GA, ads) |
| **Management** | How to opt out; preferences |
| **Updates** | When policy changes |

### Content

- **Categorized**: By cookie type or purpose
- **Table**: Cookie name, purpose, duration, type
- **Clear**: Plain language
- **Actionable**: Link to consent/preferences

### Placement

- Footer; cookie banner links here
- Required for GDPR when using non-essential cookies

## Output Format

- **Outline** for cookie policy
- **Cookie table** structure
- **Consent** flow reference
- **Disclaimer**: Recommend legal review

## Related Skills

- **privacy-page-generator**: Privacy Policy; cookie policy complements
- **legal-page-generator**: Legal page grouping
- **indexing**: Often noindex

---
name: tools-page-generator
description: When the user wants to create, optimize, or audit free tools pages. Also use when the user mentions "free tools," "tools page," "toolkit," "free [X] tool," "free [X] calculator," "free [X] checker," "lead magnet tool," "programmatic tools," or "tools hub." For content strategy, use content-strategy.
metadata:
  version: 1.0.1
---

# Pages: Tools (Free Tools)

Guides free tools pages that drive traffic and lead generation for the main product. **Tools are free, standalone utilities** — not the primary monetization. They serve the same ICP as the paid product, are often extracted mini-features from the full product (low dev effort), and typically scale via programmatic SEO. Distinct from features (paid capabilities) and resources (content hub).

**When invoking**: On **first use**, if helpful, open with 1–2 sentences on what this skill covers and why it matters, then provide the main output. On **subsequent use** or when the user asks to skip, go directly to the main output.

## Initial Assessment

**Check for project context first:** If `.claude/project-context.md` or `.cursor/project-context.md` exists, read it for product, ICP, and conversion goals.

Identify:
1. **Tool types**: Calculators, checkers, converters, generators (see Tool Types below)
2. **ICP alignment**: Same audience as paid product; tools solve related problems
3. **Format**: Single tool page vs. toolkit hub + per-tool pages
4. **Gate strategy**: No signup (max traffic) vs. email gate (lead capture) vs. usage limits (taste → upgrade)
5. **Tech**: Often SPA (single-page application); lightweight, fast load

## Tools vs Features

| Dimension | Tools | Features |
|----------|-------|----------|
| **Monetization** | Free; not primary revenue | Paid product capabilities |
| **Purpose** | Lead gen, traffic, trust | Conversion, evaluation |
| **Content** | Standalone utility; excerpt from product | Full product capability list |
| **Scale** | Many tools; programmatic keywords | Fewer, curated |
| **Format** | Often SPA; toolkit hub | Benefit-led grid/list |
| **User intent** | "I need to do X now" (task) | "What can this product do?" (evaluation) |

## Tool Page Structure

| Section | Purpose |
|---------|---------|
| **Headline** | Task-focused; "Free [X] Checker" or "Calculate [Y] in Seconds" |
| **Tool UI** | Input → process → output; minimal friction |
| **Instructions** | 1–3 steps; "Enter URL → Click Analyze → Get Results" |
| **Tool description** | What it does, who it's for; SEO content |
| **FAQ** | Tool-specific: "What is [X]?", "How is [Y] calculated?" |
| **CTA** | "Get full access" / "Try [Product] free" — link to main product |
| **Related tools** | Internal links to other tools in toolkit |

## Toolkit Hub Page Structure

| Section | Purpose |
|---------|---------|
| **Headline** | "Free [Category] Tools" or "Free Tools to [Outcome]" |
| **Category tabs/sections** | e.g., SEO Tools, AI Writing Tools, Local SEO (Semrush pattern) |
| **Tool cards** | Name, one-line benefit, CTA to tool page |
| **How to use** | 3-step: Choose tool → Enter info → Get results |
| **CTA** | "Access 50+ tools with free account" |
| **Social proof** | Logos, "Trusted by X brands" |

## Tool Types (Common Patterns)

| Type | Examples | Programmatic potential |
|------|----------|-------------------------|
| **Calculators** | ROI, LTV, loan, salary, carbon footprint | "[X] calculator" keywords |
| **Checkers** | SEO, backlink, plagiarism, grammar, keyword rank | "[X] checker" keywords |
| **Converters** | Unit, currency, file format, encoding | "[X] to [Y] converter" |
| **Generators** | Sitemap, meta tags, FAQ schema, titles | "[X] generator" keywords |
| **Analyzers** | Content, readability, sentiment | "[X] analyzer" keywords |

## Best Practices

### Lead Gen Focus

- **Taste of product**: Tool delivers instant value; CTA offers "more" (full product, higher limits)
- **No signup preferred** for top-of-funnel; email gate or limits for bottom-of-funnel tools
- **Usage limits**: e.g., 3 checks/day free → upgrade for unlimited (Semrush, Ahrefs pattern)

### Same ICP, Lower Friction

- **Extract from product**: One capability from full product; low dev cost
- **Same keywords**: Tools rank for "[X] tool" while product ranks for "[X] software"
- **Bridge**: Tool users → trial signup when they hit limits or need more

### Programmatic SEO

- **Keyword patterns**: "[keyword] checker," "[city] [tool]," "[X] calculator" — template + data
- **Scale**: Many tools; each targets long-tail; see **programmatic-seo**
- **Template**: Same structure per tool; unique input/output, FAQ, meta

### Technical

- **SPA-friendly**: Single page, client-side processing; fast load
- **Schema**: SoftwareApplication, HowTo for tool pages
- **Mobile-first**: Tools often used on-the-go

## URL Structure

| Pattern | Example |
|---------|---------|
| **Hub** | /tools, /free-tools |
| **Category** | /free-tools/seo, /tools/calculators |
| **Per tool** | /free-tools/seo-checker, /tools/roi-calculator |

## SEO

- **Intent**: Informational + Transactional (task completion)
- **Title**: "Free [X] Tool \| [Product]" or "[X] Checker — No Signup"
- **Programmatic**: Template + keyword/data; avoid thin content; each tool adds unique value

## Output Format

- **Tool list** (types, names, keywords)
- **Toolkit hub structure** (if multiple tools)
- **Per-tool page structure** (sections, CTA placement)
- **Gate strategy** (no signup vs email vs limits)
- **Internal linking** (hub ↔ tools, tools ↔ product)
- **Programmatic template** (if scaling)
- **SEO** metadata

## Related Skills

- **card**: Tool card structure; name, benefit, CTA; grid layout for toolkit hub
- **grid**: Toolkit hub grid layout; responsive columns
- **features-page-generator**: Tools ≠ features; tools are free lead gen; features are paid capabilities; link from tools to product/features
- **programmatic-seo**: Tools at scale; template + data; keyword patterns
- **resources-page-generator**: Tools can be a section in resources; or standalone /tools
- **landing-page-generator**: Tool page as lead-capture LP when gated
- **schema-markup**: SoftwareApplication, HowTo for tool pages

---
name: template-page-generator
description: When the user wants to design template pages—aggregation (gallery/hub) or detail (individual template). Also use when the user mentions "template page," "template gallery," "template hub," "template detail page," "template marketplace," "programmatic template," "CMS templates," "design templates," "vibe coding templates," "UI templates," "template for users to use," or "template + data pages." For SEO-at-scale strategy (data-driven URL sets), use programmatic-seo.
metadata:
  version: 1.2.0
---

# Pages: Template Page

Guides template page design for two distinct use cases: **(1) Programmatic SEO** — template + data = scale; **(2) User-facing templates** — users browse, select, and use templates to generate their own content (CMS, images, websites, vibe coding). See **programmatic-seo** for the scale framework. This skill covers **template aggregation pages** (gallery, hub) and **template detail pages** (individual template with "use" flow).

**When invoking**: On **first use**, if helpful, open with 1–2 sentences on what this skill covers and why it matters, then provide the main output. On **subsequent use** or when the user asks to skip, go directly to the main output.

---

## Two Template Page Types

| Type | Purpose | Examples |
|------|---------|----------|
| **Template aggregation page** | Gallery, hub, category; list templates for browse and filter | Canva /templates, Figma templates, VibeCatalog /templates, uitovibe theme gallery |
| **Template detail page** | Individual template; preview, description, **"Use this template"** CTA | Single template page; user clicks to copy, customize, or open in editor |

---

## Core Function: Users Use Templates to Generate Content

Beyond SEO, template pages enable **direct use**: users select a template and generate their own content. Common patterns:

| Domain | Flow | Examples |
|--------|------|----------|
| **CMS** | Browse templates → Select → Create page/post from template | WordPress themes, Webflow templates, Notion templates |
| **Design / Images** | Browse → Preview → Customize in editor | Canva (Customize this template), Figma (Duplicate to your drafts) |
| **Website builders** | Browse → Select → Customize (colors, fonts, content) → Deploy | VibeCatalog, Lovable, Bolt.new, v0; dashboard, landing page, SaaS templates |
| **Vibe coding** | Browse UI themes → Copy style instructions → Add to AI prompt → Generate | uitovibe (copy instructions, paste into Bolt/Lovable/Cursor prompt) |

**Key CTA**: "Use this template," "Customize this template," "Copy to editor," "Get this template," "Start with this."

---

## Template Aggregation Page (Gallery / Hub)

| Section | Purpose |
|---------|---------|
| **Headline** | "Templates for [category]" or "Browse [X] templates" |
| **Filters / Categories** | By type (dashboard, landing page, resume), platform (Bolt, Lovable, Next.js), use case |
| **Template cards** | Thumbnail, name, short description, "Use" or "Preview" CTA; grid or list |
| **Search** | By keyword, tag |
| **Social proof** | "X templates," "Used by Y users," ratings |
| **CTA** | Primary action (Browse, Get started, Sign up to use) |

**Reference**: Canva organizes by 50+ design types (Docs, Presentations, Logos, Instagram Posts, etc.); Figma offers 300+ templates; VibeCatalog by project type (dashboards, landing pages). See **card** for template card structure and grid layout.

---

## Template Detail Page (Individual Template)

| Section | Purpose |
|---------|---------|
| **Hero** | Template name, one-line benefit; **primary CTA: "Use this template" / "Customize" / "Copy"** |
| **Preview** | Live preview, screenshot, or interactive demo; multiple views (desktop, mobile) |
| **Description** | What it does, who it's for, what's included |
| **Features / What's included** | Components, sections, customization options (colors, fonts, layouts) |
| **How to use** | Steps: Copy → Paste in editor / Open in [tool] → Customize |
| **Platform compatibility** | Bolt, Lovable, v0, Next.js, React, etc. |
| **FAQ** | "Can I use commercially?", "Do I get source code?", "How do I customize?" |
| **Related templates** | Internal links to similar templates |

**Vibe coding pattern** (uitovibe, VibeCatalog): Template = style instructions or full code; user copies instructions into AI prompt or downloads/clones to customize. CTA: "Copy instructions," "Add to prompt," "Get template."

---

## Template + Programmatic SEO

When templates are **generated at scale** from data (location pages, integration pages, comparison pages), use **programmatic-seo** framework:

| Section | Purpose | Data Slot |
|---------|---------|-----------|
| **Intro** | H1, intro; matches intent | `{entity_name}`, `{context}` |
| **Evidence block** | Tables, lists, verified data; avoids thin content | `{data_table}`, `{list_items}` |
| **Decision** | Recommendation, next steps | `{recommendation}` |
| **FAQ** | Schema-friendly Q&A | `{faq_items}` |
| **CTA** | Conversion | `{cta_destination}` |

See **programmatic-seo** for data, automation, pitfalls. When programmatic pages have conversion goals, apply **landing-page-generator** principles.

---

## Template + Landing Page (Conversion-Focused Programmatic)

When programmatic pages drive signup/lead capture (e.g., "[Product] for [City]" LPs), apply landing page structure to the template: Stop the scroll → Earn trust → Explain value → Remove doubt → Make the ask. See **landing-page-generator**.

---

## Common Template Patterns by Domain

| Domain | Aggregation | Detail | Use Flow |
|--------|-------------|--------|---------|
| **Design (Canva, Figma)** | Category browse, filters | Preview, "Customize" | Open in editor, drag-and-drop |
| **Vibe coding (uitovibe, VibeCatalog)** | Theme gallery, by style | Copy instructions, "Add to prompt" | Paste into Bolt/Lovable/Cursor |
| **Website (Lovable, Bolt, v0)** | By project type | Live demo, "Use template" | Clone, customize, deploy |
| **CMS** | By content type | Preview, "Create from template" | New page/post from template |
| **Programmatic SEO** | N/A (data-driven) | Output pages from template + data | Informational; CTA to product |

---

## Output Format

- **Page type** (aggregation vs detail)
- **Sections** (per type above)
- **Primary CTA** ("Use this template," "Customize," "Copy instructions")
- **User flow** (browse → preview → use → customize)
- **Programmatic alignment** (if template + data scale)
- **Schema** (ItemList for aggregation; CreativeWork, SoftwareApplication for detail)

## Related Skills

- **card**: Template card structure; thumbnail, name, description, CTA; grid layout
- **grid**: Template grid layout; responsive columns
- **programmatic-seo**: Template + data = scale; use cases, data requirements, pitfalls
- **landing-page-generator**: Conversion structure; programmatic landing pages
- **tools-page-generator**: Tool pages at scale; toolkit hub
- **alternatives-page-generator**: Alternatives/comparison at scale
- **category-page-generator**: Category structure; similar to template aggregation
- **schema-markup**: ItemList, CreativeWork, SoftwareApplication
- **url-structure**: /templates, /templates/[slug] hierarchy

---
name: resources-page-generator
description: When the user wants to create, optimize, or audit resources page or content hub. Also use when the user mentions "resources page," "resource center," "content hub," "learning center," "resource library," "downloads," "templates," "guides," or "resource hub." For content hub planning, use content-strategy.
metadata:
  version: 1.0.1
---

# Pages: Resources

Guides resources page and content hub structure for discovery and SEO.

**When invoking**: On **first use**, if helpful, open with 1-2 sentences on what this skill covers and why it matters, then provide the main output. On **subsequent use** or when the user asks to skip, go directly to the main output.

## Initial Assessment

**Check for project context first:** If `.claude/project-context.md` or `.cursor/project-context.md` exists, read it for content themes and audience.

Identify:
1. **Content types**: Blog, guides, webinars, templates, tools (or standalone /tools; see **tools-page-generator**)
2. **Audience**: Buyers, users, both
3. **Funnel stage**: Top, middle, bottom

## Best Practices

### Purpose

- **Help buyers buy**: Content that supports decision-making
- **Help users succeed**: How-to, best practices
- **SEO**: Organize for discoverability and topical authority

### Structure

| Element | Purpose |
|---------|---------|
| **Categories** | By topic, format, or funnel stage |
| **Filters** | Format (blog, guide, video), topic, date |
| **Featured** | Highlight key assets |
| **Search** | Help users find specific content |
| **Contextual embeds** | Resource tiles on product pages |

### Navigation

- **Visible**: Resources in main nav or top-level section
- **Not buried**: Higher than content hubs in hierarchy
- **Clear labels**: "Resources," "Learn," "Content Library"

### Organization

- **Avoid junk drawer**: Intentional structure; not a catch-all
- **Logical hierarchy**: Folders, tags, categories
- **Internal linking**: Connect related content

### Integration

- **Product pages**: Embed relevant resources (streams, tiles)
- **Landing pages**: Lead magnet (ebook, template) or webinar as resource; LP exchanges value for email
- **Blog**: Part of resources or separate with cross-links
- **Glossary**: Link from resources

## Tools Integration

- **Standalone /tools**: When many free tools; use **tools-page-generator**; toolkit hub + per-tool pages
- **Resources section**: When few tools; embed tool cards in resources hub

## Output Format

- **Structure** (categories, filters)
- **Navigation** placement
- **Content** types to include
- **Internal linking** strategy
- **SEO** metadata

## Related Skills

- **card**: Resource card structure; thumbnail, title, format, CTA; tiles in hub
- **grid**: Resource hub grid layout; tiles
- **tools-page-generator**: Standalone /tools when many free tools; toolkit hub

- **landing-page-generator**: Lead magnet (ebook, webinar) as LP offer; LP exchanges resource for email
- **url-slug-generator**: URL slug for resource pages (e.g. /resources/guide-slug); 3-5 words
- **blog-page-generator**: Blog may be part of resources
- **glossary-page-generator**: Glossary as resource
- **tools-page-generator**: Standalone /tools when many free tools; toolkit hub
- **content-strategy**: Content hub strategy
- **internal-links**: Resource page linking

---
name: glossary-page-generator
description: When the user wants to create, optimize, or audit glossary page content and structure. Also use when the user mentions "glossary," "definitions," "terminology," "industry terms," "glossary page," "term definitions," "vocabulary," "glossary SEO," or "definition page." For definitions at scale, use programmatic-seo.
metadata:
  version: 1.0.1
---

# Pages: Glossary

Guides glossary page structure, content, and internal linking for SEO.

**When invoking**: On **first use**, if helpful, open with 1-2 sentences on what this skill covers and why it matters, then provide the main output. On **subsequent use** or when the user asks to skip, go directly to the main output.

## Initial Assessment

**Check for project context first:** If `.claude/project-context.md` or `.cursor/project-context.md` exists, read it for industry terms and customer language.

Identify:
1. **Domain**: SEO, marketing, tech, industry-specific
2. **Audience**: Beginners, practitioners, both
3. **Content volume**: Number of terms

## Best Practices

### Structure

| Element | Purpose |
|---------|---------|
| **Alphabetical index** | A-Z or by category |
| **Term + definition** | Clear, concise explanation |
| **Related terms** | Cross-links within glossary |
| **Internal links** | Link to relevant blog/content |
| **Search** | Help users find terms |

### Definition Quality

- **Clear**: Jargon-free where possible
- **Concise**: One paragraph typical
- **Context**: How term is used in your domain
- **Examples**: When helpful

### Internal Linking Strategy

- **Anchor text**: Descriptive, keyword-rich; avoid "click here"
- **Variation**: Mix anchor phrases; don't repeat identical text
- **Placement**: Higher on page = more valuable
- **Relevance**: Link to most valuable next content
- **Avoid orphans**: Ensure every term page has inbound links

### SEO Benefits

- **Topic clusters**: Glossary as hub; links to and from pillar content; see **content-strategy**
- **Long-tail**: Definition queries, "what is X"
- **Crawlability**: Reduces depth; distributes authority
- **User engagement**: Helps users understand; keeps them on site

### Maintenance

- **New terms**: Add as content expands
- **Audit links**: Periodically check internal links
- **Update**: Keep definitions current

## Output Format

- **Structure** (index, layout)
- **Term** template (definition format)
- **Internal linking** plan
- **SEO** metadata
- **Schema**: DefinedTerm or similar if applicable

## Related Skills

- **url-slug-generator**: URL slug for glossary terms (e.g. /glossary/term-slug); 3-5 words
- **internal-links**: Glossary is internal linking hub
- **content-strategy**: Glossary supports content clusters
- **blog-page-generator**: Link between glossary and blog
- **title-tag, meta-description, page-metadata**: Glossary page metadata

---
name: features-page-generator
description: When the user wants to create, optimize, or audit features page content. Also use when the user mentions "features page," "product features," "capabilities," "what it does," "feature list," "feature comparison," "product capabilities," or "features section." For sitewide page planning, use website-structure.
metadata:
  version: 1.1.1
---

# Pages: Features

Guides features page content, structure, and conversion optimization.

**When invoking**: On **first use**, if helpful, open with 1-2 sentences on what this skill covers and why it matters, then provide the main output. On **subsequent use** or when the user asks to skip, go directly to the main output.

## Initial Assessment

**Check for project context first:** If `.claude/project-context.md` or `.cursor/project-context.md` exists, read it for product, differentiation, and proof points.

Identify:
1. **Feature set**: Core features, differentiators
2. **Audience**: Who evaluates features (buyer persona)
3. **Format**: Single page vs. per-feature pages
4. **Primary goal**: Demo, sign up, learn more

## Features Page Structure

| Section | Purpose |
|---------|---------|
| **Headline** | Benefit-led; "Everything you need to..." |
| **Feature grid/list** | Each feature: name, benefit, optional screenshot |
| **Use case links** | "For marketers," "For developers" |
| **Social proof** | Testimonials, logos |
| **CTA** | Try free, see demo, contact |

## Best Practices

### Benefit-First

- **Lead with benefit**: "Save 10 hours/week" not "Automated reporting"
- **Customer outcome**: What they get, not what it does
- **Specificity**: Numbers, examples, not vague claims

### Organization

- **By capability**: Group by product area or capability (e.g., Analytics, Automation, Integrations) — avoid organizing by use case to prevent overlap with use cases pages
- **By priority**: Most important/differentiating first
- **By journey**: Discovery -> evaluation -> decision

### Per-Feature Pages

- Use when features are substantial or rank separately
- Each page: feature name, benefit, how it works, proof
- Internal link from main features page

## SEO

- Title: "Features | [Product]" or "[Feature] | [Product]"
- H1: Main value; H2 per feature or section
- Schema: SoftwareApplication if applicable
- Internal links: To pricing, use cases, blog

### Avoid Overlap with Use Cases

- **Features = What**: Capability + benefit; no scenario narratives. Do not write "When you need to X..." — that belongs on use cases pages.
- **Link, don't duplicate**: Use "Use case links" (e.g., "For marketers," "For developers") to send users to use cases pages; do not replicate scenario content.
- **Content cannibalization**: Both target Commercial/Consideration; differentiate by angle (capability vs scenario) so each page serves unique intent.

## Output Format

- **Feature list** with benefit-first copy
- **Structure** (sections, order)
- **Headline** options
- **Per-feature** content (if separate pages)
- **SEO** metadata and schema

### vs. Tools

| Page | Purpose | Monetization |
|------|---------|--------------|
| **Features** | Paid product capabilities; conversion | Primary revenue |
| **Tools** | Free utilities; lead gen; excerpt from product | Not primary; drives signups |

See **tools-page-generator** for free tools pages.

## Related Skills

- **card**: Feature card structure; name, benefit, screenshot; grid/list layout
- **grid, list**: Feature grid or list layout
- **tools-page-generator**: Tools = free lead gen; features = paid capabilities; link from tools to product/features
- **use-cases-page-generator**: Features = what it does; use cases = when/how to use it; link between; avoid duplicating scenario content on features page
- **landing-page-generator**: Features content for product LP "Explain value" step; product LP links to features
- **url-slug-generator**: URL slug for per-feature pages (e.g. /features/feature-name); 3-5 words
- **homepage-generator**: Homepage links to features
- **pricing-page-generator**: Features inform plan tiers
- **schema-markup**: SoftwareApplication schema
- **heading-structure**: Feature page heading structure

---
name: faq-page-generator
description: When the user wants to create, optimize, or audit FAQ page content. Also use when the user mentions "FAQ page," "frequently asked questions," "help page," "Q&A page," "FAQ schema," "FAQ section," "common questions," "FAQ SEO," "accordion FAQ," "People Also Ask," "PAA," "People Also Search For," "PASF," or "FAQ rich results." For FAQ structured data markup, use schema-markup. For AI search visibility strategy, use generative-engine-optimization.
metadata:
  version: 1.2.0
---

# Pages: FAQ

Guides FAQ page content, structure, and optimization for SEO, conversion, and rich results (PAA, Featured Snippet, GEO, PASF). FAQ content from real user questions and rich-result targeting.

**When invoking**: On **first use**, if helpful, open with 1-2 sentences on what this skill covers and why it matters, then provide the main output. On **subsequent use** or when the user asks to skip, go directly to the main output.

## FAQ and Rich Results

| Feature | Relationship | Optimization |
|---------|--------------|---------------|
| **People Also Ask (PAA)** | FAQ schema triggers PAA-style dropdowns; PAA questions = FAQ source | FAQPage schema; match question phrasing; "how/what/why" format. PAA ~51% of searches. See **serp-features** |
| **Featured Snippet** | Answers extracted for position zero | 40-60 words; answer-first; H2/H3; paragraph (70%), list (19%), table (6%). See **featured-snippet** |
| **GEO / AI Overviews** | AI cites FAQ blocks; FAQ most cited content type (3-7x more citations) | Self-contained; 40-80 words; entity signals; content in initial HTML. See **geo** |
| **People Also Search For (PASF)** | Appears when user bounces; comprehensive FAQ reduces bounce | Match intent; cover related questions. PASF shows 6-8 related queries. |
| **FAQ rich result** | FAQPage schema; max 2 dropdowns per SERP | Restricted to government/health in many regions; schema still helps PAA, voice, AI |

**PAA vs PASF**: PAA = expandable question boxes (same SERP). PASF = related queries after bounce. Both benefit from comprehensive, intent-matching content.

## Content Sources

**Real user**: Support tickets, chat logs, sales objections, surveys, reviews.

**Rich-result purpose**: PAA (search keyword, extract questions), AnswerThePublic, AlsoAsked, Featured Snippet queries, competitor FAQ, keyword research, GEO citation data.

**Reverse flow**: Use PAA, Featured Snippet, GSC Search queries to find questions you rank for but don't answer.

## Content Structure

| Approach | When | Example |
|----------|------|---------|
| **Page topic** | In-page section | 3-8 questions about that page |
| **Theme** | Dedicated page | Group by Billing, Features, Support, Compliance |
| **Logical flow** | Decision funnel | Awareness -> Consideration -> Purchase -> Support |
| **Objection handling** | Conversion | "Is it worth it?" "Can I cancel?" |

**Page-specific**: LP (objection handling); pricing (billing, plans, enterprise); alternatives (migration, comparison); category (materials, recommendations); tools (what is X, how calculated). See **landing-page-generator**, **pricing-page-generator**, **alternatives-page-generator**, **category-pages**, **tools-page-generator**.

## Dedicated FAQ Page vs In-Page FAQ Section

| Dimension | Dedicated Page | In-Page Section |
|-----------|----------------|-----------------|
| **Placement** | /faq, /help, standalone URL | Within LP, pricing, blog, product page |
| **Count** | 5-30 (5-10 optimal) | 3-8 |
| **Structure** | Categories, TOC, navigation | Inline; after main content |
| **Schema** | One FAQPage per page | Same; schema matches visible Q&A |
| **When to use** | Many questions; support/help hub; central FAQ | Objection handling; page-specific long-tail; conversion |
| **Related pages** | contact-page, docs-page, website-structure | landing-page, pricing-page, blog, alternatives, category-pages, tools-page |

**Shared rules**: Word count, content rules, format, and schema apply to both. Choose placement based on question volume and page purpose.

## Accordion: Crawlable?

**Yes.** Google indexes accordion content fully; hidden content receives full weight.

**Requirements**: Content in DOM at load (no AJAX on click); use `<details>`/`<summary>` or server-rendered HTML; first item expanded. Avoid `display: none` for primary content. See **tab-accordion**, **rendering-strategies**.

**Nuance**: Some tests suggest visible content outperforms hidden. Use accordion for secondary FAQ; keep primary Q&A visible.

## Best Practices

### Word Count

| Element | Range | Notes |
|---------|-------|------|
| **Answer** | 40-80 words | Sweet spot for AI; under 40 = incomplete; over 80 = cut off |
| **Featured Snippet** | 40-60 words | 45 words most common |
| **First sentence** | 40-50 words | Answer immediately |
| **Sentences** | 2-4 | Standalone, comprehensive |

### Content Rules

- **Genuine questions**: PAA, AnswerThePublic, support; no invented marketing questions
- **Standalone answers**: Each answer makes sense alone; AI extracts individual pairs
- **Content parity**: Schema must exactly match visible content; hidden schema = violation
- **No duplicates**: Each Q&A on one page; choose most authoritative
- **Topical focus**: FAQs match page topic
- **Inverted pyramid**: Most important first; data, numbers, actionable advice
- **Keywords**: 1-2 times naturally; no stuffing
- **Quality over quantity**: 5-10 excellent beat 50 thin
- **Update quarterly**: Add questions from emerging trends

### Format

- **Schema**: JSON-LD; one FAQPage per page
- **Answer HTML** (in schema `text`): `<a>`, `<strong>`, `<em>`, `<p>`, `<br>`, `<ol>`; use sparingly
- **Structure**: H2/H3 per question; semantic HTML; answer-first under heading
- **Validation**: Google Rich Results Test, Schema.org Validator, GSC

### Number of Questions

| Placement | Count | Notes |
|-----------|-------|------|
| **In-page section** | 3-8 | Directly related to page |
| **Dedicated page** | 5-10 optimal | 10-30 if well-crafted; quality over quantity |
| **Schema minimum** | 2+ | Single Q&A rarely shown |
| **Google display** | Max 2 per result | See **serp-features** |

### Question and Answer

**Question**: Match how users ask ("How do I return?" not "Return Policy"); target "how/what/why"; H2/H3; avoid promotional or invented.

**Answer**: Answer-first in 40-60 words; paragraph, list, or table by content type; scannable (bullets, bold); self-contained; entity signals. See **entity-seo**.

### Organization

Group by topic; clear hierarchy; TOC, accordions, jump links; audit quarterly.

## Initial Assessment

**Check project context** (`.cursor/project-context.md` or `.claude/project-context.md`) for objections, product details, customer language.

Identify: (1) Source of questions (2) Conversion focus (3) Placement (dedicated vs in-page).

## Why It Matters

- Reduces support load
- Long-tail and voice search
- Category pages: +157% conversion when FAQ used
- 20-30% CTR lift when rich results display
- 3-7x more AI citations with optimized FAQ

## Output Format

- Question list (from research)
- Category structure
- Answer format and tone
- Schema (FAQPage)
- SEO metadata

## Related Skills

- **tab-accordion**: Accordion implementation; details/summary
- **serp-features**: PAA, Featured Snippet, PASF, FAQ limits
- **featured-snippet**: Answer length, position zero
- **geo**: GEO strategy; citable blocks; AI crawlers
- **schema-markup**: FAQPage implementation
- **keyword-research**: PAA to FAQ; question keywords
- **landing-page-generator**, **pricing-page-generator**, **alternatives-page-generator**, **category-pages**, **tools-page-generator**: In-page FAQ section
- **contact-page-generator**, **docs-page-generator**, **website-structure**: Dedicated FAQ page; FAQ reduces contact form volume
- **title-tag, meta-description, page-metadata**: Metadata
- **entity-seo**: Entity signals for GEO
- **rendering-strategies**: Content in initial HTML

---
name: docs-page-generator
description: When the user wants to create, optimize, or structure a documentation site. Also use when the user mentions "docs," "documentation site," "docs subdomain," "docs.yourdomain.com," "help center," "knowledge base," "Getting Started," "API Reference," "user guides," or "tutorials." For API marketing landing, use api-page-generator.
metadata:
  version: 1.0.1
---

# Pages: Documentation Site

Guides documentation site structure, navigation, and content organization. Typically hosted on `docs.*` or `help.*` subdomain. Includes Getting Started, guides, tutorials, **API Reference** (endpoint docs), and troubleshooting. Distinct from API introduction page (api-page-generator).

**When invoking**: On **first use**, if helpful, open with 1–2 sentences on what this skill covers and why it matters, then provide the main output. On **subsequent use** or when the user asks to skip, go directly to the main output.

## Initial Assessment

**Check for project context first:** If `.claude/project-context.md` or `.cursor/project-context.md` exists, read it for product, audience, and use cases.

Identify:
1. **Product type**: Software, API, hardware, service
2. **Audience**: End users, developers, admins
3. **Content sources**: Markdown, MDX, Git, CMS
4. **Subdomain**: docs.*, help.*, or path (/docs)

## Documentation Structure

| Section | Purpose | Typical Content |
|---------|---------|-----------------|
| **Getting Started** | Onboarding, first steps | Quick start, installation, first task |
| **Guides / Tutorials** | Step-by-step learning | How-to articles, workflows |
| **Concepts** | Background, architecture | Key concepts, glossary links |
| **API Reference** | Endpoint docs | Auth, request/response, examples; part of docs, not separate page |
| **Troubleshooting** | Problem solving | FAQ, common errors, support links |

## Best Practices

### Information Architecture

- **Progressive disclosure**: Start simple, link to depth
- **Sidebar navigation**: Hierarchical, collapsible sections
- **Search**: Full-text search for long doc sets
- **Breadcrumbs**: For deep hierarchies

### API Reference (within Docs)

API Reference is a section of docs, not a standalone page. Include: endpoints by resource, auth, request/response schemas, error codes, rate limits, code examples (cURL, SDKs). Use OpenAPI/Swagger for consistency.

### Content

- **Task-oriented**: "How to X" not "X feature"
- **Code examples**: Copy-paste ready, multiple languages if relevant
- **Screenshots/videos**: For UI-heavy products
- **Versioning**: Document product/API version when applicable

### SEO and Discovery

- **Index docs**: Unless internal-only; use robots if needed
- **Internal links**: Cross-link related articles, link to main site
- **Schema**: TechArticle, HowTo for guides

## Output Format

- **Structure** (sections, hierarchy)
- **Navigation** design (sidebar, top-level)
- **Getting Started** outline
- **Content** checklist per section
- **Subdomain/path** recommendation

## Related Skills

- **api-page-generator**: API intro page links to docs
- **sidebar-generator**: Docs sidebar design
- **faq-page-generator**: FAQ can live in docs or main site
- **content-strategy**: Doc content planning

---
name: blog-page-generator
description: When the user wants to create, optimize, or audit blog index or listing page structure (not a single post). Also use when the user mentions "blog page," "blog index," "blog layout," "content hub," "blog homepage," "blog listing," "subdomain vs subdirectory," "blog structure," or "blog SEO." For single post page SEO and schema, use article-page-generator.
metadata:
  version: 1.1.0
---

# Pages: Blog

Guides blog page structure, SEO, and content marketing best practices.

**When invoking**: On **first use**, if helpful, open with 1-2 sentences on what this skill covers and why it matters, then provide the main output. On **subsequent use** or when the user asks to skip, go directly to the main output.

## Initial Assessment

**Check for project context first:** If `.claude/project-context.md` or `.cursor/project-context.md` exists, read it for topics, audience, and keywords.

Identify:
1. **Blog purpose**: SEO traffic, thought leadership, product education
2. **Content mix**: Pillar pages, cluster content, news
3. **Audience**: Buyers, existing customers, developers

## Best Practices

### Blog Placement: Subdomain vs Subdirectory

| Option | Example | SEO / Use |
|--------|---------|-----------|
| **Subdirectory** | `example.com/blog` | SEO weight flows to main domain; recommended for product blogs |
| **Subdomain** | `blog.example.com` | Treated as separate entity; consider for distinct brands or technical isolation |

Choose based on SEO weight distribution, brand consistency, and technical architecture. See [Alignify subdomain vs subdirectory guide](https://alignify.co/zh/seo/create-blog) for details.

### Blog Index Page Structure

| Section | Purpose |
|---------|---------|
| **Featured/Recent** | Highlight newest or most important posts |
| **Categories/Topics** | Help users find by theme |
| **Editor's Picks** | Curate best content |
| **Related posts** | Per-article recommendations |
| **Search** | Help users find specific topics |

### Content Strategy

- **Topical authority**: Topic clusters -> pillar page per core topic + 6-12 cluster articles
- **Intent mapping**: Transactional, problem-aware, informational
- **EEAT signals**: Author bios, Organization schema, citations, changelog
- **Refresh > new**: For established sites, updating existing content often outperforms publishing new posts; avoid changing only the date without substantive edits
- **Quality > quantity**: Fewer high-quality posts beat many mediocre ones; consider deleting, merging, or refreshing underperformers
- **Topic focus**: Avoid blindly expanding topics; dilution can hurt authority on core topics
- **Conversion as north star**: SEO KPIs should tie to leads, signups, or sales -> not just traffic

### SEO

- **Title**: 55 chars, power words, primary keyword
- **Meta**: Clear CTA in description
- **Headers**: H1-H3 hierarchy, table of contents
- **Content depth**: 2,500+ words for pillars; Grade 8 readability
- **URL**: Use **url-slug-generator** -> clean slugs, 3-5 words, under 60 chars
- **Schema**: Article, BlogPosting, FAQPage where relevant

### Technical

- **Core Web Vitals**: LCP < 1.0s on mobile
- **Images**: WebP, compressed
- **IndexNow**: For fast indexing of new posts

### Design

- **Scannable**: Preview copy, thumbnails, hero images
- **Social sharing**: Share buttons on article pages -> see **social-share-generator**
- **Quick answers**: Definition boxes, mini-FAQs for AEO
- **TOC**: Table of contents for Featured Snippets; jump links in long articles; see **featured-snippet**, **toc-generator**
- **CTA placement**: Sidebar CTA or in-paragraph CTA at key conversion points
- **Related/Recent posts**: Manual curation or plugin; same topic cluster

## Output Format

- **Structure** for blog index and post template
- **Content** strategy (pillar + clusters)
- **SEO** metadata and schema
- **Internal linking** approach

## Related Skills

- **card**: Article card structure for blog index; cover image, title, excerpt, date
- **grid, list**: Grid for visual; list for text-heavy blog index
- **article-page-generator**: Single article/post page structure, SEO, schema -> use for individual post templates
- **featured-snippet**: TOC, answer-first format for snippet opportunities
- **url-slug-generator**: URL slug for blog posts; 3-5 words, primary keyword
- **content-strategy**: Content clusters, editorial calendar
- **keyword-research**: Keywords for blog topics
- **title-tag, meta-description, page-metadata, open-graph, twitter-cards**: Blog metadata and social previews
- **schema-markup**: Article schema
- **resources-page-generator**: Blog may be part of resources hub

---
name: article-page-generator
description: When the user wants to create, optimize, or audit a single article/post page (not the blog index). Also use when the user mentions "article page," "blog post page," "single post," "post template," "article structure," "post optimization," "competitor article analysis," "optimize based on top-ranking articles," "analyze ranking articles," "optimize article for SEO," or "article schema." For writing article body copy, use article-content. For blog listing/index page, use blog-page-generator.
metadata:
  version: 1.3.0
---

# Pages: Article (Single Post)

Guides **structure, SEO, and UX** for individual article pages — layout, metadata, schema, technical. For **article body content** (intro, body, conclusion, writing), see **article-content**. Distinct from **blog-page-generator**, which covers the blog index/listing page.

**When invoking**: On **first use**, if helpful, open with 1–2 sentences on what this skill covers and why it matters, then provide the main output. On **subsequent use** or when the user asks to skip, go directly to the main output.

**Output workflow**: Always output in order: **0. Research Phase** (keywords, search intent, competitors) → **1. Intent Analysis** → **2. Content Analysis** → **3. Recommendations**. Do not skip steps. When Research Phase was performed via web search, show the search results and findings.

## Optimization Foundation: Four Inputs

Article analysis and creation rest on **four inputs**. Gather or infer them before outputting recommendations:

| Input | Purpose | Source |
|-------|---------|--------|
| **Product** | Product connection, features, use cases, CTA placement | project-context (Sections 1–4, 9–11); article content; web search |
| **Keywords** | Target keyword, primary/secondary placement | project-context Section 6; keyword-research; article |
| **Article intent** | Informational, commercial, transactional, navigational; drives structure, CTA, SEO depth | project-context Section 6 (target intent); article orientation; content type |
| **Competitor articles** | Structure to adopt, content gaps, length target, keyword opportunities | User-provided URLs; project-context Section 11; web search |

**When any input is missing**: Proactively ask or search. For article analysis: perform **Research Phase** (keyword search, search intent, competitor articles) by default — see Research Phase section. For product/keywords/intent, infer from article or prompt user to add project-context.

## Before Analysis: Gather Context

**1. Product / company context**

Use available context to give **tailored** analysis:

| Source | Use for |
|--------|---------|
| **project-context.md** | Keywords (Section 6), competitors (Section 7), content strategy (Section 11), product connection |
| **Article content** | Extract product name, features, URLs; infer target keyword and audience |
| **Web search** | When analyzing a known brand: search for "[product] features", "[product] vs competitors", company positioning — use to validate product connection, suggest missing features/use cases, and improve competitor gap analysis |

If no project-context exists, infer from the article and optionally search for company/product info to enrich recommendations.

## Research Phase: Keyword, Search Intent, Competitor (Required for Article Analysis)

**Lightweight** research for article analysis. When **analyzing or auditing** an article, perform searches and **output the results** in Section 0. Skip only if user explicitly asks to skip (e.g. "skip search").

- **Keyword**: Extract from article (title, H1, H2s, first 100 words); search for opportunities — see **keyword-research** (extract from article method)
- **Search intent**: Informational / Commercial / Transactional / Navigational — see **keyword-research** Search Intent
- **Competitor articles**: Fetch 2–3 top-ranking pages; analyze structure, gaps, length target — see **competitor-research** (Competitor Article Fetch Workflow)

**Output format**: See Output Format Section 0 below.

## Scope

- **Single article page**: One post, one URL (e.g. `/blog/how-to-optimize-seo`)
- **Not** the blog index, category pages, or archive pages — see **blog-page-generator** for those

## Initial Assessment

**Check for project context first:** If `.claude/project-context.md` or `.cursor/project-context.md` exists, read it for topics, audience, keywords, and Section 11 (Content/Blog/Article Strategy).

Identify:
1. **Product connection**: How does this article support the product? (educate on problem, introduce features, nurture leads)
2. **Keyword basis**: Target keyword from product context or keyword research — see **keyword-research**
3. **Content type**: Blog post, guide, tutorial, news, evergreen
4. **Length**: Short (<1,000 words), medium (1,000–2,500), long (2,500+)
5. **Intent**: Informational, commercial, problem-aware

**Product-linked content**: Articles should tie to the product (problem it solves, features, use cases). Avoid purely generic content with no product relevance. Link to product/feature pages naturally in conclusion or when context fits.

## Article Orientations

Choose structure, SEO depth, and schema based on **orientation**. See **content-marketing** for full Article Orientations (Funding/PR, Product update, Guide, News, Evergreen), SEO-driven vs non-SEO-driven, Evergreen vs Timely.

**Intent Analysis output**: Orientation, primary goal, SEO vs non-SEO, Evergreen vs timely — see Output Format Section 1.

## Article Page Structure

| Section | Purpose |
|---------|---------|
| **Hero/Header** | Title (H1), author, **single date** (see **schema-markup** Date display for CTR), **reading time** (word count ÷ 200; round up), featured image, **share buttons** |
| **TL;DR or Key Takeaways** | See **article-content** for content; placed after intro; supports GEO/AI citation |
| **Introduction** | See **article-content** for hook, length, keyword placement |
| **Body** | See **article-content** for QAE, paragraph length, scannability |
| **Conclusion** | See **article-content** for summary, CTA, product connection |
| **Related posts** | 3–6 contextual links; end-of-article recommendations |
| **Author bio** | E-E-A-T; credentials, photo, link to author page — see **eeat-signals** |

### Featured Image

See **image-optimization** (Article / Blog hero). Same image for Schema, Open Graph, Twitter Cards; min 1200px wide, absolute URL. See **open-graph**, **twitter-cards**.

### Social Sharing

- Add **share buttons** (X, LinkedIn, Facebook, etc.) — see **social-share-generator**
- Place after intro and/or end of article; sticky sidebar for long-form
- Requires **Open Graph** and **Twitter Cards** for rich previews when shared

### GEO / AI Optimization

See **article-content** for TL;DR, Key Takeaways, QAE pattern, answer-first; **generative-engine-optimization** for full GEO strategy.

### Long-Form (1,000+ words)

- Add **table of contents** (TOC) after intro — see **toc-generator**
- Use jump links for major sections
- Break text with images, lists, definition boxes, mini-FAQs

## SEO Best Practices

### Title & Meta

| Element | Guideline |
|---------|-----------|
| **Title** | 55 chars; primary keyword near start; power words |
| **Meta description** | 150–160 chars; CTA; primary keyword |
| **H1** | One per page; matches title; primary keyword naturally |

### Keyword Placement

- **Title**: 1× primary keyword
- **First 100 words**: 1× primary keyword
- **Body**: 2–3× naturally; avoid stuffing
- **At least one H2**: Include primary or related keyword

### Content Quality

See **article-content** for readability, depth, originality, word count by type. **E-E-A-T**: Author bio, citations, changelog, expert quotes — see **eeat-signals**.

### Common Mistakes to Avoid

- Multiple H1s; skipping heading levels (H2→H4); keyword stuffing in headings
- Neglecting conclusion or CTA; no internal links to related content
- Walls of text; generic "click here" anchors

### URL

Use **url-slug-generator** for slug creation. Key rules:

- **Slug**: 3–5 words; under 60 chars; primary keyword; lowercase, hyphens
- **Example**: `/blog/ai-people-search` not `/blog/ai-search-engine-finding-people-speed-discovery-outreach`
- **Avoid**: Date in path (`/blog/2025/01/15/article-title`); copy-pasting full title

### Date Display

See **schema-markup** (Date display for CTR): show only one visible date; prefer dateModified.

## Schema & Open Graph

See **schema-markup** for Article/BlogPosting/NewsArticle type selection, required properties, JSON-LD example, and date display. Validate with [Rich Results Test](https://search.google.com/test/rich-results).

## Open Graph for Articles

Use `og:type: article` for article pages (not `website`):

```html
<meta property="og:type" content="article">
<meta property="og:article:published_time" content="2025-01-15T09:00:00Z">
<meta property="og:article:modified_time" content="2025-02-01T14:30:00Z">
<meta property="og:article:author" content="https://example.com/author/jane">
```

## Internal Linking

| Element | Guideline |
|---------|-----------|
| **Volume** | 3–5 contextual links in body + 3–6 in Related posts = 6–11 total per article |
| **First paragraph** | 1 link to pillar or key related content |
| **Body** | 2–4 contextual links; one per major section when relevant |
| **Related posts** | 3–6 end-of-article links; same topic cluster |
| **Anchor text** | Descriptive (e.g. "SEO checklist for 2025", "how to optimize meta tags"); avoid "click here", "learn more", "read more" |
| **Variation** | Mix exact-match, partial-match, branded anchors; avoid over-optimization |
| **Orphan prevention** | Every article has ≥1 internal link from hub/pillar or nav |

## Outbound Links (External)

| Element | Guideline |
|---------|-----------|
| **Volume** | 2–5 external links per article; cite authoritative sources |
| **When to use** | Statistics, research, definitions, tool comparisons, expert quotes |
| **Anchor text** | Descriptive (e.g. "Google's Search Quality Guidelines", "SEO study"); link to source |
| **Same URL** | Counts once per page for link equity; no need to repeat |
| **E-E-A-T** | External links to reputable sources signal trust — see **eeat-signals** |

## References / Citations

See **article-content** for citation format; **eeat-signals** for E-E-A-T and when to include.

## AI-Assisted Content

See **article-content** for AI-assisted content guidance; **eeat-signals** for E-E-A-T.

## Technical

- **Core Web Vitals**: LCP < 1.0s on mobile
- **Images**: WebP, compressed; descriptive alt text; keyword in filename when natural
- **IndexNow**: For fast indexing of new posts
- **Canonical**: Self-referencing canonical on article page

## Post-Publication

- **Refresh**: Update every 6–12 months; refresh stats, add insights
- **Internal links**: Add links from older posts to new articles
- **Monitor**: GSC indexing, rankings, Core Web Vitals

## Content Analysis

When auditing or optimizing an article, apply the Content Audit Checklist. See **article-content** for full dimensions.

## Output Format

### 0. Research Phase (output first, when analysis/audit is performed)

When analyzing or auditing an article, output this section **before** Intent Analysis. Include search sources and findings. If user asked to skip search, note that and infer from article only.

| Section | Output |
|--------|--------|
| **Keyword Search** | Primary keyword (from article or search), secondary keywords, keyword opportunities (from SERP/competitor analysis). If search was performed: query used, top results observed. |
| **Search Intent** | Intent for primary keyword (Informational/Commercial/Transactional/Navigational), intent for 2–3 secondary keywords, whether article content matches intent. If search was performed: SERP snippet types observed. |
| **Competitor Articles** | If searched: 2–3 URLs, brief structure (word count, H2s), content gaps, length target. If user provided URLs: same. See **competitor-research** for full methodology. If skipped: "Competitor analysis skipped." |

### 1. Intent Analysis (output second)

Before any recommendations, output a brief analysis:

| Dimension | Output |
|-----------|--------|
| **Orientation** | Funding/PR, Product update, Guide, News, Evergreen |
| **Primary goal** | Brand, PR, education, product adoption, organic traffic, … |
| **SEO vs non-SEO** | SEO-driven / Non-SEO-driven / Hybrid |
| **Evergreen vs timely** | Evergreen / Timely |
| **Implications** | 1–2 sentences: e.g. "Low SEO priority → focus on clarity, shareability" or "SEO-driven → full keyword + GEO optimization" |

### 2. Content Analysis (output third)

Apply the Content Analysis table above. Output a brief assessment per dimension (✅ / ⚠️ / ❌ + one-line note).

### 3. Recommendations (output fourth, tailored to intent)

Assign **priority** to each item: **P0** (critical), **P1** (high), **P2** (medium), **P3** (nice-to-have). Output as table or list with priority prefix.

| Priority | Use when |
|----------|----------|
| **P0** | Blocks GEO/SEO; missing core element (TL;DR or Key Takeaways, keyword in first 100 words, schema) |
| **P1** | Significant impact on traffic, CTR, or conversion (title length, share buttons, CTA) |
| **P2** | Improves UX or authority (related posts, author bio, internal links) |
| **P3** | Polish (image optimization, readability tweaks) |

Example: `[P0] Add TL;DR or Key Takeaways — GEO, AI citation`

- **Product connection** (how article supports product; where to link) — see **article-content**
- **Keyword** (target from product context or keyword research)
- **Structure** for article template (hero, TL;DR or Key Takeaways, intro, body, conclusion, related, author) — content creation: **article-content**
- **Featured image** (dimensions, alt, file size, og:image alignment)
- **GEO** elements (TL;DR or Key Takeaways, QAE pattern) — *skip or minimal for non-SEO-driven*
- **SEO** checklist (title, meta, H1, keyword placement) — *skip or minimal for non-SEO-driven*
- **Schema** type and JSON-LD
- **Internal links** (3–5 in body + 3–6 Related; anchor text suggestions; avoid "click here")
- **Outbound links** (2–5 external; cite stats, research; anchor text for each)
- **References** (inline citations vs Reference section; when to add for E-E-A-T)
- **Competitor analysis** (when URLs provided or searched): content gaps vs top rankers, structure to adopt, length target, keyword opportunities — see **competitor-research** for methodology; **Before Analysis** to prompt user or search

## Related Skills

- **article-content**: Article body creation; intro, body, conclusion; writing frameworks; Content Audit Checklist
- **eeat-signals**: E-E-A-T; author bio, citations, YMYL
- **competitor-research**: Content gaps, structure, length target
- **blog-page-generator**: Blog index/listing; article pages live within blog
- **keyword-research**: Keyword basis for articles
- **schema-markup**: Article/BlogPosting/NewsArticle schema
- **heading-structure**: H1–H6 structure for article body
- **content-optimization**: H2 keywords, tables, lists, multimedia; word count for articles → **article-content**
- **image-optimization**: Article hero/featured image specs
- **internal-links**: Related posts, contextual links
- **open-graph, twitter-cards**: Social previews for articles
- **generative-engine-optimization**: GEO strategy; AI citation optimization