What problem does it solve? Maintaining legacy JavaScript codebases consistently is hard when contributors apply different formatting, naming, and module conventions. This Skill gives an agent the authoritative Google JavaScript Style Guide rules so it can write and review code that matches Google's conventions without guessing. ## Core Features & Use Cases - Formatting and structure rules: Enforces 80-column limits, 2-space indentation, required semicolons and braces, trailing commas, and line-wrapping conventions. - Module and language-feature guidance: Covers ES modules vs goog.module, named exports, import path extensions, const/let usage, arrow functions, and forbidden features like eval and prototype manipulation. - Naming and JSDoc conventions: Defines UpperCamelCase, lowerCamelCase, and CONSTANT_CASE naming plus JSDoc type annotations, nullability modifiers, and visibility annotations. - Use Case: When refactoring an old JavaScript file in a repository that follows Google style, ask the agent to update the code so declarations, imports, and JSDoc comments all comply with the guide. ## Quick Start Review this JavaScript file and rewrite it to comply with the Google JavaScript Style Guide, fixing formatting, naming, and JSDoc annotations.
