thoughtbot/guides

A guide for programming in style.

View on GitHub ↗Jump to charts ↓

Summary Information

Updated 42 minutes ago
Added to GitGenius on September 6th, 2026
Created on July 27th, 2012
Open Issues & Pull Requests: 11 (+0)
GitHub issues: Enabled
Number of forks: 1,347
Total Stargazers: 9,560 (+0)
Total Subscribers: 337 (+0)

Repository Insights (GitGenius)

Median issue/PR response: N/A
Mean response time: 0.0 hours
90th percentile: 0.0 hours
Tracked items: 2

Charts & Analytics

Fetching additional details & charts...

Issue Activity (beta)

Open issues: 1
New in 7 days: 0
Closed in 7 days: 0
Avg open age: 159 days
Stale 30+ days: 1
Stale 90+ days: 1

Recent activity

Opened in 7 days: 0
Closed in 7 days: 0
Comments in 7 days: 0
Events in 7 days: 0

Top labels

No label distribution available yet.

Most active issues this week

No issue events were indexed in the last 7 days.

Detailed Description

Guides is a collection of programming style guides and best practices documentation.

The project addresses the need for consistent coding standards and collaborative practices across teams and projects. It provides structured guidance across multiple dimensions: programming languages, frameworks, collaboration protocols, and tools. The approach uses clear language conventions to distinguish between levels of recommendation, distinguishing "avoid" from "don't," and "prefer" from "use," so teams understand which guidelines are flexible versus absolute. The guides emphasize consistency within existing codebases over retroactive refactoring, and allow exceptions when teammates can be convinced of a good reason.

The guides span a broad range of technologies and practices, making them most useful for teams already working with the thoughtbot tech stack or seeking comprehensive guidance across multiple domains. The collection includes language-specific guides for Ruby, Python, JavaScript and TypeScript, Bash, CSS, Sass, HTML, ERB, Shell, and Swift; framework guides for Rails, React, React Native, Android, and iOS; protocol guides covering accessibility, data handling, email, object-oriented design, security, web standards, and web performance; and tool guides for Git, GraphQL, Postgres, and relational databases. Teams should adopt these guides if they value explicit, documented standards and want to reduce decision-making friction around code style and team practices.

The project operates with a deliberate review process: contributors with commit access are expected to wait a week before merging changes to allow time for team feedback. This reflects a commitment to consensus-building around guideline updates rather than rapid iteration. The guides are maintained as living documentation distributed under a Creative Commons Attribution License, indicating they are intended for broad reuse and adaptation.