Style guide
A written coding style or conventions guide for a language or team; not a linter configuration.
Repositories
18
Net stars gained, last 7 days
+155
Top-level Tag
Net stars gained each day, last 90 days
Largest
Most stars in total now.
readme:
Airbnb JavaScript Style Guide() {
readme:
more than 80 best practices, style guides, and architectural tips are presented
readme:
This is a set of common historical and emerging project layout patterns in the Go ecosystem.
description:
The C++ Core Guidelines are a set of tried-and-true guidelines, rules, and best practices about coding in C++
readme:
This project (google/styleguide) links to the style guidelines we use for Google code.
- alibaba/p3c31K
readme:
Alibaba Java Coding Guidelines which consolidates the best programming practices over the years from Alibaba Group's technical teams.
readme:
Here's a list of guidelines we've found, written and gathered that (we think) works really well with most JavaScript projects here at elsewhen.
readme:
The following sections outline a _reasonable_ style guide for modern JavaScript development and are not meant to be prescriptive.
readme:
If you are looking for an opinionated style guide for syntax, conventions, and structuring Angular applications, then step right in.
readme:
This repository contains a collection of documents and related materials supporting the overall Microsoft REST API Guidelines initiative.
How a repository gets this Tag
An agent reads the description, the GitHub topics, and the start of the README of each repository. It chooses Tags only from the Tag list in the AwesomeRepos source code. For each Tag, it quotes the text. A code check keeps the Tag only when the quote is in that text. The quote under each repository is that evidence. A Tag does not rank repositories. It does not say that one repository can replace another. To report a wrong Tag, use "Report a problem with this page" on the page of the repository. All numbers on this page count only visible repositories.