What data types are supported by these patterns?

The skill includes specialized patterns for UUIDs, Strings, Enums, Booleans, Integers, Timestamps, Arrays, and JSONB objects.

Can it document deprecated or read-only fields?

Yes, it includes specific formatting patterns and prefixes to clearly identify Deprecated, Read-only, and Nullable fields to end-users.

Does it handle the difference between requests and responses?

Yes, it provides specific rules for indicating required fields in requests and uses a standardized placeholder for response fields where the required status is not applicable.

How does this skill help with API documentation?

It provides standardized patterns and templates for describing API fields, ensuring consistency across your entire API reference by defining specific ways to explain types, constraints, and purposes.

Is there a way to verify the quality of the documentation generated?

The skill includes a quality checklist that covers field purpose, type accuracy, constraints, default values, and relationship clarity to ensure high-standard output.

API Field Documentation Standards

Name: API Field Documentation Standards
Author: LerianStudio

byLerianStudio

•

API Development

Standardizes API field documentation with consistent patterns for types, constraints, and realistic examples.

About

The api-field-descriptions skill provides a structured framework for documenting API request and response schemas, ensuring that field-level documentation is clear, consistent, and user-centric. By enforcing specific patterns for various data types—such as UUIDs, enums, and timestamps—it helps developers create self-explanatory API references that include mandatory constraints, example values, and edge-case behaviors. This tool is essential for teams looking to improve API usability and maintain high-quality documentation standards within their automated development workflows.

Key Features

Preferred Markdown table structures for clean request and response schema visualization
Clear logic for documenting Required, Optional, and Conditional fields
Support for special field states like deprecated, read-only, and nullable behaviors
Comprehensive 10-point quality checklist for API field accuracy
Standardized description patterns for all major data types including UUID, Enum, and JSONB
17 GitHub stars

Use Cases

Refactoring legacy API schemas to meet modern developer experience standards
Generating documentation for new REST or GraphQL API endpoints
Creating consistent internal data model documentation for microservices

About

Key Features

Preferred Markdown table structures for clean request and response schema visualization
Clear logic for documenting Required, Optional, and Conditional fields
Support for special field states like deprecated, read-only, and nullable behaviors
Comprehensive 10-point quality checklist for API field accuracy
Standardized description patterns for all major data types including UUID, Enum, and JSONB
17 GitHub stars

Use Cases

Refactoring legacy API schemas to meet modern developer experience standards
Generating documentation for new REST or GraphQL API endpoints
Creating consistent internal data model documentation for microservices