sc-document

Generate inline code comments, API references, and user guides.

19|2|Updated Aug 26, 2025
One-click install
npx skills add https://github.com/Tony363/SuperClaude --skill sc-document-tony363
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: sc-document
Source: https://github.com/Tony363/SuperClaude/tree/main/.claude/skills/sc-document
Command: npx skills add https://github.com/Tony363/SuperClaude --skill sc-document-tony363

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) components.

What problem does it solve?

This Skill automates the creation of various types of documentation, from inline code comments to comprehensive API references and user guides, reducing the manual effort and ensuring consistency.

Core Features & Use Cases

  • Inline Documentation: Generates JSDoc/docstrings for functions, including parameters, returns, and exceptions.
  • API References: Creates detailed documentation for API endpoints, including request/response schemas and usage examples.
  • User Guides: Develops user-focused tutorials and implementation patterns.
  • Use Case: A developer needs to document a new authentication module. They can use this skill to generate inline comments for the code, create an API reference for the endpoints, and produce a brief user guide explaining how to integrate it.

Quick Start

Use the sc-document skill to generate inline documentation for the file src/auth/login.js.

Frequently Asked Questions about sc-document

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

FAQPage Schema
How do I generate API references and user guides for my code components?

Generating inline documentation like JSDoc or docstrings for functions involves analyzing code components to automatically produce parameter descriptions, return values, and exceptions. This ensures technical writing consistency and reduces the manual effort required to document code logic.

What's the best way to automate technical writing for an authentication module?

The best way to automate technical writing for an authentication module is to generate inline comments for the code, create an API reference for the endpoints, and produce a brief user guide explaining the integration. This covers all necessary documentation types consistently.

Can I generate both inline code comments and external documentation files at the same time?

You can generate both inline code comments and external documentation files simultaneously. The system supports bulk generation across different types and styles, allowing you to produce JSDoc for functions and external user guides concurrently.

Does this documentation generation approach work with MCP integrations for review and publishing?

Documentation generation integrates with PAL and Rube MCPs for review, lookup, writing assistance, publishing, and bulk generation. These integrations streamline the technical writing workflow by connecting code analysis directly to publishing pipelines.

When do I need to generate API references versus user guides for my features?

Generate API references when documenting endpoint schemas and usage examples for developers, whereas user guides are needed for user-focused tutorials and implementation patterns. Generating both ensures comprehensive coverage for different audiences interacting with your features.