api-docs-reference

Generate an OpenAPI 3 specification from Spring REST Docs.

1|Updated Feb 21, 2026
One-click install
npx skills add https://github.com/kssumin/claude-playground --skill api-docs-reference
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: api-docs-reference
Source: https://github.com/kssumin/claude-playground/tree/main/.claude/skills/api-docs-reference
Command: npx skills add https://github.com/kssumin/claude-playground --skill api-docs-reference

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Streamlines API documentation by bridging REST Docs with OpenAPI 3, generating up-to-date specifications and Swagger UI for Spring services.

Core Features & Use Cases

  • Integrates Spring REST Docs with OpenAPI 3 to produce a single, consistent API spec.
  • Provides Swagger UI setup to browse documentation at runtime.
  • Demonstrates test patterns for POST/GET, pagination, and error cases, along with a reusable field utility.

Quick Start

Configure your Spring project to generate an OpenAPI spec from REST Docs and serve it through Swagger UI.

Frequently Asked Questions about api-docs-reference

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

FAQPage Schema
How do I convert Spring REST Docs to OpenAPI 3 specifications?

To convert Spring REST Docs to OpenAPI 3, you can bridge the two by configuring your Spring project to generate an OpenAPI specification directly from your existing REST Docs test snippets. This standardizes API documentation workflows for Spring-based services.

How do I serve Swagger UI for a Spring Boot application using REST Docs?

You can serve Swagger UI for a Spring Boot application by deploying the UI to browse the OpenAPI specification generated from your REST Docs at runtime. This provides a single, consistent API spec view for your services.

What test patterns are needed to generate OpenAPI documentation from REST Docs?

Generating OpenAPI documentation from REST Docs requires test patterns for POST and GET requests, pagination, and error cases. A reusable field utility is also demonstrated to help structure these tests effectively.

Does bridging REST Docs with OpenAPI 3 require plugin integration for Spring services?

Yes, bridging REST Docs with OpenAPI 3 requires plugin integration, OpenAPI configuration, and Swagger UI deployment to satisfy the standardized API documentation workflow requirements for Spring-based services.

Why use OpenAPI 3 with Spring REST Docs instead of generating documentation separately?

Using OpenAPI 3 with Spring REST Docs streamlines API documentation by producing a single, consistent API spec. This approach ensures your documentation remains up-to-date by generating specifications directly from your tests.