agentleFS
Alice39sAlice39s/agent-stash/skills/code-styleguide/SKILL.md

code-styleguide

Skill20 starsChanged 21 days agoApache-2.0View on GitHub

Google, Angular, and Android Kotlin style guides synced from upstream, covering Common Lisp, C++, C#, Go, Haskell, HTML/CSS, JavaScript, Java, JSON, Markdown, Objective-C, Python, R, Rust, Shell, TypeScript, Verilog, Vim script, XML Document Format, Angular, Kotlin. Use when writing, reviewing, refactoring, or formatting code that should follow one of these guides, or when the user asks about naming, formatting, comments, imports, or language-feature rules in these languages.

The file

We split this skill into the rules it gives an agent

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

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈2

    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:

    Read its index (the line range in the Index column).

    line 16
  2. Distinctive:

    Read only the sections you need, starting at those lines.

    line 17

≈ “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

Code style guides

Each reference is one upstream guide converted to Markdown. Load only what the task needs:

  1. Pick the reference for the language or framework below.
  2. Read its index (the line range in the Index column). Each entry gives the line where a section starts.
  3. Read only the sections you need, starting at those lines.

Code fences tagged good show recommended code; fences tagged bad show code to avoid. The project's own configuration, formatter, and surrounding code take precedence over these guides.

TopicReferenceIndexLines
Common LispGoogle Common Lisp Style Guide1-551215
C++Google C++ Style Guide1-1193658
C#C# at Google Style Guide1-37493
GoGo Style1-10120
GoGo Style Best Practices1-612862
GoGo Style Decisions1-772629
GoGo Style Guide1-18273
HaskellGoogle's Haskell Style Guide1-41702
HTML/CSSGoogle HTML/CSS Style Guide1-19907
JavaScriptGoogle JavaScript Style Guide1-703134
JavaGoogle Java Style Guide1-41931
JSONGoogle JSON Style Guide1-771316
MarkdownMarkdown style guide1-37716
Objective-CGoogle Objective-C Style Guide1-771735
PythonGoogle Python Style Guide1-482399
RGoogle's R Style Guide1-17110
RustRust Style Guide1-851243
ShellShell Style Guide1-511074
TypeScriptTS/JS Style Guide1-643205
VerilogGoogle Verilog Style Guide1-1264222
Vim scriptGoogle Vimscript Style Guide1-29273
XML Document FormatGoogle XML Document Format Style Guide1-23233
AngularAngular coding style guide1-34299
KotlinKotlin style guide1-16888

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.