api-docs

Generate HTML API documentation for Squint endpoints from extracted codebase types.

Updated Jul 11, 2022
One-click install
npx skills add https://github.com/kvnxiao/.dotfiles --skill api-docs-kvnxiao
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: api-docs
Source: https://github.com/kvnxiao/.dotfiles/tree/main/claude/skills/api-docs
Command: npx skills add https://github.com/kvnxiao/.dotfiles --skill api-docs-kvnxiao

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill automates the creation of HTML API documentation for Squint endpoints, converting codebase metadata into structured, navigable docs that can be consumed by external developers.

Core Features & Use Cases

  • Automated endpoint documentation: Generate HTML docs for REST endpoints including request/response details and authentication notes.
  • Standardized structure: Produces docs with a consistent layout and sections compatible with Google Docs.
  • Use Case: Suppose you onboard a partner; you can generate up-to-date API docs and share a link to the HTML docs in documents or portals.

Quick Start

Run the documentation generator on a target API module or let it scan the repository to discover endpoints.

Frequently Asked Questions about api-docs

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

FAQPage Schema
How do I generate HTML API documentation for Squint endpoints?

To generate HTML API documentation for Squint endpoints, run the documentation generator on a target API module or let it scan the repository to discover endpoints. It extracts router, handler, and service metadata to produce structured HTML docs.

Can I copy generated API documentation directly into Google Docs?

Generated API documentation is compatible with Google Docs, producing structured HTML output that details request and response structures. You can share these HTML docs directly into documents or onboarding portals for external developers.

What should API documentation for external-facing endpoints include?

API documentation for external-facing endpoints should detail request and response structures, authentication methods, and error mappings. This ensures external developers and partners understand integration requirements by extracting metadata from the codebase.

How does automated endpoint documentation handle internal integrations?

Automated endpoint documentation handles internal integrations by extracting router, handler, service, and response types from the codebase. It applies the same structured HTML formatting to both external-facing endpoints and internal integrations.

Do I need to manually format the output of the generated developer docs?

You do not need to manually format the output of generated developer docs. The output adheres to predefined HTML templates to ensure consistent formatting and standardized structure across all generated API documentation files.

Where does the generated HTML API documentation get saved?

The generated HTML API documentation gets saved to the docs/api-docs/api/v1 directory. This standardized output location ensures developers can consistently find and access the endpoint documentation within the repository.