docs

Generate JSDoc, Storybook stories, READMEs, and API docs from TypeScript source.

Updated Aug 27, 2026
One-click install
npx skills add https://github.com/strongerDeer/stronger-dotfiles --skill docs-strongerdeer
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: docs
Source: https://github.com/strongerDeer/stronger-dotfiles/tree/main/claude/skills/docs
Command: npx skills add https://github.com/strongerDeer/stronger-dotfiles --skill docs-strongerdeer

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Automates the generation of technical documentation by analyzing source code to produce JSDoc comments, Storybook stories, and README content.

Core Features & Use Cases

  • JSDoc generation: Extracts type definitions, props, parameters, and usage examples from TypeScript/JavaScript source.
  • Storybook integration: Creates stories with controls, args, and variants to showcase components.
  • README & API docs: Generates component READMEs and API documentation from source annotations.

Quick Start

Run the docs builder on your codebase to generate JSDoc, Storybook stories, README files, and API docs.

Frequently Asked Questions about docs

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

FAQPage Schema
How do I auto-generate JSDoc comments from TypeScript source code?

To auto-generate JSDoc comments from TypeScript source code, run the docs builder to statically analyze your files and extract type definitions, props, and parameters into consistent annotations.

Can I generate Storybook stories automatically from React components?

Yes, you can generate Storybook stories automatically from React components by statically analyzing the source to extract props and types, then outputting stories with controls, args, and variants.

What is the best way to create README files and API docs from source annotations?

The best way to create README files and API docs from source annotations is to parse your JavaScript and TypeScript comments during static analysis and output structured markdown documentation artifacts.

Does this documentation generation approach work with plain JavaScript or only TypeScript?

This documentation generation approach works with both TypeScript and JavaScript sources, statically analyzing types and annotation comments to produce READMEs, JSDoc, and API documentation.

How do I extract props and usage examples for my React components?

You extract props and usage examples for React components by running a static analysis process over your source code that parses type definitions and annotation comments to build comprehensive documentation.

What are the limitations of auto-generating documentation from source code?

Limitations of auto-generating documentation from source code include a strict reliance on static analysis and existing annotation comments, meaning runtime behaviors or undocumented logic may not be captured in the output artifacts.