docs-page-generator
The docs-page-generator skill guides the creation and organization of documentation sites, including Getting Started sections, how-to guides, API reference materials, and troubleshooting content. Use this skill when a user requests help building or optimizing a documentation site, mentions specific documentation types like knowledge bases or help centers, or references documentation subdomains or paths such as docs.yourdomain.com.
git clone --depth 1 https://github.com/kostja94/marketing-skills /tmp/docs-page-generator && cp -r /tmp/docs-page-generator/skills/pages/content/docs ~/.claude/skills/docs-page-generatorSKILL.md
# 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 - **howto-section-generator**: HowTo step blocks in guides/tutorials; TechArticle + HowTo alignment - **content-strategy**: Doc content planning
When the user wants to create, optimize, or audit About page content. Also use when the user mentions "about page," "about us," "company story," "our team," "about section," "company overview," "brand story," "team page," or "who we are." For sitewide page planning, use website-structure.
When the user wants to plan, implement, or optimize affiliate marketing strategy. Also use when the user mentions "affiliate marketing," "affiliate program strategy," "CPS model," "affiliate recruitment," "commission structure," "affiliate partners," "affiliate network," "affiliate tracking," "affiliate commission," or "partner marketing." For affiliate page, use affiliate-page-generator.
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.
When the user wants to track AI search traffic in GA4 or GSC. Also use when the user mentions "AI traffic," "ChatGPT referral," "Perplexity traffic," "AI Overviews," "GA4 AI sources," "AI search analytics," "track AI referrals," "AI search traffic," "Claude traffic," or "how to track AI traffic." For AI SEO strategy, use generative-engine-optimization.
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.
When the user wants to set up, audit, or optimize analytics tracking (GA4, events, conversions). Also use when the user mentions "Google Analytics," "GA4," "event tracking," "conversions," "attribution model," "gtag," "data layer," "GA4 setup," "conversion tracking," "event setup," "User ID tracking," or "CTA attribution." For traffic insights, use traffic-analysis.
When the user wants to create, optimize, or audit the API introduction/overview page. Also use when the user mentions "API page," "API landing page," "/api page," "API overview," "developer landing," "API marketing," or "API for developers." Note: API documentation (endpoint reference) lives in docs; use docs-page-generator.
When the user wants to write, generate, or create article body content—blog post body, long-form content, how-to guide, listicle. Also use when the user mentions "write article," "article content," "blog post content," "article body," "long-form content creation," "generate article," "article draft," "how-to guide content," "listicle content," "information gain," or "content density." For single post page structure, schema, and SEO metadata, use article-page-generator. For blog index/listing page, use blog-page-generator. For short ad, landing, or email copy, use copywriting.