bilingual-jsdoc

Generate bilingual Chinese and English JSDoc for exported TypeScript functions.

207|39|Updated Aug 29, 2017
One-click install
npx skills add https://github.com/MichealWayne/fe-tools --skill bilingual-jsdoc
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: bilingual-jsdoc
Source: https://github.com/MichealWayne/fe-tools/tree/main/utils/.cursor/skills/bilingual-jsdoc
Command: npx skills add https://github.com/MichealWayne/fe-tools --skill bilingual-jsdoc

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill helps teams maintain accurate, bilingual (Chinese + English) JSDoc for exported functions in fe-tools, ensuring accessible documentation for diverse developers.

Core Features & Use Cases

  • Bilingual JSDoc Generation: Create or update JSDoc with Chinese and English descriptions for parameters and return values.
  • Type-Safe Alignment: Ensures the JSDoc descriptions match the TypeScript function signature.
  • Use Case: When adding or modifying utilities, run this to generate consistent bilingual docs and keep codebase documentation up-to-date.

Quick Start

Provide bilingual JSDoc for the target exported function, including Chinese and English descriptions for each parameter and a corresponding returns description.

Frequently Asked Questions about bilingual-jsdoc

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

FAQPage Schema
How do I generate bilingual JSDoc comments for TypeScript exported functions?▼

Bilingual JSDoc generation adds Chinese and English descriptions to exported functions by matching the TypeScript signature, including @param lines with bilingual descriptions, a @returns description, and at least two usage examples.

What is the best way to keep JSDoc documentation aligned with TypeScript function signatures?▼

Type-safe JSDoc alignment ensures parameter descriptions and return values match the TypeScript function signature exactly, preventing documentation drift when updating or adding utility functions.

How do I add Chinese and English descriptions to JSDoc @param and @returns tags?▼

Add bilingual descriptions by writing both Chinese and English text for each @param tag and the @returns tag, ensuring the documentation covers diverse developers reading the utility exports.

Does bilingual JSDoc generation require examples for both normal and edge cases?▼

Yes, bilingual JSDoc requires at least two examples illustrating normal usage and edge cases, ensuring the documentation demonstrates practical behavior for each exported function.

Can I use this JSDoc approach for existing functions or only new utility exports?▼

Bilingual JSDoc applies to both new utilities and existing exported functions, covering documentation updates, fixes, and additions across fe-tools modules to keep the codebase documentation current.

When do I need bilingual JSDoc for a TypeScript utility library?▼

Bilingual JSDoc is needed when maintaining accessible documentation for diverse developers across fe-tools modules, ensuring exported functions have consistent Chinese and English descriptions during updates or additions.