Guidelines for writing effective JSDoc documentation
Use consistent formatting and style// Always use the same format for similar tags
// Good: @param {string} name - User name
// Good: @param {number} age - User ageDocument all public APIs// Document all parameters, return values, and exceptions
// Include examples for complex functionsWrite clear, concise descriptions// Good: Calculates user age from birth date
// Bad: Does age stuffAlways specify types for parameters and returns// Always include types
@param {string|null} name - User name or null
@returns {Promise<User>} Promise resolving to user objectInclude usage examples for complex functions/**
* @example
* // Basic usage
* const result = myFunction('input');
*
* @example
* // Advanced usage
* const result = myFunction('input', { option: true });
*/