documentation-standards

To enforce Python docstring standards, mandate Google-style docstrings for all functions, ensuring they explain the 'why' behind the logic, not just the 'what'. This approach maintains consistent documentation rules during code reviews.

Standardizing JSDoc comments requires enforcing specific formats for JavaScript and TypeScript files to explain code purpose clearly. This approach differentiates between explaining why code exists versus what it does.

Maintaining .AGENTS.md files involves keeping project artifacts up-to-date and mandating the use of relative paths for internal linking. This skill provides specific guidance on artifact maintenance to ensure project standards are consistently applied.

Yes, this documentation standard works for both Python and JavaScript projects by enforcing Google-style Python docstrings and JSDoc for JavaScript/TypeScript. It ensures comprehensive documentation quality across multiple languages within a single team workflow.

Code comments should explain the why because understanding the reasoning behind specific logic prevents future errors and maintains codebase clarity. This standard enforces comment guidelines that differentiate between explaining why code exists versus what it does.