
Typescript Docs
Generate layered TypeScript API docs, JSDoc, ADRs, and framework-specific reference for libraries and apps you are building.
Overview
typescript-docs is an agent skill for the Build phase that generates layered TypeScript documentation with JSDoc, TypeDoc, ADRs, and framework-specific patterns for NestJS, Express, React, Angular, and Vue.
Install
npx skills add https://github.com/giuseppe-trisciuoglio/developer-kit --skill typescript-docsWhat is this skill?
- TypeDoc and Compodoc commands plus ESLint JSDoc validation for documentation quality
- JSDoc patterns for TypeScript constructs and multi-audience layered documentation
- ADR creation and maintenance for architectural decisions
- Framework-specific patterns for NestJS, Express, React, Angular, and Vue
- GitHub Actions pipeline setup for automated doc generation
- Supports TypeDoc, Compodoc, and ESLint JSDoc validation in the documented toolchain
- Framework-specific documentation patterns for NestJS, Express, React, Angular, and Vue
Adoption & trust: 1.5k installs on skills.sh; 271 GitHub stars; 3/3 security scanners passed (skills.sh audits).
What problem does it solve?
Your TypeScript project lacks consistent API reference, inline types, and recorded design decisions, so collaborators and future-you cannot trust the docs.
Who is it for?
Solo builders shipping TS libraries, SaaS APIs, or multi-framework monorepos who want TypeDoc-grade reference plus ADRs in one workflow.
Skip if: Teams that only need marketing pages, non-TypeScript stacks, or documentation with zero JSDoc/TypeDoc toolchain.
When should I use this skill?
Creating API documentation, architectural decision records, code examples, or framework-specific patterns for NestJS, Express, React, Angular, or Vue.
What do I get? / Deliverables
You get validated JSDoc, generated API docs, maintainable ADRs, and an optional CI pipeline so documentation stays aligned with the code.
- TypeDoc or framework-aligned API documentation output
- JSDoc-annotated source and ADR markdown files
- ESLint JSDoc config and optional GitHub Actions doc workflow
Recommended Skills
Journey fit
Documentation is authored while the product is being built, before or alongside shipping public APIs and internal architecture records. The skill targets docs artifacts—TypeDoc output, JSDoc, ADRs, and examples—not runtime code or deploy pipelines.
How it compares
Use as a structured doc generator and ADR workflow instead of scattered README edits and ad-hoc comment blocks.
Common Questions / FAQ
Who is typescript-docs for?
Indie and solo developers building TypeScript backends or frontends who need API reference, inline JSDoc, and ADRs without hiring a tech writer.
When should I use typescript-docs?
During Build when creating API documentation, architectural decision records, code examples, or framework-specific doc patterns for NestJS, Express, React, Angular, or Vue.
Is typescript-docs safe to install?
Review the Security Audits panel on this Prism page and the skill’s allowed tools (Read, Write, Edit, Bash, Grep, Glob) before running doc pipelines in a sensitive repo.
SKILL.md
READMESKILL.md - Typescript Docs
# TypeScript Documentation Generate production-ready TypeScript documentation with layered architecture for multiple audiences. Supports API docs with TypeDoc, ADRs, and framework-specific patterns. ## Overview Use JSDoc annotations for inline documentation, TypeDoc for API reference generation, and ADRs for tracking design choices. **Key capabilities:** - TypeDoc configuration and API documentation generation - JSDoc patterns for all TypeScript constructs - ADR creation and maintenance - Framework-specific patterns (NestJS, React, Express, Angular, Vue) - ESLint validation rules for documentation quality - GitHub Actions pipeline setup ## When to Use Use this skill when creating API documentation, architectural decision records, code examples, or framework-specific patterns for NestJS, Express, React, Angular, or Vue. ## Quick Reference | Tool | Purpose | Command | |------|---------|---------| | TypeDoc | API documentation generation | `npx typedoc` | | Compodoc | Angular documentation | `npx compodoc -p tsconfig.json` | | ESLint JSDoc | Documentation validation | `eslint --ext .ts src/` | ### JSDoc Tags | Tag | Use Case | |-----|----------| | `@param` | Document parameters | | `@returns` | Document return values | | `@throws` | Document error conditions | | `@example` | Provide code examples | | `@remarks` | Add implementation notes | | `@see` | Cross-reference related items | | `@deprecated` | Mark deprecated APIs | ## Instructions ### 1. Configure TypeDoc ```bash npm install --save-dev typedoc typedoc-plugin-markdown ``` ```json { "entryPoints": ["src/index.ts"], "out": "docs/api", "theme": "markdown", "excludePrivate": true, "readme": "README.md" } ``` ### 2. Add JSDoc Comments ```typescript /** * Service for managing user authentication * * @remarks * Handles JWT-based authentication with bcrypt password hashing. * * @example * ```typescript * const authService = new AuthService(config); * const token = await authService.login(email, password); * ``` * * @security * - Passwords hashed with bcrypt (cost factor 12) * - JWT tokens signed with RS256 */ @Injectable() export class AuthService { /** * Authenticates a user and returns access tokens * @param credentials - User login credentials * @returns Authentication result with tokens * @throws {InvalidCredentialsError} If credentials are invalid */ async login(credentials: LoginCredentials): Promise<AuthResult> { // Implementation } } ``` ### 3. Create an ADR ```markdown # ADR-001: TypeScript Strict Mode Configuration ## Status Accepted ## Context What is the issue motivating this decision? ## Decision What change are we proposing? ## Consequences What becomes easier or more difficult? ``` ### 4. Set Up CI/CD Pipeline ```yaml name: Documentation on: push: branches: [main] paths: ['src/**', 'docs/**'] jobs: generate-docs: runs-on: ubuntu-latest steps: - uses: actions/checkout@v4 - uses: actions/setup-node@v4 with: node-version: '20' cache: 'npm' - run: npm ci - run: npm run docs:generate - run: npm run docs:validate ``` ### 5. Validate Documentation ```json { "rules": { "jsdoc/require-description": "error", "jsdoc/require-param-description": "error", "jsdoc/require-returns-description": "error", "jsdoc/require-example": "warn" } } ``` **If validation fails:** review ESLint errors, fix JSDoc comments (add missing descriptions, add `@param`/`@returns`/`@throws` where absent), re-run `eslint --ext .ts src/` until