About google-styleguides-skills
A skill pack of Google's official style guides for 17 programming and markup languages, intended for AI coding agents. It places the guides in a project so agents can consult them while generating code.
Key features
- 01Style guides for 17 languages
- 02Frontend, backend, and mobile coverage
- 03Guidance on naming and formatting
- 04Documentation and code-quality guidance
- 05Install the full pack or individual guides
Use cases
- 01Applying Google style conventions in generated code
- 02Checking naming and formatting practices
- 03Consulting language-specific documentation guidance
Install
Copy the command and run it in a terminal.
npx skills add https:/ / github.com/ testdino-hq/ google-styleguides-skills --skill google-styleguides-skillsAfter installing, type/google-styleguides-skillsin Claude Code to confirm it loaded.
Bundled files
References and scripts installed along with SKILL.md.
LICENSEREADME.mdangularjs/angularjs.mdcommon-lisp/common-lisp.mdcpp/cpp.mdcsharp/csharp.mdgo/go.mdhtml-css/html-css.mdjava/java.mdjavascript/javascript.mdjson/json.mdmarkdown/markdown.mdobjective-c/objective-c.mdpython/python.mdr/r.mdshell/shell.mdswift/swift.mdtypescript/typescript.mdvim-script/vim-script.mdDetails
From the project READMEGoogle Style Guides
Official Google style guides for 17 languages — packaged for AI coding agents.
This skill pack includes all 17 official Google style guides from https://google.github.io/styleguide/
Included Style Guides
Frontend
- TypeScript - Types, interfaces, naming, null handling, enums, imports
- JavaScript - ES6+, modules, naming, formatting, JSDoc
- HTML/CSS - Formatting, naming, semantics, accessibility
- AngularJS - Controllers, services, directives, modules
Backend
- Python - PEP 8, type hints, docstrings, imports, comprehensions
- Java - Naming, formatting, Javadoc, exceptions, best practices
- Go - Formatting, naming, comments, error handling, concurrency
- C++ - Headers, naming, formatting, classes, memory management
- C# - Naming, formatting, LINQ, async/await, XML docs
Mobile
- Swift - Naming, optionals, protocols, error handling, formatting
- Objective-C - Naming, formatting, memory management, protocols
Other
- Shell - Bash scripting, naming, error handling, portability
- R - Naming, formatting, functions, documentation
- Common Lisp - Naming, formatting, macros, documentation
- Vim Script - Plugin structure, naming, portability
- JSON - Formatting, naming, structure, comments
- Markdown - Formatting, structure, links, lists
Installation Options
Install Everything (This Skill)
npx skills add testdino-hq/google-styleguides-skills
Install Individual Languages
# Frontend
npx skills add testdino-hq/google-styleguides-skills/typescript
npx skills add testdino-hq/google-styleguides-skills/javascript
npx skills add testdino-hq/google-styleguides-skills/html-css
npx skills add testdino-hq/google-styleguides-skills/angularjs
# Backend
npx skills add testdino-hq/google-styleguides-skills/python
npx skills add testdino-hq/google-styleguides-skills/java
npx skills add testdino-hq/google-styleguides-skills/go
npx skills add testdino-hq/google-styleguides-skills/cpp
npx skills add testdino-hq/google-styleguides-skills/csharp
# Mobile
npx skills add testdino-hq/google-styleguides-skills/swift
npx skills add testdino-hq/google-styleguides-skills/objective-c
# Other
npx skills add testdino-hq/google-styleguides-skills/shell
npx skills add testdino-hq/google-styleguides-skills/r
npx skills add testdino-hq/google-styleguides-skills/common-lisp
npx skills add testdino-hq/google-styleguides-skills/vim-script
npx skills add testdino-hq/google-styleguides-skills/json
npx skills add testdino-hq/google-styleguides-skills/markdown
Golden Rules Across All Languages
Naming
- Be consistent - Follow language conventions
- Be descriptive - Clarity over brevity
- Be conventional - Use established patterns
Formatting
- Automate it - Use language-specific formatters
- Be consistent - Same style across the codebase
- Follow standards - Don't reinvent formatting rules
Documentation
- Document public APIs - Help users understand interfaces
- Explain why, not what - Code shows what, comments explain why
- Keep it updated - Outdated docs are worse than no docs
Code Quality
- Prefer clarity - Readable code over clever code
- Handle errors - Don't ignore error conditions
- Test your code - Automated tests catch regressions
How It Works
When you install this skill:
- The style guides are copied to
.kiro/skills/in your project - Your AI coding agent reads them when generating code
- Generated code follows Google's official style conventions automatically
License
This project is licensed under the MIT License.
Copyright (c) 2026 TestDino
Source
All content derived from Google's official style guides:
https://google.github.io/styleguide/