Sign in

Tags / Lists and learning /

Design patterns

Explanations or example code of software design patterns or architecture patterns.

Repositories

14

Net stars gained, last 7 days

+189

Top-level Tag

Lists and learning

Net stars gained each day, last 90 days

2026-08-26: +174 net stars. Most from nilbuild/design-patterns-for-humans, +124.2026-08-27: +162 net stars. Most from nilbuild/design-patterns-for-humans, +114.2026-09-17: +368 net stars. Most from humanlayer/12-factor-agents, +342.

Peak days

  1. 1

    Aug 26, 2026 +174 net stars (median day +49)

  2. 2

    Aug 27, 2026 +162 net stars (median day +49)

  3. 3

    Sep 17, 2026 +368 net stars (median day +49)

A peak day has at least 2 times the net stars of the median day of this chart, and at least 100 more. For each peak day, the list shows the repositories that gained the most net stars that day. It also shows their GitHub releases of that day or the day before (UTC), and their creation date when it was 14 days or less before. These events occur near the same day. They do not show why the stars came.

Largest

Most stars in total now.

  1. readme: Design patterns are the best, formalized practices a programmer can use to solve common problems when designing an application or system.

  2. description: Ultra-simplified explanation to design patterns!

  3. readme: These samples showcase different architectural approaches to developing Android apps.

  4. readme: A collection of design patterns and idioms in Python.

  5. readme: A curated collection of idiomatic design & application patterns for Go language.

  6. readme: Factor 12: Make your agent a stateless reducer

  7. readme: This project is an example of how the popular FizzBuzz game might be built were it subject to the high quality standards of enterprise software.

  8. readme: This is a collection of known design patterns and some sample codes on how to implement them in PHP.

  9. readme: A starting point for Clean Architecture with ASP.NET Core.

  10. readme: A compilation of React Patterns, techniques, tips and tricks.

All 14 in the Repository Index

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.