awesome-repositories.com
© 2026 Bringes Technology SRL·VAT RO45896025·hello@bringes.io
MCPSitemapPrivacyTerms
SOLID Principles · Awesome GitHub Repositories

1 repo

Awesome GitHub RepositoriesSOLID Principles

Core object-oriented design guidelines that define how classes and interfaces should be structured to ensure maintainability and extensibility.

Explore 1 awesome GitHub repository matching software engineering & architecture · SOLID Principles. Refine with filters or upvote what's useful.

  1. Home
  2. Software Engineering & Architecture
  3. Software Architecture
  4. Foundational Theory and Guidance
  5. Software Architecture Principles
  6. SOLID Principles

Awesome SOLID Principles GitHub Repositories

Describe the repository you're looking for…
We'll search the best matching repositories with AI.
  • iluwatar/java-design-patterns

    iluwatar/java-design-patterns

    93,757GitHubView on GitHub↗

    This project is a comprehensive educational knowledge base designed to help developers master software engineering excellence through a structured catalog of design patterns and architectural principles. It provides a curated repository of best practices, programming heuristics, and implementation examples, all organiz

    Clarifies how to ensure subclasses remain interchangeable with superclasses without breaking program correctness.

    Javaawesome-listdesign-patternshacktoberfest

Explore sub-tags

  • Interface Segregation PrinciplesDesign principle focused on splitting large, monolithic interfaces into smaller, client-specific interfaces to reduce unnecessary dependencies.
  • Liskov Substitution PrinciplesDesign principle requiring that objects of a superclass must be replaceable with objects of its subclasses without altering program correctness.
  • Open/Closed PrinciplesDesign principle stating that software entities should be designed to allow extension of behavior without requiring modification of existing code.
Single Responsibility PrinciplesDesign principle asserting that a class should have only one specific reason to change, promoting focused and maintainable code.