Awesome Guidelines — curated style guides for every language

reference Sat Jul 04 2026 00:00:00 GMT+0000 (Coordinated Universal Time) referencestyle-guidecoding-conventionslanguagesexternal

Awesome Guidelines — external reference

Curated links list. Nothing copied here — this file is a pointer.

Upstream

Repo: Kristories/awesome-guidelines
Raw README: https://raw.githubusercontent.com/Kristories/awesome-guidelines/main/README.md
License: CC0-1.0 (public domain)
Maintainer: Wahyu Kristianto (@Kristories)
Health: 10.9k stars, actively maintained (updated 2026-05-28)

Categories (upstream sections)

Category	What it covers
Programming Languages	60+ languages: C, C++, C#, Clojure, Dart, Elixir, F#, Go, Groovy, Haskell, Java, JavaScript, Kotlin, Lisp, Objective-C, Perl, PHP, PowerShell, Python, R, Ruby, Rust, Scala, Shell, SQL, Swift, TypeScript, Visual Basic, and more
Development Environment	IDE + editor conventions, git commit-message guidelines, changelog formats
Platforms	iOS, Android, Web, cross-platform mobile
Frameworks	Angular, React, Vue, Rails, Django, Spring, .NET, Symfony, Laravel, and more
Content Management System	WordPress, Drupal, Joomla
Tools	Editor config, EditorConfig, Docker, Kubernetes, terminal, shell

Fetch pattern (on-demand, zero-copy)

Agents fetch when needed:

# Full README
curl -fsSL https://raw.githubusercontent.com/Kristories/awesome-guidelines/main/README.md

# Or via mcp__fetch__fetch (MCP tool)
mcp__fetch__fetch(url="https://raw.githubusercontent.com/Kristories/awesome-guidelines/main/README.md")

For a specific language section, grep the fetched content:

curl -fsSL https://raw.githubusercontent.com/Kristories/awesome-guidelines/main/README.md \
  | awk '/^### Python/,/^###/' | head -30

When to reach for this

User asks "what's the style guide for X" (Python, Rust, Go, etc.)
Before writing code in an unfamiliar language, especially for a public repo
Reviewing a PR in a language where our own house style is silent
Choosing between multiple community style guides for the same language

Cross-refs

match-surrounding-style — when the repo already has a style, match it; use upstream guidelines only when the repo is silent
use-language-style-guides-before-writing — the rule that mandates checking this pointer

Why zero-copy

Upstream is authoritative + evolves — copying at 2026-07-04 means our copy rots the next time a language's canonical guide moves
CC0 doesn't require copying — it permits, doesn't mandate, redistribution
Repo bloat — the README is ~600 lines of links; copying adds no value vs curl
Agent-friendly — MCP fetch tool + okf-prompt-lookup.ts surfacing this pointer means agents find + fetch in one turn