skills.rest
cc01cc
cc01ccCOMMUNITY
Explore all skills by this author →
WebsiteGitHub

typedoc-visibility-auditor

Audit TypeDoc visibility and export surfaces across multi-package projects.

4|Updated Jan 22, 2026
Search Tags:#documentation#api#audit#export#visibility#internal#typedoc
One-click install
npx skills add https://github.com/cc01cc/cmtx-project --skill typedoc-visibility-auditor
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: typedoc-visibility-auditor
Source: https://github.com/cc01cc/cmtx-project/tree/main/.kilo/skills-repo/develop/typedoc-visibility-auditor
Command: npx skills add https://github.com/cc01cc/cmtx-project --skill typedoc-visibility-auditor

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This skill helps teams define and enforce stable public API boundaries by auditing TypeDoc exports and visibility annotations across multi-package projects.

Core Features & Use Cases

  • Clarify what should be public vs internal in TypeDoc and generate a consistent category scheme.
  • Design and apply module-based grouping to API surfaces, improving navigability in generated docs.
  • Provide audit reports and recommended changes that reduce API surface area without breaking consumers.

Quick Start

Analyze your TypeDoc output and apply a stable visibility and categorization scheme to your API surface.

Frequently Asked Questions about typedoc-visibility-auditor

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

FAQPage Schema
How do I audit TypeDoc visibility and exports for a multi-package project?▼

Auditing TypeDoc visibility involves analyzing export surfaces to classify symbols as public or internal, standardizing API boundaries across multi-package projects to generate a consistent categorization scheme and cleaner documentation.

What is the best way to group TypeDoc exports by module for API documentation?▼

Grouping TypeDoc exports by module requires applying module-based categorization to API surfaces, improving navigability in generated docs by enforcing clear public API boundaries and a stable categorization scheme across packages.

How does TypeDoc visibility annotation affect my public API surface area?▼

Visibility annotations determine which symbols appear in generated TypeDoc output; auditing them helps reduce API surface area without breaking consumers by clarifying internal versus public boundaries and providing recommended changes.

Can I standardize TypeDoc categorization across multiple packages?▼

Standardizing TypeDoc categorization across multiple packages is supported by auditing export surfaces and visibility annotations to enforce clear public API boundaries and generate a consistent category scheme.

Why does my TypeDoc output expose internal symbols that should not be public?▼

TypeDoc output exposes internal symbols when visibility annotations and export surfaces are not properly audited; applying a stable visibility scheme ensures internal symbols are hidden and public API boundaries are enforced.

Related Skills

Explore More Software Engineering Skills→
tsurutantsurutan

doc-generator

Generate inline and standalone documentation from JavaScript, TypeScript, Python, and Go code.

Community
Intermediate
giuseppe-trisciuogliogiuseppe-trisciuoglio
322

typescript-docs

Generate TypeScript API references and ADRs with TypeDoc and JSDoc.

Community
Advanced
NeKon69NeKon69
1

Plugin.hardtime

Provide API reference and usage notes for the hardtime.nvim plugin.

Community
Basic
tankpkgtankpkg
1

@tank/ast-linter-codemod

Create custom ESLint rules with auto-fix and codemods for API migrations.

Official
Advanced