docs: update .github/CONTRIBUTING.md via Apex Optimizer

Author: chirag127

.github/CONTRIBUTING.md

@@ -0,0 +1,100 @@
+# Contributing to Python-Foundation-Libraries-And-Scripts-Python-Lib
+
+Thank you for considering contributing to the `Python-Foundation-Libraries-And-Scripts-Python-Lib` repository! We aim to maintain a high standard of quality, efficiency, and professionalism.
+
+## 1. Code of Conduct
+
+This project adheres to the Contributor Covenant Code of Conduct. By participating, you are expected to uphold this code. Please report any violations to [[email protected]](mailto:[email protected]) or via a direct GitHub issue.
+
+## 2. How to Contribute
+
+We welcome contributions in the form of bug reports, feature requests, and code contributions.
+
+### 2.1. Reporting Bugs
+
+Before reporting a bug, please check the [Issues](https://github.com/chirag127/Python-Foundation-Libraries-And-Scripts-Python-Lib/issues) page to see if it has already been reported.
+
+If it's a new bug, please:
+
+1.  **Create a New Issue:** Use the `Bug Report` template.
+2.  **Provide Details:** Include a clear and concise description of the bug, steps to reproduce it, your operating system, Python version, and any relevant error messages or logs.
+3.  **Use the Template:** Ensure you fill out all sections of the `Bug Report` issue template.
+
+### 2.2. Suggesting Features & Enhancements
+
+For new ideas or feature requests:
+
+1.  **Create a New Issue:** Use the `Feature Request` template (if available, otherwise a general issue).
+2.  **Describe Your Idea:** Explain the proposed feature, its benefits, and how it might be implemented.
+3.  **Be Specific:** The more detailed your suggestion, the better we can understand and consider it.
+
+### 2.3. Submitting Code Changes (Pull Requests)
+
+We encourage you to submit your improvements via Pull Requests (PRs).
+
+**Workflow:**
+
+1.  **Fork the Repository:** Create your own fork of the repository: `https://github.com/chirag127/Python-Foundation-Libraries-And-Scripts-Python-Lib`.
+2.  **Clone Your Fork:** Clone your forked repository to your local machine:
+    bash
+    git clone https://github.com/chirag127/Python-Foundation-Libraries-And-Scripts-Python-Lib.git
+    cd Python-Foundation-Libraries-And-Scripts-Python-Lib
+    
+3.  **Set Up Development Environment:** Follow the setup instructions in the `README.md` to install dependencies (using `uv` as per the project's standard) and prepare your environment.
+4.  **Create a New Branch:** Create a feature branch for your changes:
+    bash
+    git checkout -b feature/your-feature-name
+    
+    (Replace `your-feature-name` with a descriptive name).
+5.  **Make Your Changes:** Implement your feature or bug fix. Adhere to the project's coding standards and architectural principles (Modular Monolith, DRY, SOLID).
+6.  **Test Your Changes:** Ensure all tests pass and consider adding new tests for your changes. Run tests using `pytest`.
+7.  **Lint and Format:** Use `ruff` to ensure your code is clean and formatted correctly.
+    bash
+    ruff check .
+    ruff format .
+    
+8.  **Commit Your Changes:** Commit your work with clear, descriptive commit messages.
+    bash
+    git add .
+    git commit -m "feat: Add awesome new feature for X"
+    # or
+    git commit -m "fix: Resolve critical bug in Y"
+    
+9.  **Push to Your Fork:** Push your branch to your fork on GitHub:
+    bash
+    git push origin feature/your-feature-name
+    
+10. **Open a Pull Request:** Go to the original repository (`https://github.com/chirag127/Python-Foundation-Libraries-And-Scripts-Python-Lib`) and open a new Pull Request from your feature branch.
+    *   **Title:** Use a concise and descriptive title (e.g., "Feat: Add X functionality").
+    *   **Description:** Clearly explain the changes, the problem they solve, and reference any related issues.
+    *   **Use the PR Template:** Ensure the Pull Request template is filled out.
+
+## 3. Development Standards & Environment
+
+*   **Language:** Python 3.10+
+*   **Package Management:** `uv` is the standard for dependency management.
+*   **Linting & Formatting:** `ruff` is used for code quality and style enforcement.
+*   **Testing:** `pytest` is used for all unit and integration tests.
+*   **Architecture:** Adheres to Modular Monolith principles.
+*   **Principles:** We follow SOLID, DRY, and YAGNI principles.
+
+## 4. Code Review Process
+
+*   All PRs will be reviewed by at least one maintainer.
+*   Reviews will focus on correctness, adherence to standards, maintainability, and performance.
+*   Please be responsive to feedback and make necessary revisions.
+
+## 5. Project Structure
+
+Refer to the `README.md` for the detailed project structure. Key components include:
+
+*   `src/` or package directory: Core application logic.
+*   `tests/`: Unit and integration tests.
+*   `scripts/`: Utility scripts.
+*   `pyproject.toml`: Project configuration and dependencies.
+
+## 6. AI Agent Directives
+
+This project is designed to be compatible with Apex AI Agent Directives. For detailed information on the expected structure, tooling, and architectural patterns, please refer to the `AGENTS.md` file in the root of this repository.
+
+By contributing, you agree to help maintain these standards.