api-page-generator

SKILL.md

Pages: API Introduction

Guides the API introduction page →typically at /api →that overviews the API, use cases, and links to documentation. API documentation (endpoint reference, code examples) lives on separate pages.

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 developer use cases.

Identify:

API type: REST, GraphQL, etc.

Audience: Developers (integration) vs. decision makers (evaluation)

Docs location: Where API documentation lives (e.g. /docs, /api/reference, external)

Page Role

API page (/api): Introduction, overview, value prop, CTA to docs or signup

API documentation: Lives in docs (docs.*) → API Reference section with endpoint reference, auth, examples