Does this skill help with API lifecycle management?

Yes, it supports the x-apidog-status field to track endpoints through stages like designing, developing, testing, and released.

What is the primary purpose of the Bun.js Apidog skill?

It automates the creation of OpenAPI 3.0 specifications and provides a seamless way to sync your Bun.js backend documentation with the Apidog platform.

Why is camelCase mandatory in this skill?

CamelCase is the native standard for the JavaScript/JSON ecosystem and TypeScript, ensuring seamless integration between your API, frontend clients, and auto-generated code.

What environment variables are required for Apidog synchronization?

You need to define APIDOG_PROJECT_ID and APIDOG_API_TOKEN in your environment to allow Claude to push updates to your Apidog project.

Can I organize my API endpoints into folders?

Yes, the skill uses the x-apidog-folder extension to visually organize your API structure within the Apidog interface.

Bun.js OpenAPI & Apidog Integration

Name: Bun.js OpenAPI & Apidog Integration
Author: MadAppGang

byMadAppGang

•

196

API Development

Streamlines API documentation by generating OpenAPI 3.0 specifications and synchronizing them with Apidog for Bun.js TypeScript backends.

About

This skill provides a standardized workflow for managing the API lifecycle in Bun.js environments, bridging the gap between code and documentation. It enforces industry-standard OpenAPI 3.0 patterns, mandates camelCase naming conventions for JSON consistency, and utilizes Apidog-specific extensions to organize endpoints by status and ownership. By automating the synchronization process via the Apidog REST API, it ensures that your visual documentation, mock servers, and testing suites remain perfectly aligned with your backend implementation.

Key Features

196 GitHub stars
Support for Apidog extensions like x-apidog-folder and x-apidog-status
Enforced camelCase naming conventions for API field consistency
OpenAPI 3.0 specification generation for Bun.js backends
Automated documentation synchronization via Apidog REST API
Standardized schema design for reusable request/response models

Use Cases

Generating and maintaining live API documentation for Bun.js microservices
Synchronizing local schema changes with team-wide Apidog workspaces
Standardizing API contracts and naming conventions across backend teams

About

Key Features

196 GitHub stars
Support for Apidog extensions like x-apidog-folder and x-apidog-status
Enforced camelCase naming conventions for API field consistency
OpenAPI 3.0 specification generation for Bun.js backends
Automated documentation synchronization via Apidog REST API
Standardized schema design for reusable request/response models

Use Cases

Generating and maintaining live API documentation for Bun.js microservices
Synchronizing local schema changes with team-wide Apidog workspaces
Standardizing API contracts and naming conventions across backend teams