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 product marketing context first: If .claude/product-marketing-context.md or .cursor/product-marketing-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: Separate pages →endpoint reference, auth, examples, tutorials
Best Practices
Overview and Structure
- What the API does: Clear value proposition, key capabilities
- Use cases: Who uses it, common scenarios
- Getting started: Quick path to first call or docs
- Link to docs: Prominent CTA to API documentation
Content
- Key concepts: High-level, not endpoint-level detail
- Auth overview: How auth works; link to docs for details
- Pricing/limits: If relevant for evaluation
- SDKs and tools: If available; link to docs
SEO and Discovery
- Developer search: Target "API" + product/category terms
- Metadata: Title, description for developer intent
- Internal links: From homepage, features, resources
Output Format
- Structure outline (sections)
- Value proposition and key messages
- CTA to documentation or signup
- SEO metadata for developer search
Related Skills
- pages-home: Link to API page for developers
- seo-on-page-schema: WebPage or SoftwareApplication schema
- seo-on-page-title, seo-on-page-description, seo-on-page-metadata: API page metadata
1---2name: pages-api-introduction3description: 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.4---56# Pages: API Introduction78Guides 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.910**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.1112## Initial Assessment1314**Check for product marketing context first:** If `.claude/product-marketing-context.md` or `.cursor/product-marketing-context.md` exists, read it for product and developer use cases.1516Identify:171. **API type**: REST, GraphQL, etc.182. **Audience**: Developers (integration) vs. decision makers (evaluation)193. **Docs location**: Where API documentation lives (e.g. `/docs`, `/api/reference`, external)2021## Page Role2223- **API page** (`/api`): Introduction, overview, value prop, CTA to docs or signup24- **API documentation**: Separate pages →endpoint reference, auth, examples, tutorials2526## Best Practices2728### Overview and Structure2930- **What the API does**: Clear value proposition, key capabilities31- **Use cases**: Who uses it, common scenarios32- **Getting started**: Quick path to first call or docs33- **Link to docs**: Prominent CTA to API documentation3435### Content3637- **Key concepts**: High-level, not endpoint-level detail38- **Auth overview**: How auth works; link to docs for details39- **Pricing/limits**: If relevant for evaluation40- **SDKs and tools**: If available; link to docs4142### SEO and Discovery4344- **Developer search**: Target "API" + product/category terms45- **Metadata**: Title, description for developer intent46- **Internal links**: From homepage, features, resources4748## Output Format4950- **Structure** outline (sections)51- **Value proposition** and key messages52- **CTA** to documentation or signup53- **SEO** metadata for developer search5455## Related Skills5657- **pages-home**: Link to API page for developers58- **seo-on-page-schema**: WebPage or SoftwareApplication schema59- **seo-on-page-title, seo-on-page-description, seo-on-page-metadata**: API page metadata
tools-only