explaingit

kristories/awesome-guidelines

10,794JavaScriptAudience · developerComplexity · 1/5Setup · easy

TLDR

A curated collection of links to coding style guides and best-practice documents covering dozens of programming languages, frameworks, platforms, and development tools in one place.

Mindmap

mindmap
  root((repo))
    What It Does
      Links to style guides
      Covers best practices
      Organized by category
    Topics Covered
      Dozens of languages
      Popular frameworks
      Dev environments
      Version control
    Notable Guides
      Google style guides
      Airbnb JS guide
      Platform-specific docs
    Who Its For
      New project starters
      Team onboarding
      Best practice review
Click or tap to explore — scroll the page freely

Code map

Detail Auto

An interactive map of this repo's files and how they connect — its source is parsed live in your browser. Click Visualize to build it.

filefunction / class

Things people build with this

USE CASE 1

Find the official or community-recommended style guide for a programming language you are starting to use on a new project.

USE CASE 2

Onboard onto a new team by reviewing the naming, formatting, and structure conventions the broader community follows for your stack.

USE CASE 3

Check what formatting and project structure rules apply to a framework or platform such as Android or iOS before writing your first file.

Tech stack

JavaScript

Getting it running

Difficulty · easy Time to first run · 5min
License not mentioned in the explanation.

In plain English

Awesome Guidelines is a curated collection of links to coding style guides and best-practice documents across a wide range of programming languages, frameworks, and development tools. If you have ever needed to know what conventions a given language community recommends for naming variables, formatting code, or structuring a project, this list points you to those resources in one place. The collection is organized by category. The programming languages section covers dozens of languages, from common choices like Java, Python, Go, and JavaScript to less common ones like Brainfuck, Fortran, and Erlang. Each entry links to one or more official or community-maintained guides that describe how code in that language is typically written and why. Beyond individual languages, the list also covers development environment setup guides, platform-specific conventions for systems like Android and iOS, style guidelines for popular frameworks, and recommendations for content management systems. There is also a tools section with links to guidance on things like version control workflows and documentation practices. This kind of list is useful when you are starting a project in a language you have not used much, when you are joining an existing team and want to match their conventions, or when you want to review what the broader community considers good practice. The entries include both official sources from language designers and well-known community efforts, such as the Google style guides and the Airbnb JavaScript guide. The repository is part of the Awesome series, a broader GitHub tradition of community-maintained link collections on specific topics.

Copy-paste prompts

Prompt 1
I found a style guide in kristories/awesome-guidelines for Python. Here is a rule I don't understand: [paste rule]. Explain it in plain English and show me a before and after code example.
Prompt 2
Based on the Airbnb JavaScript guide linked in kristories/awesome-guidelines, help me rewrite this function to follow its naming and formatting conventions: [paste code].
Prompt 3
I'm starting an Android project. Using the Android style guide linked in kristories/awesome-guidelines as reference, what are the five most important naming and structure conventions I should follow from day one?
Prompt 4
I want to contribute a missing language guide to kristories/awesome-guidelines. Help me write a well-formatted markdown entry that fits the existing list style and links to the most authoritative source for that language.
Open on GitHub → Explain another repo

← kristories on gitmyhub — every repo by this author, as a profile.

Verify against the repo before relying on details.