t-doc

Scan codebases to generate structured tutorial documentation under docs/tutorials/.

64|6|Updated Apr 17, 2026
One-click install
npx skills add https://github.com/timzaak/web-dev-skills --skill t-doc
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: t-doc
Source: https://github.com/timzaak/web-dev-skills/tree/main/skills/t-doc
Command: npx skills add https://github.com/timzaak/web-dev-skills --skill t-doc

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

Generate project tutorial documentation that reads like a human wrote it, not like AI output. It scans the codebase, extracts architecture, APIs, config, and deployment details, and writes structured tutorial docs under docs/tutorials/ to accelerate onboarding and knowledge transfer.

Core Features & Use Cases

  • Codebase scanning and automatic extraction of architecture, APIs, configuration, and deployment details.
  • Generation of structured, human-readable tutorials for onboarding, getting-started guides, API references, and deployment walkthroughs.
  • Support for multiple languages/frameworks by adapting the docs to project structure and conventions.

Quick Start

Run the command /t-doc <project-name> to generate a full tutorial documentation set under docs/tutorials/.

Frequently Asked Questions about t-doc

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

FAQPage Schema
How do I generate project documentation from a codebase automatically?

Generate project documentation by scanning a codebase to extract architecture, APIs, configuration, and deployment details, which outputs structured, human-readable tutorials under docs/tutorials/ to accelerate onboarding and knowledge transfer.

What is the best way to create developer tutorials for onboarding?

Creating developer tutorials is best handled by scanning repo content to automatically assemble getting-started guides, API references, and deployment walkthroughs, ensuring the output reads like a human wrote it rather than AI-generated text.

How do I extract architecture and API details for deployment walkthroughs?

Extract architecture and API details by scanning the repository content, validating inputs to assemble comprehensive deployment walkthroughs and structured documentation that adapts to the project's conventions and directory structure.

Can I generate documentation for multiple programming languages and frameworks?

Generate documentation for multiple languages and frameworks by adapting the output to the specific project structure and conventions, allowing the scanning mechanism to support diverse codebases without manual configuration overrides.

Does codebase documentation generation work for existing repositories?

Codebase documentation generation works for existing repositories by validating inputs through repo content scanning, automatically extracting configuration and deployment details to write structured tutorial docs directly into the project.

Why does my generated API reference read like AI output instead of human-written docs?

Generated API references read like AI output when the tool lacks deep codebase scanning; resolving this requires a skill that extracts architecture and validates repo content to assemble structured, human-friendly tutorials rather than generic summaries.