Sonarjs
managedcode/dotnet-skills
Use SonarJS-derived rules in .NET repositories that ship JavaScript or TypeScript frontends and need deeper bug-risk, code-smell, or cognitive-complexity checks than a minimal ESLint baseline.
JavaScript style and best practices based on Google's official JavaScript Style Guide.
Install JS Google
$ npx skills add pproenca/dot-skills --skill js-google -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install pproenca/dot-skills js-google --agent claude-codeProject scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).
$ git clone --depth 1 https://github.com/pproenca/dot-skills.git skills-src && mkdir -p .claude/skills && cp -r skills-src/skills/.experimental/js-google .claude/skills/js-google && rm -rf skills-srcUse ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.
Claude Code skills documentation · loads skills from .claude/skills/
Install the "js-google" agent skill from https://github.com/pproenca/dot-skills/tree/master/skills/.experimental/js-google into .claude/skills/js-google/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "js-google", then confirm the skill loads.Claude Code copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$skill-installer install https://github.com/pproenca/dot-skills/tree/master/skills/.experimental/js-googleType this inside Codex. $skill-installer <name> installs a curated skill from openai/skills. The installer writes to $CODEX_HOME/skills (default ~/.codex/skills). Restart Codex if the skill does not show up.
$ npx skills add pproenca/dot-skills --skill js-google -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install pproenca/dot-skills js-google --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/pproenca/dot-skills.git skills-src && mkdir -p .agents/skills && cp -r skills-src/skills/.experimental/js-google .agents/skills/js-google && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "js-google" agent skill from https://github.com/pproenca/dot-skills/tree/master/skills/.experimental/js-google into .agents/skills/js-google/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "js-google", then confirm the skill loads.Codex copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add pproenca/dot-skills --skill js-google -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install pproenca/dot-skills js-google --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/pproenca/dot-skills.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/skills/.experimental/js-google .cursor/skills/js-google && rm -rf skills-srcUse ~/.cursor/skills/ instead of .cursor/skills for a personal install.
Cursor skills documentation · loads skills from .cursor/skills/, .agents/skills/, .claude/skills/, .codex/skills/
Install the "js-google" agent skill from https://github.com/pproenca/dot-skills/tree/master/skills/.experimental/js-google into .cursor/skills/js-google/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "js-google", then confirm the skill loads.Cursor copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gemini skills install https://github.com/pproenca/dot-skills.git --path skills/.experimental/js-google--scope user (default) or --scope workspace; --path is the subfolder of the repo that holds the skill; --consent skips the security confirmation prompt.
$ npx skills add pproenca/dot-skills --skill js-google -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install pproenca/dot-skills js-google --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/pproenca/dot-skills.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/skills/.experimental/js-google .gemini/skills/js-google && rm -rf skills-srcUse ~/.gemini/skills/ instead of .gemini/skills for a personal install, then run /skills reload.
Gemini CLI skills documentation · loads skills from .gemini/skills/, .agents/skills/
Install the "js-google" agent skill from https://github.com/pproenca/dot-skills/tree/master/skills/.experimental/js-google into .gemini/skills/js-google/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "js-google", then confirm the skill loads.Gemini CLI copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gh skill install pproenca/dot-skills js-googleInstalls for Copilot at project scope by default; add --scope user for a personal install. Preview a skill first with gh skill preview. Needs GitHub CLI 2.90.0 or later (public preview).
$ npx skills add pproenca/dot-skills --skill js-google -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/pproenca/dot-skills.git skills-src && mkdir -p .github/skills && cp -r skills-src/skills/.experimental/js-google .github/skills/js-google && rm -rf skills-srcUse ~/.copilot/skills/ instead of .github/skills for a personal install. Commit .github/skills so cloud agent and code review can use it.
GitHub Copilot skills documentation · loads skills from .github/skills/, .claude/skills/, .agents/skills/
Install the "js-google" agent skill from https://github.com/pproenca/dot-skills/tree/master/skills/.experimental/js-google into .github/skills/js-google/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "js-google", then confirm the skill loads.GitHub Copilot copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add pproenca/dot-skills --skill js-google -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install pproenca/dot-skills js-google --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/pproenca/dot-skills.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/skills/.experimental/js-google .opencode/skills/js-google && rm -rf skills-srcUse ~/.config/opencode/skills/ instead of .opencode/skills for a personal install.
OpenCode skills documentation · loads skills from .opencode/skills/, .claude/skills/, .agents/skills/
Install the "js-google" agent skill from https://github.com/pproenca/dot-skills/tree/master/skills/.experimental/js-google into .opencode/skills/js-google/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "js-google", then confirm the skill loads.OpenCode copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
Facts
- Skill name
js-google- GitHub stars
- 214
- Token cost
- ~2k tokens
- SKILL.md length
- 526 words
- Files
- 53 (incl. references, assets)
- Skills in repo
- 182
- Repo updated
- First seen
- Licence
- MIT
At a glance
JavaScript style and best practices based on Google's official JavaScript Style Guide.
- Works in 8 steps: Module System & Imports (CRITICAL) → Language Features (CRITICAL) → Type Safety & JSDoc (HIGH) → …
- Tasks involving JavaScript
- SKILL.md covers When to Apply, Rule Categories by Priority, Quick Reference and How to Use, plus 2 more sections
- Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md
What it does
JS Google is an agent skill from pproenca/dot-skills. JavaScript style and best practices based on Google's official JavaScript Style Guide. This skill should be used when writing, reviewing, or refactoring JavaScript code to ensure consistent style and prevent common bugs. Triggers on tasks involving JavaScript, ES6, modules, JSDoc, naming conventions, or code formatting.
Its SKILL.md is about 2k tokens, which your agent loads only when the skill is triggered. The skill folder holds 55 other files, including reference files and assets (for example `AGENTS.md`, `README.md` and `assets/templates/_template.md`).
It sits in Development, covering Technical documentation, Linting and formatting and Refactoring. It works with JavaScript. The repository describes itself as: A collection of AI agent skills following the Agent Skills open format. The licence is MIT.
When your agent uses it
- Tasks involving JavaScript
- Naming conventions
- Code formatting
Example prompts
- “/js-google”
Workflow steps
8 steps, taken from the step headings in SKILL.md.
What it can do on your machine
Read from SKILL.md and the folder at commit cf93c57. It shows what the files ask for, not the result of running them.
Tool permissions
Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.
From allowed-tools in the SKILL.md frontmatter.
Runs code
No scripts in the folder and no shell commands in SKILL.md.
From the folder's file list and the shell code blocks in SKILL.md.
Network
No URLs in SKILL.md.
From URLs in SKILL.md, links to its own repository left out.
Credentials
Names no API keys, tokens, secrets or passwords.
From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.
Context cost
JS Google loads about 2k tokens when it runs, and up to ~21k if it reads all its reference files. Until then it costs about 83 tokens; SKILL.md has 526 words of instructions outside code blocks.
Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.
Safety
Auto-check passed
The automated check found no risky patterns in SKILL.md.
Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.
SKILL.md
The full file from pproenca/dot-skills at commit cf93c57, republished under its MIT licence (© pproenca). 526 words, ~1,999 tokens.
Download SKILL.mdSave it as
.claude/skills/js-google/SKILL.md (or your agent's skills folder). This skill also uses 52 other files; get the full folder from GitHub.- name
- js-google
- description
- JavaScript style and best practices based on Google's official JavaScript Style Guide. This skill should be used when writing, reviewing, or refactoring JavaScript code to ensure consistent style and prevent common bugs. Triggers on tasks involving JavaScript, ES6, modules, JSDoc, naming conventions, or code formatting.
Google JavaScript Best Practices
Comprehensive JavaScript style and best practices guide based on Google's official JavaScript Style Guide, designed for AI agents and LLMs. Contains 47 rules across 8 categories, prioritized by impact to guide automated refactoring and code generation.
When to Apply
Reference these guidelines when:
- Writing new JavaScript or ES6+ code
- Structuring modules and managing imports/exports
- Adding JSDoc type annotations and documentation
- Reviewing code for naming and style consistency
- Refactoring existing JavaScript code
Rule Categories by Priority
| Priority | Category | Impact | Prefix |
|---|---|---|---|
| 1 | Module System & Imports | CRITICAL | module- |
| 2 | Language Features | CRITICAL | lang- |
| 3 | Type Safety & JSDoc | HIGH | type- |
| 4 | Naming Conventions | HIGH | naming- |
| 5 | Control Flow & Error Handling | MEDIUM-HIGH | control- |
| 6 | Functions & Parameters | MEDIUM | func- |
| 7 | Objects & Arrays | MEDIUM | data- |
| 8 | Formatting & Style | LOW | format- |
Quick Reference
1. Module System & Imports (CRITICAL)
module-avoid-circular-dependencies- Prevent loading failures from circular importsmodule-file-extension-in-imports- Include .js extension in import pathsmodule-named-exports-over-default- Prefer named exports for consistencymodule-no-duplicate-imports- Import from same file only oncemodule-no-import-aliasing- Keep original export namesmodule-source-file-structure- Follow standard file structure order
2. Language Features (CRITICAL)
lang-const-over-let-over-var- Use const by default, never varlang-es6-classes-over-prototypes- Use class syntax over prototype manipulationlang-explicit-semicolons- Always use explicit semicolonslang-no-eval- Never use eval or Function constructorlang-no-modify-builtins- Never modify built-in prototypeslang-no-non-standard-features- Use only standard ECMAScript featureslang-no-primitive-wrappers- Never use primitive wrapper objectslang-no-with-statement- Never use the with statement
3. Type Safety & JSDoc (HIGH)
type-cast-with-parentheses- Use parentheses for type caststype-enum-annotations- Annotate enums with static literal valuestype-explicit-nullability- Use explicit nullability modifierstype-jsdoc-required-for-exports- Require JSDoc for exported functionstype-template-parameters- Always specify template parameterstype-typedef-for-complex-types- Use typedef for complex object types
4. Naming Conventions (HIGH)
naming-constant-case-for-constants- Use CONSTANT_CASE for immutable valuesnaming-descriptive-over-brief- Prefer descriptive names over brevitynaming-file-naming-conventions- Use lowercase with dashes or underscoresnaming-lowercamelcase-for-methods- Use lowerCamelCase for methods and variablesnaming-no-dollar-prefix- Avoid dollar sign prefix in identifiersnaming-uppercamelcase-for-classes- Use UpperCamelCase for classes
Show full SKILL.md (218 more words)Show less
5. Control Flow & Error Handling (MEDIUM-HIGH)
control-comment-empty-catch- Document empty catch blockscontrol-for-of-over-for-in- Prefer for-of over for-incontrol-strict-equality- Use strict equality except for null checkscontrol-switch-default-last- Always include default case in switchcontrol-throw-error-objects- Always throw Error objects
6. Functions & Parameters (MEDIUM)
func-arrow-functions-for-nested- Prefer arrow functions for nested functionsfunc-arrow-parentheses- Always use parentheses around arrow paramsfunc-default-parameters- Use default parameters instead of conditionalsfunc-rest-parameters-over-arguments- Use rest parameters over argumentsfunc-spread-over-apply- Use spread operator instead of apply
7. Objects & Arrays (MEDIUM)
data-array-literals-over-constructor- Use array literals over Array constructordata-destructuring-for-multiple-values- Use destructuring for multiple propertiesdata-no-mixing-quoted-unquoted-keys- Never mix quoted and unquoted keysdata-object-literals-over-constructor- Use object literals over constructordata-spread-over-concat-slice- Use spread over concat and slicedata-trailing-commas- Use trailing commas in multi-line literals
8. Formatting & Style (LOW)
format-braces-required- Always use braces for control structuresformat-column-limit- Limit lines to 80 charactersformat-one-statement-per-line- Place one statement per lineformat-single-quotes- Use single quotes for string literalsformat-two-space-indent- Use two-space indentation
How to Use
Read individual reference files for detailed explanations and code examples:
- Section definitions - Category structure and impact levels
- Rule template - Template for adding new rules
Full Compiled Document
For a complete compiled guide with all rules, see AGENTS.md.
Reference Files
| File | Description |
|---|---|
| AGENTS.md | Complete compiled guide with all rules |
| references/_sections.md | Category definitions and ordering |
| assets/templates/_template.md | Template for new rules |
| metadata.json | Version and reference information |
© pproenca, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file
Files
SKILL.md and 52 other files (references, assets) in skills/.experimental/js-google of pproenca/dot-skills.
- SKILL.md
- AGENTS.md
- README.md
- assets/templates/_template.md
- metadata.json
- references/_sections.md
- references/control-comment-empty-catch.md
- references/control-for-of-over-for-in.md
- references/control-strict-equality.md
- references/control-switch-default-last.md
- references/control-throw-error-objects.md
- references/data-array-literals-over-constructor.md
- references/data-destructuring-for-multiple-values.md
- references/data-no-mixing-quoted-unquoted-keys.md
- references/data-object-literals-over-constructor.md
- references/data-spread-over-concat-slice.md
- references/data-trailing-commas.md
- references/format-braces-required.md
- … and 35 more
Open the folder on GitHubat commit cf93c57
Compare with similar skills
JS Google next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.
| Skill | Stars | Used in | Tokens | Auto-check | Licence | Repo updated |
|---|---|---|---|---|---|---|
| JS Google this skillpproenca/dot-skills | 214 | — | ~2k | Automated safety check: Pass | MIT | |
| Sonarjsmanagedcode/dotnet-skills | 486 | — | ~1.6k | Automated safety check: Pass | MIT | |
| Install Anti-Slop Oxlint Rulesdmmulroy/anti-slop | 5.2k | — | ~2.2k | Automated safety check: Pass | MIT | |
| Rust Best Practicesfarm-fe/farm | 5.6k | 3 repos | ~1.1k | Automated safety check: Pass | MIT | |
| WooCommerce Markdown Guidelineswoocommerce/woocommerce | 11k | 1 repos | ~1.7k | Automated safety check: Pass | Custom licence | |
| Dinero Best Practicesdinerojs/dinero.js | 6.8k | — | ~756 | Automated safety check: Pass | MIT |
Similar skills
Install Anti-Slop Oxlint Rules
dmmulroy/anti-slop
Installs, updates or migrates the vendored anti-slop Oxlint plugin in a repository, keeping local rule changes and the plugin's license and provenance files.
Rust Best Practices
farm-fe/farm
Guide for writing idiomatic Rust code based on Apollo GraphQL's best practices handbook.
WooCommerce Markdown Guidelines
woocommerce/woocommerce
Rules for writing and editing markdown in the WooCommerce repository, with the project's markdownlint settings for headings, lists and code blocks.
Dinero Best Practices
dinerojs/dinero.js
Core best practices for the Dinero.js money library. An agent skill from dinerojs/dinero.js.
Ultracite
agustinusnathaniel/nextarter-tailwind
Ultracite is a zero-config linting and formatting preset for JavaScript/TypeScript projects.
More from pproenca/dot-skills
All 182 skills in this repoAudio Voice Recovery
pproenca/dot-skills
Audio forensics and voice recovery guidelines for CSI-level audio analysis.
Codemod React Pipeline
pproenca/dot-skills
Guided, scripted pipeline for running JSX/TSX/React codemods safely across large legacy codebases.
Dev Rfc
pproenca/dot-skills
Create well-structured RFCs and technical proposals for software projects.
Dx Harness
pproenca/dot-skills
Developer-experience friction auditing and fixing — slow onboarding, repeated manual setup steps, missing bootstrap/reset/seed scripts, undiscoverable conventions.
Language Spec Author
pproenca/dot-skills
Turn a rough idea for a language into a complete, implementable specification — a DSL, query, config/data, template, or protocol language — by interviewing the author dimension by dimension until…
Python Pep Author
pproenca/dot-skills
Drafting Python Enhancement Proposals (PEPs) — proposing a Python language feature, a standard library change, an interoperability standard, or an informational/process document for the Python…
Related
Works with
Categories
Questions about JS Google
What does JS Google do?
JavaScript style and best practices based on Google's official JavaScript Style Guide. JS Google is an agent skill from pproenca/dot-skills. JavaScript style and best practices based on Google's official JavaScript Style Guide.
When should I use JS Google?
JS Google fits situations like: tasks involving JavaScript; naming conventions; code formatting.
How do I install JS Google in Claude Code?
Run `npx skills add pproenca/dot-skills --skill js-google -a claude-code`. Or copy the skill folder (skills/.experimental/js-google in pproenca/dot-skills) into .claude/skills/js-google in your project. Claude Code loads it when a task matches its description.
How do I install JS Google in Codex?
Run `npx skills add pproenca/dot-skills --skill js-google -a codex`. Or copy the skill folder (skills/.experimental/js-google in pproenca/dot-skills) into .agents/skills/js-google in your project. Codex loads it when a task matches its description.
Can I use JS Google in Cursor, Gemini CLI or GitHub Copilot?
Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add pproenca/dot-skills --skill js-google -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/js-google, .gemini/skills/js-google, .github/skills/js-google and .opencode/skills/js-google in your project.
What does JS Google need to run?
SKILL.md names no scripts, command-line tools or credentials: JS Google is instructions for the agent only.
Does JS Google access the network?
SKILL.md contains no URLs. Any network use would come from the scripts or tools the agent runs. This is read from the text; nothing was executed.
Is JS Google safe to install?
Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.
What licence does JS Google use?
JS Google is published under the MIT licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.
How many tokens does JS Google use?
About 2k tokens (SKILL.md is roughly 8k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full. Its references folder adds about 19k tokens, read only when the agent opens those files.
What are the alternatives to JS Google?
Skills that share tags, products or a category with JS Google: Sonarjs (managedcode/dotnet-skills, 486 stars), Install Anti-Slop Oxlint Rules (dmmulroy/anti-slop, 5.2k stars), Rust Best Practices (farm-fe/farm, 5.6k stars) and WooCommerce Markdown Guidelines (woocommerce/woocommerce, 11k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains JS Google?
pproenca (a GitHub user) maintains it in pproenca/dot-skills, which has 214 GitHub stars. The repository holds 182 skills in this directory. The repository was last updated on August 15, 2026.
Source: pproenca/dot-skills on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.