Login
kostja94/marketing-skills1 file

Docs Page Generator

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.

Use this skillView repositoryView on skills.sh
Specification
Skill ID
kostja94/marketing-skills/docs-page-generator
Publisher
kostja94
Repository
marketing-skills
Installs
0
Files
1
Synced
Sep 23, 2026
How to use it

Open any RiverX project, open the Skills panel in the chat, and search for this identifier. The files are fetched from the source repository at install time.

kostja94/marketing-skills/docs-page-generatorInstalls these files
  • SKILL.md

What this skill tells the agent

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

SectionPurposeTypical Content
Getting StartedOnboarding, first stepsQuick start, installation, first task
Guides / TutorialsStep-by-step learningHow-to articles, workflows
ConceptsBackground, architectureKey concepts, glossary links
API ReferenceEndpoint docsAuth, request/response, examples; part of docs, not separate page
TroubleshootingProblem solvingFAQ, 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

More from kostja94

kostja94/marketing-skills

404 Page Generator

When the user wants to create, optimize, or audit 404 error pages. Also use when the user mentions "404 page," "404 error," "error page," "page not found," "broken link page," "404 design," "custom 404," "404 redirect," "404 page UX," or "404 recovery." For sitewide page planning, use website-structure.

kostja94/marketing-skills

About Page Generator

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.

kostja94/marketing-skills

Affiliate Marketing

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.

Use this skill in a project

Open any RiverX project, search the Skills panel for kostja94/marketing-skills/docs-page-generator, and install it in one click.

Use this skill