agentleFS
Sign inStart free
testdino-hqtestdino-hq/google-styleguides-skills/SKILL.md

google-styleguides-skills

Skill15 starsChanged 9 months agoMITView on GitHub

Complete collection of Google's official style guides for 17 languages. Includes TypeScript, JavaScript, Python, Java, Go, C++, C#, Swift, Objective-C, HTML/CSS, AngularJS, Shell, R, Common Lisp, Vim Script, JSON, and Markdown. Production-ready coding standards used across Google's engineering organization, formatted for AI agent consumption.

The file

We split this skill into the rules it gives an agent

7 rules. About 0 are common, 7 are distinctive, and 0 are very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈7

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 0

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    Be consistent: - Follow language conventions

    line 77
  2. Distinctive:

    Be conventional: - Use established patterns

    line 79
  3. Distinctive:

    Automate it: - Use language-specific formatters

    line 82
  4. Distinctive:

    Follow standards: - Don't reinvent formatting rules

    line 84
  5. Distinctive:

    Handle errors: - Don't ignore error conditions

    line 93
  6. Distinctive:

    When you install this skill:

    line 98
  7. Distinctive:

    All content derived from Google's official style guides: https://google.github.io/styleguide/

    line 111

≈ “Common” is an estimate: at least 1 in 5 of the 350,495 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

Google 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:

  1. The style guides are copied to .kiro/skills/ in your project
  2. Your AI coding agent reads them when generating code
  3. 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/

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

Check your setup, free