docs: add repository standards

Author: ReenigneArcher

.gitmodules

@@ -0,0 +1,70 @@
+Repository Standards
+====================
+
+This document outlines the standards and best practices for LizardByte repositories to ensure consistency,
+maintainability, and quality across all projects.
+
+Repository Structure
+--------------------
+
+File Organization
+~~~~~~~~~~~~~~~~~
+
+All repositories should follow a consistent structure:
+
+.. code-block:: text
+
+   repository-name/
+   ├── .github/
+   │   ├── matchers/  # custom problem matchers
+   │   ├── workflows/
+   │   │   ├── _codeql.yml
+   │   │   └── _common-lint.yml
+   │   ├── dependabot.yml
+   │   └── semantic.yml
+   ├── branding/  # project specific branding assets
+   ├── docs/  # structure varies depending on the doc system used
+   ├── src/  # main source code
+   ├── tests/  # if there are tests
+   ├── third-party/  # location of submodules if any
+   ├── .gitignore
+   ├── LICENSE
+   └── README.md or README.rst
+
+Required Files
+~~~~~~~~~~~~~~
+
+Every repository must include:
+
+- **LICENSE**: All projects must use an appropriate license
+- **README**: Primary documentation in reStructuredText (.rst) or Markdown (.md) format
+- **.gitignore**: Appropriate for the project's language and framework.
+  See `GitHub's collection <https://github.com/github/gitignore>`_ for starter templates.
+- **.github/**: Contains GitHub-specific configurations (workflows, issue templates, etc.)
+
+Naming Conventions
+------------------
+
+Repository Names
+~~~~~~~~~~~~~~~~
+
+- Be descriptive and concise
+- Avoid abbreviations unless widely understood
+
+Branch Names
+~~~~~~~~~~~~
+
+- Use descriptive names with forward slashes for organization
+- Format: ``type/short-description``
+- Types: ``feat/``, ``fix/``, ``docs/``, ``refactor/``:
+  see `Convential Commits <https://www.conventionalcommits.org/en/v1.0.0/>`_
+- Examples: ``feat/user-authentication``, ``fix/memory-leak``, ``docs/api-reference``
+
+File and Directory Names
+~~~~~~~~~~~~~~~~~~~~~~~~~
+
+- Be consistent within each project
+- Avoid spaces and special characters
+
+For questions about these standards or exceptions, please open an issue in the ``.github`` repository
+or contact the maintainers.

docs/source/developers/repository_standards.rst

@@ -18,3 +18,4 @@
 
    developers/code_of_conduct
    developers/contributing
+   developers/repository_standards