sdcorejs-comment-code

To stop excessive comments in TypeScript code, use a comment insertion gate that forces the AI to ask for a comment level before writing. Choosing 'skip' or 'simple' prevents unnecessary code bloat while maintaining readable files.

The best way to enforce JSDoc conventions in an AI workflow is to apply deterministic JSDoc rules based on a user-selected comment level. This ensures consistent inline 'why' explanations and documentation density across Angular, NestJS, or Next.js projects.

Yes, you can control AI documentation density for NestJS modules by triggering a mandatory comment level prompt. You can select 'medium' for standard JSDoc or 'full' to generate companion WHY-X.md files and test invariants.

Comment levels for different documentation needs include 'skip' for no comments, 'simple' for basic inline notes, 'medium' for standard JSDoc, and 'full' for rich JSDoc, design rationale documentation, and test invariants.

You should use full code commenting instead of simple inline comments when you need to document non-obvious module decisions, generate design rationale files, and establish test invariants for complex Angular Portal, NestJS, or Next.js tasks.

Yes, the comment insertion gate supports bilingual prompts aligned to the session language. It can present the 'skip', 'simple', 'medium', and 'full' options in either English or Vietnamese before applying JSDoc conventions.