write-api-reference

Generates MDX API reference pages for Next.js components, functions, directives, and more.

Updated Apr 7, 2026
One-click install
npx skills add https://github.com/villa1/backupshop --skill write-api-reference-villa1
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: write-api-reference
Source: https://github.com/villa1/backupshop/tree/main/.agents/skills/write-api-reference
Command: npx skills add https://github.com/villa1/backupshop --skill write-api-reference-villa1

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

API references are inconsistently documented, delaying integration and increasing support cost. This skill creates focused, one-API reference pages that are concise, example-driven, and aligned to category templates.

Core Features & Use Cases

  • Produces API reference documentation for Next.js APIs: functions, components, file conventions, directives, and config options.
  • Follows a category-based template to ensure consistency across docs and ease of discovery.
  • Generates a page with usage examples, reference sections, behavior notes, and examples for a single API surface.

Quick Start

Use this skill to draft an API reference page for a specific Next.js API, providing a minimal usage example and the appropriate category template.

Frequently Asked Questions about write-api-reference

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I generate API reference pages for Next.js functions and config options?

Generate Next.js API reference pages by creating focused MDX files from source code or user specifications. The output includes YAML frontmatter, usage examples, reference sections, and behavior notes for a single API surface.

What is the best way to document Next.js file conventions in MDX?

Document Next.js file conventions in MDX by applying a category-based template to ensure consistency. This approach yields concise, example-driven pages aligned with specific API categories like components or directives.

Can I use this approach to create API docs for both components and directives?

Yes, you can create API docs for both components and directives. The documentation process applies to functions, file conventions, and config options, generating a dedicated MDX page for each API surface.

How do I structure YAML frontmatter for Next.js API documentation?

Structure YAML frontmatter for Next.js API documentation by including title, description, usage example, reference, behavior notes, and examples. This metadata header standardizes the generated MDX page layout.

Why are inconsistently documented API references a problem for integration?

Inconsistently documented API references delay integration and increase support costs. Creating focused, one-API reference pages solves this by ensuring documentation is concise, example-driven, and aligned to category templates.