When the user wants to plan content strategy or decide what topics to cover — "what should I write about," "blog strategy," "topic clusters," "editorial calendar," "content pillars," "content roadmap," "I don't know what to write." For writing individual pieces, see copywriting. For SEO audits, see seo-audit. For social media, see social-content.
中文简介正在准备中。当前显示原文说明。
安装前可以查看交给 AI 代理的指令内容。
Plan content that drives traffic, builds authority, and generates leads by being searchable, shareable, or both.
Product context: If .agents/product-marketing-context.md exists (or .claude/product-marketing-context.md in older setups), read it first and tailor output to it; only ask for what it doesn't cover.
Gather (ask if not provided):
Every piece must be searchable, shareable, or both — prioritize in that order; search traffic is the foundation. Searchable content captures existing demand from people actively looking for answers. Shareable content creates demand by spreading ideas.
Searchable: target a specific keyword or question and match search intent exactly; clear titles matching search queries; headings that mirror search patterns; keywords in title, headings, first paragraph, URL; comprehensive coverage (leave no questions unanswered) with data, examples, links to authoritative sources; optimize for AI/LLM discovery (clear positioning, structured content, brand consistency across the web).
Shareable: lead with a novel insight, original data, or counterintuitive take; challenge conventional wisdom with well-reasoned arguments; tell stories that make people feel something; share vulnerable, honest experiences others can learn from; create content people share to look smart or help others; connect to current trends or emerging problems.
Use-Case Content Formula: [persona] + [use-case]. Targets long-tail keywords: "Project management for designers," "Task tracking for developers," "Client collaboration for freelancers."
Hub and Spoke Hub = comprehensive overview. Spokes = related subtopics.
/topic (hub)
├── /topic/subtopic-1 (spoke)
├── /topic/subtopic-2 (spoke)
└── /topic/subtopic-3 (spoke)
Hub first, then spokes; interlink strategically.
Note: /blog/post-title is sufficient for most posts; reserve dedicated hub/spoke URL structures for major topics with layered depth (e.g., Atlassian's /agile guide).
Template Libraries High-intent keywords + product adoption: target searches like "marketing plan template," provide immediate standalone value, show how the product enhances the template.
Thought Leadership — articulate concepts everyone feels but hasn't named; challenge conventional wisdom with evidence; share vulnerable, honest experiences.
Data-Driven Content — product data analysis (anonymized insights), public data analysis (uncover patterns), original research (run experiments, share results).
Expert Roundups — 15-30 experts answering one specific question; built-in distribution.
Case Studies — Challenge → Solution → Results → Key learnings.
Meta Content — behind-the-scenes transparency: "How We Got Our First $5k MRR," "Why We Chose Debt Over VC."
For programmatic content at scale, see programmatic-seo skill.
Content pillars are the 3-5 core topics your brand will own; each spawns a cluster of related content. Most content can live under /blog with good internal linking — dedicated pillar pages with custom URLs (like /guides/topic) are only needed for comprehensive multi-layered resources.
Pillar Topic (Hub)
├── Subtopic Cluster 1 → Articles A, B, C
├── Subtopic Cluster 2 → Articles D, E, F
└── Subtopic Cluster 3 → Articles G, H, I
Good pillars align with your product/service, match what your audience cares about, have search volume and/or social interest, and are broad enough for many subtopics.
Map topics to the buyer's journey using keyword modifiers:
Modifiers: "what is," "how to," "guide to," "introduction to" Example (project management basics): "What is Agile Project Management," "Guide to Sprint Planning," "How to Run a Standup Meeting"
Modifiers: "best," "top," "vs," "alternatives," "comparison" Example (evaluating tools): "Best Project Management Tools for Remote Teams," "Asana vs Trello vs Monday," "Basecamp Alternatives"
Modifiers: "pricing," "reviews," "demo," "trial," "buy" Example (pricing in sales calls): "Project Management Tool Pricing Comparison," "How to Choose the Right Plan," "[Product] Reviews"
Modifiers: "templates," "examples," "tutorial," "how to use," "setup" Example (support tickets show struggles): "Project Template Library," "Step-by-Step Setup Tutorial," "How to Use [Feature]"
If user provides keyword exports (Ahrefs, SEMrush, GSC), analyze for: topic clusters (group related keywords), buyer stage, search intent (informational, commercial, transactional), quick wins (low competition + decent volume + high relevance), and content gaps (keywords competitors rank for that you don't).
Output as prioritized table: | Keyword | Volume | Difficulty | Buyer Stage | Content Type | Priority |
From sales or customer call transcripts, extract: questions asked (→ FAQ content or blog posts), pain points (problems in their own words), objections (content to address proactively), language patterns (exact voice-of-customer phrases), competitor mentions. Output content ideas with supporting quotes.
Mine survey data for: open-ended responses (topics and language), common themes (30%+ mention = high priority), resource requests (what they wish existed), content format preferences.
Use web search:
Reddit: site:reddit.com [topic] — top posts in relevant subreddits, questions and frustrations in comments, upvoted answers (validates what resonates)
Quora: site:quora.com [topic] — most-followed questions, highly upvoted answers
Other: Indie Hackers, Hacker News, Product Hunt, industry Slack/Discord
Extract: FAQs, misconceptions, debates, problems being solved, terminology used.
Find their content: site:competitor.com/blog
Analyze: top-performing posts (comments, shares), repeatedly covered topics, uncovered gaps, case studies (customer problems, use cases, results), content structure (pillars, categories, formats).
Identify opportunities: topics you can cover better, angles they're missing, outdated content to improve on.
From customer-facing teams: common objections, repeated questions, support ticket patterns, success stories, feature requests and underlying problems.
Score each idea on four factors:
Frequency in research; percentage of customers facing the challenge; emotional charge of the pain point; potential LTV of customers with this need.
Alignment with problems your product solves; unique insights from customer research; supporting customer stories; natural path to product interest.
Monthly search volume; competitiveness; related long-tail opportunities; growing vs. declining interest.
Expertise to create authoritative content; additional research needed; assets required (graphics, data, examples).
| Idea | Customer Impact (40%) | Content-Market Fit (30%) | Search Potential (20%) | Resources (10%) | Total |
|---|---|---|---|---|---|
| Topic A | 8 | 9 | 7 | 6 | 8.0 |
| Topic B | 6 | 7 | 9 | 8 | 7.1 |
3-5 pillars with rationale, subtopic clusters for each, and how pillars connect to product.
For each recommended piece: topic/title; searchable, shareable, or both; content type (use-case, hub/spoke, thought leadership, etc.); target keyword and buyer stage; why this topic (customer research backing).
Visual or structured representation of how content interconnects.
还没有评价。欢迎分享你的使用感受。
无需登录即可发表。欢迎分享使用感受、提问，或说明在哪些环境下无法运行。
还没有评论。来写第一条吧。
Act as a Senior Accessibility Engineer to audit a page, component, or design against WCAG 2.2 AA. Produces a triaged finding list (critical/serious/moderate), focus-order map, contrast report, ARIA decision tree, and a screen-reader test plan. Use when shipping new UI, hardening an existing flow, or preparing for VPAT/accessibility conformance.
中文简介正在准备中。当前显示原文说明。
When the user wants to plan, design, or implement an A/B test or experiment — "split test," "variant copy," "multivariate test," "hypothesis," "statistical significance," "how long should I run this test," or comparing two versions. For tracking implementation, see analytics-tracking. For page-level conversion optimization, see page-cro.
中文简介正在准备中。当前显示原文说明。
When the user wants to generate, iterate, or scale ad creative — headlines, descriptions, primary text, full variations — for any paid platform; 'ad copy variations,' 'RSA headlines,' 'bulk ad copy,' 'creative testing,' 'write me some ads.' For campaign strategy and targeting, see paid-ads. For landing page copy, see copywriting.
中文简介正在准备中。当前显示原文说明。
When the user wants content cited by LLMs or surfaced in AI-generated answers — 'AI SEO,' 'AEO,' 'GEO,' 'LLMO,' 'answer engine optimization,' 'AI Overviews,' 'optimize for ChatGPT/Perplexity/Claude,' 'AI citations,' 'zero-click search.' For traditional technical/on-page audits, see seo-audit. For structured data, see schema-markup.
中文简介正在准备中。当前显示原文说明。
When the user wants to set up, improve, or audit analytics tracking and measurement — "GA4," "conversion tracking," "event tracking," "UTM parameters," "tag manager," "GTM," "tracking plan," "attribution," "Mixpanel," "Segment," "are my events firing," or how to measure marketing results. For A/B test measurement, see ab-test-setup.
中文简介正在准备中。当前显示原文说明。
Architectural decision advisor for cloud, data, and SaaS distributed systems. Use when the user asks "should we use X or Y", weighs a tradeoff, or needs a decision matrix, scaling analysis, cost-at-scale review, data-tier design, multi-tenancy model, or API/resilience guidance. For full technical blueprints, use enterprise-design.
中文简介正在准备中。当前显示原文说明。