jsdoc-authoring

Structure and content rules for JSDoc and TSDoc comments and the inline comments beside them, in JavaScript and TypeScript. Use whenever the task involves such a comment — writing one, editing or rewriting an existing one, reviewing or critiquing one, deciding whether a declaration needs one, or comparing two versions. Covers the four content slots and their order, where the summary section ends, the one rule that inverts between TypeScript and checked JavaScript (a type in a tag is noise in one and code in the other), {@link} and what actually checks it, which tags earn their line, comments a tool rather than a human reads (@ts-expect-error, eslint-disable-next-line, #__PURE__, release tags), how far a rewrite may grow, why a list of members should usually be the rule that defines them, and the extra rules for tests, module docs, and a comment that ships in a .d.ts. A one-line comment is in scope. Wording is governed by english-developer-style, which this skill defers to and does not replace.