blog-strategy
Blog strategy development including topic cluster architecture with hub-and-spoke design, audience mapping, competitive landscape analysis, AI citation surface strategy across ChatGPT/Perplexity/AI Overviews, distribution channel planning (YouTube, Reddit, review platforms for GEO), content scoring targets, measurement framework, and content differentiation through original research and first-hand experience. Use when user says "blog strategy", "content strategy", "blog positioning", "what should I blog about", "blog topics", "content pillars", "blog ideation".
What this skill does
# Blog Strategy: Positioning & Content Architecture
Develops comprehensive blog strategies that build topical authority for
Google rankings while establishing brand presence for AI citation platforms.
Includes topic cluster architecture, AI citation surface strategy, content
scoring targets, and GEO-specific optimization plans.
**Research discipline references (v1.8.0)**:
- `skills/blog/references/research-quality.md` - 5-dim rubric, pre-flight trap classes, cross-source clustering, freshness floors
- `skills/blog/references/synthesis-contract.md` - 6 LAWs for synthesis output
**Auto-loaded inputs (v1.8.0)**: when `DISCOURSE.md` exists at the project root (from `/blog discourse`), load it for cross-platform discourse signal alongside this skill's authority-source planning.
## Cross-reference
Strategy planning should consider the FLOW 5-surface model (owned site, SERP plus AI Overviews, AI assistant citations, local pack, communities and video). Local-pack work is delegated to `claude-seo`; everything else lives inside claude-blog. Full mapping in `skills/blog/references/flow-alignment.md`.
For evidence-led audience-avatar, keyword-research, and content-prioritization prompts that feed strategic planning, see `/blog flow find`.
## Workflow
### Step 1: Discovery
Gather context through questions or project analysis:
1. **Business**: What do you sell/do? Who are your customers?
2. **Blog goals**: Traffic? Leads? Authority? AI citations?
3. **Current state**: Existing blog content? (scan if project available)
4. **Competitors**: Who are your 3-5 main competitors?
5. **Differentiator**: What unique expertise or data do you have?
6. **Resources**: Writing capacity (posts/week), budget for visuals?
### Step 2: Competitive Landscape
Research competitors' blogs:
1. WebSearch for competitor blog URLs
2. For each competitor, assess:
- Publishing frequency
- Content types (guides, case studies, comparisons, news)
- Visual quality (images, charts, videos)
- Schema usage
- Social distribution (YouTube, Reddit, LinkedIn)
- AI citation presence (search ChatGPT/Perplexity for industry terms)
3. Identify gaps no competitor covers well
#### Competitive AI Citation Analysis
Map competitor visibility across AI platforms. Use WebSearch to find how
competitors appear in AI-generated responses for target keywords.
```
## Competitive AI Citation Map
| Query | ChatGPT Cites | Perplexity Cites | AI Overview Cites | Gap? |
|-------|--------------|-----------------|-------------------|------|
| [keyword] | [competitor/none] | [competitor/none] | [competitor/none] | [Yes/No] |
| [keyword] | [competitor/none] | [competitor/none] | [competitor/none] | [Yes/No] |
| [keyword] | [competitor/none] | [competitor/none] | [competitor/none] | [Yes/No] |
```
Score each competitor's AI visibility:
- **High**: Cited in 3/3 platforms for multiple queries
- **Medium**: Cited in 1-2 platforms or for limited queries
- **Low**: Rarely cited, only in niche queries
- **None**: No AI citation presence detected
Identify AI citation gaps: queries where no competitor is cited. These
represent the highest-opportunity targets for new content.
Note: only 12% overlap between platforms. A competitor strong on ChatGPT
may be absent from Perplexity. Analyze each platform independently.
### Step 3: Audience Mapping
Define 2-3 audience segments:
```
### Audience Segment: [Name]
- **Role**: [Job title / description]
- **Pain points**: [What problems do they have?]
- **Search behavior**: [What do they Google?]
- **AI behavior**: [What do they ask ChatGPT/Perplexity?]
- **Content preferences**: [Long guides? Quick answers? Video?]
- **Buying stage**: [Awareness / Consideration / Decision]
```
### Step 4: Content Pillar Design with Topic Cluster Architecture
Design 3-5 content pillars based on audience needs and competitive gaps.
For each pillar, build the full hub-and-spoke cluster model.
```
### Pillar: [Topic Area]
- **Purpose**: Build authority in [topic]
- **Primary keywords**: [3-5 keywords]
- **Content types**: Pillar guide, supporting posts, comparisons, FAQ
- **Unique angle**: [What first-hand experience/data can you provide?]
- **Estimated posts**: [N] to achieve topic coverage
- **AI citation potential**: [High/Medium/Low] - [why]
```
#### Cluster Architecture Design
For each pillar, design the complete hub-and-spoke structure:
```
### Cluster Architecture: [Pillar Topic]
┌──────────────────┐
│ Pillar Page │
│ 3,000-4,000w │
└────────┬─────────┘
│
┌─────────────────┼──────────────────┐
│ │ │
┌──────▼──────┐ ┌─────▼──────┐ ┌───────▼──────┐
│ Spoke #1 │ │ Spoke #2 │ │ Spoke #3 │
│ 1,500-2,500│ │ 1,500-2,500│ │ 1,500-2,500 │
└──────┬──────┘ └─────┬──────┘ └───────┬──────┘
│ │ │
└────────────────┼───────────────────┘
(cross-links between spokes)
```
For each cluster, specify:
- **8-12 spoke topics** per pillar, each targeting a specific long-tail keyword
- **Internal linking plan** between all cluster pages (every spoke links to pillar, pillar links to all spokes, spokes cross-link to related spokes)
- **Content template assignment** for each piece from the 12 available templates:
`how-to-guide`, `listicle`, `case-study`, `comparison`, `pillar-page`,
`product-review`, `thought-leadership`, `roundup`, `tutorial`,
`news-analysis`, `data-research`, `faq-knowledge`
```
### Cluster Build Plan: [Pillar Topic]
| # | Spoke Topic | Template | Target Keyword | Word Count | Internal Links |
|---|------------|----------|---------------|-----------|----------------|
| P | [Pillar title] | pillar-page | [keyword] | 3,000-4,000 | Links to all spokes |
| 1 | [Spoke title] | how-to-guide | [keyword] | 1,500-2,500 | Pillar + Spokes 2,3 |
| 2 | [Spoke title] | comparison | [keyword] | 1,500-2,500 | Pillar + Spokes 1,3 |
| 3 | [Spoke title] | listicle | [keyword] | 1,500-2,500 | Pillar + Spokes 1,2 |
| ... | ... | ... | ... | ... | ... |
```
Reference: `references/internal-linking.md` for hub-and-spoke model and anchor text rules.
### Step 5: Differentiation Strategy
The December 2025 Core Update rewards first-hand experience. Plan
how to demonstrate genuine expertise:
| Signal Type | Implementation |
|-------------|---------------|
| Original data | Conduct surveys, analyze proprietary data, run experiments |
| Case studies | Document real client/project results with metrics |
| Build in public | Share process, learnings, and failures transparently |
| Expert interviews | Feature practitioners with first-hand knowledge |
| Tool reviews | Test products personally, share screenshots and results |
| Industry analysis | Provide unique perspective on public data |
### Step 5.5: AI Citation Surface Strategy
Plan how to maximize AI citation across platforms. 80% of LLM citations
come from outside the top 100 organic results. Traditional SEO alone
is insufficient.
#### On-Site Optimization
Structure every piece of content for AI citability:
- Every H2 opens with an answer-first paragraph (40-60 words with stat + source)
- **Citation capsules**: 40-60 word self-contained passages per H2 section
- **Q&A format**: 60-70% of H2 headings phrased as questions
- **FAQ sections** with schema markup on every post
- **Entity clarity**: consistent terminology throughout (no synonym variation for key concepts)
- **Structured data**: JSON-LD for Article, FAQ, HowTo, and Review schemas
#### Off-Site Presence (Critical: 88-92% of AI citations from off-site)
| Channel | AI Citation Impact | Priority Action |
|---------|-------------------|-----------------|
| YouTube | 0.737 correlation (strongest) | Companion videos for pillar posts |
| Reddit | 450% citation surge | Authentic participation in 3-5 sRelated in Design
contribute
IncludedLocal-only OSS contribution command center. Auto-refreshes the user's in-flight PR and issue state on invoke so conversations start with full context — no need to brief Claude on what's in flight. Helps the user find issues to contribute to on GitHub, builds per-repo dossiers of what each upstream expects (CLA, DCO, branch convention, AI policy, draft-first, review bots, issue templates), runs deterministic gates before any external action so AI-assisted contributions don't reach maintainers as slop. State is markdown-only: candidate files at ~/.contribute-system/candidates/, repo dossiers at ~/.contribute-system/research/, append-only event log at ~/.contribute-system/log.jsonl. No database, no cloud calls. Use when the user asks about their PRs / issues / contributions, wants to find new work to take on, claim an issue, build/refresh a repo's dossier, or draft a Design Issue or PR. Trigger with "/contribute", "what's my PR status", "find a contribution", "claim issue X", "draft a Design Issue for Y", "refresh dossier for Z".
architectural-analysis
IncludedUser-triggered deep architectural analysis of a codebase or scoped subtree across eight modes — information architecture, data flow, integration points, UI surfaces, interaction patterns, data model, control flow, and failure modes. This skill should be used when the user asks to "diagram this codebase," "map the architecture," "show the data flow," "give me an ERD," "trace control flow," "find the integration points," "verify the layout pattern," "audit the UX architecture," or any similar request whose primary deliverable is mermaid diagrams plus cited reports under docs/architecture/. Dispatches haiku/sonnet sub-agents in parallel for per-mode exploration, then verifies every citation mechanically before any node lands in a diagram. Not for one-off prose explanations of code (use code-explanation) or for high-level system design from scratch (use system-design).
mcp
IncludedModel Context Protocol (MCP) server development and tool management. Languages: Python, TypeScript. Capabilities: build MCP servers, integrate external APIs, discover/execute MCP tools, manage multi-server configs, design agent-centric tools. Actions: create, build, integrate, discover, execute, configure MCP servers/tools. Keywords: MCP, Model Context Protocol, MCP server, MCP tool, stdio transport, SSE transport, tool discovery, resource provider, prompt template, external API integration, Gemini CLI MCP, Claude MCP, agent tools, tool execution, server config. Use when: building MCP servers, integrating external APIs as MCP tools, discovering available MCP tools, executing MCP capabilities, configuring multi-server setups, designing tools for AI agents.
react-native-skia
IncludedDesign, build, debug, and optimise high-polish animated graphics in React Native or Expo using @shopify/react-native-skia, Reanimated, and Gesture Handler. Use when the user wants canvas-driven UI, shaders, paths, rich text, image filters, sprite fields, Skottie, video frames, snapshots, web CanvasKit setup, or performance tuning for custom motion-heavy elements such as loaders, hero art, cards, charts, progress indicators, particle systems, or gesture-driven surfaces. Also use when the user asks for fluid, glow, glass, blob, parallax, 60fps/120fps, or GPU-friendly animated effects in React Native, even if they do not explicitly say "Skia". Do not use for ordinary form/layout work with standard views.
plaid
IncludedProduct Led AI Development — guides founders from idea to launched product. Six capabilities: Idea (discover a product idea), Validate (pressure-test the idea against fatal flaws, problem reality, competition, and 2-week MVP feasibility), Plan (vision intake + document generation), Design (translate image references into a design.md spec), Launch (go-to-market strategy), and Build (roadmap execution). Use when someone says "PLAID", "plaid idea", "help me find an idea", "product idea", "idea from my business", "idea from my expertise", "plaid validate", "validate my idea", "pressure-test", "is this idea good", "find fatal flaws", "validate the problem", "plan a product", "define my vision", "generate a PRD", "product strategy", "plaid design", "design from image", "translate image to design", "create design.md", "extract design tokens", "plaid launch", "go-to-market", "launch plan", "GTM strategy", "launch playbook", "plaid build", "build the app", "start building", or "execute the roadmap".
nextjs-framer-motion-animations
IncludedAdds production-safe Motion for React or Framer Motion animations to Next.js apps, including reveal, hover and tap micro-interactions, whileInView, stagger, AnimatePresence, layout and layoutId transitions, reorder, scroll-linked UI, and lightweight route-content transitions. Use when the user asks to add, refactor, or debug Motion or Framer Motion in App Router or Pages Router codebases, especially around server/client boundaries, reduced motion, LazyMotion, bundle size, hydration, or route transitions. Avoid for GSAP-style timelines, WebGL or 3D scenes, heavy scroll storytelling, or CSS-only effects unless Motion is explicitly requested.