sdk-docs-generator

Generate CMS-compatible documentation JSON from SDK source exports.

Updated Aug 27, 2026

Search Tags:#automation #documentation #sdk #cms #docs-generation #sanity-cms

Ready to run

npx skills add https://github.com/eugene-belkovich/ai-setup --skill sdk-docs-generator

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: sdk-docs-generator
Source: https://github.com/eugene-belkovich/ai-setup/tree/main/claude/profiles/work/skills/docs/sdk-docs-generator
Command: npx skills add https://github.com/eugene-belkovich/ai-setup --skill sdk-docs-generator

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Generate CMS-compatible documentation JSON from the SDK source to ensure documentation always reflects the current exports and surface.

Core Features & Use Cases

Inventory the SDK surface by parsing sdk/src exports and types.
Produce CMS-ready JSON for a Sanity-based docs site, covering overview, types, guides, and changelog.
Validate drift between code and docs and provide a repeatable update pipeline during releases.

Quick Start

Run the sdk-docs-generator against the sdk/src directory to refresh all CMS pages and update the documentation bundle.

Frequently Asked Questions about sdk-docs-generator

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

FAQPage Schema

How do I generate documentation JSON from SDK source code automatically?▼

You can generate documentation JSON from SDK source code by parsing the sdk/src exports and types to output CMS-compatible JSON that reflects exact type signatures for the Sanity import pipeline.

What is the best way to keep SDK documentation in sync with code changes?▼

The best way to keep SDK docs in sync with code is to run a repeatable update pipeline that validates drift between source and docs, refreshing overview, types, responses, blocks, and utilities after SDK changes or releases.

Can I use this to update Sanity CMS pages when my SDK adds new exports?▼

Yes, you can update Sanity CMS pages when your SDK adds new exports by running the generator against the sdk/src directory to refresh all CMS pages and produce CMS-ready JSON covering overview, types, guides, and changelog.

How do I validate documentation drift between my SDK source and published docs?▼

You validate documentation drift between your SDK source and published docs by inventorying the SDK surface from source and producing updated CMS-ready JSON to compare against existing documentation covering overview, types, guides, and changelog.

Does this approach work for generating Sanity CMS import files from TypeScript SDKs?▼

Yes, this approach works for generating Sanity CMS import files from TypeScript SDKs by extracting exact type signatures from source and producing JSON that follows the CMS JSON schema and aligns with the Sanity CMS import pipeline.

When should I run an SDK documentation generator during my release process?▼

You should run an SDK documentation generator during your release process after SDK changes, feature additions, or releases to refresh CMS pages and ensure the documentation bundle always reflects the current exports and SDK surface.