docs: 🤝 add contributing guidelines

Author: faresrafat3

CONTRIBUTING.md

@@ -1,11 +1,51 @@
-# Contributing
+# Contributing to Fares Rafat's AI Systems
 
-1. Fork and branch from `main`.
-2. `pip install -e ".[dev]"`
-3. Add tests for new experts or pipeline layers.
-4. `pytest -q`
-5. Open a PR with a clear ARSENAL-layer note (L0–L6) if you change routing or memory.
+First off, thank you for considering contributing! We are building advanced, cost-aware LLM agent systems and intelligence aggregators. Contributions from the community ensure these architectures remain robust, open, and at the bleeding edge.
 
-## Design rule
+## 🧠 What we are looking for:
+- **Bug Fixes:** Fixing broken flows, outdated API calls, or dependency issues.
+- **New LEGO Pieces (AI Earth):** Adding new logical flows from recent SOTA AI papers.
+- **Pipeline Optimizations (ARSENAL):** Enhancing prompt performance, reducing token cost, or refining the multi-agent orchestration.
+- **Documentation:** Translating concepts, fixing typos, or improving the Mermaid graphs.
 
-Prefer **explicit claims + limits** over flashy ungrounded generation. This project is an epistemic scaffold.
+## 🚀 How to Contribute
+
+### 1. Fork and Clone
+Fork the repository to your own GitHub account and then clone it locally.
+```bash
+git clone https://github.com/YOUR-USERNAME/REPOSITORY-NAME.git
+cd REPOSITORY-NAME
+```
+
+### 2. Branching Strategy
+Create a new branch for your feature or bugfix. Please use descriptive names:
+- `feature/new-agent-logic`
+- `fix/router-latency`
+- `docs/arabic-translation`
+
+```bash
+git checkout -b feature/your-feature-name
+```
+
+### 3. Making Changes
+- Write clear, concise, and documented code.
+- If you are adding a new AI logic extraction, ensure you cite the original paper.
+- Follow the existing coding style (Python PEP-8, TypeScript standard).
+
+### 4. Testing
+If the repository contains tests (e.g., `pytest`), make sure to run them locally before pushing.
+```bash
+pytest tests/
+```
+
+### 5. Push and Pull Request
+Push your branch to your fork and submit a Pull Request against the `main` branch of this repository.
+```bash
+git push origin feature/your-feature-name
+```
+In your PR description, explain **what** you changed and **why**. If it fixes an open issue, link to it (e.g., "Fixes #12").
+
+## ⚖️ Code of Conduct
+By participating, you are expected to uphold our [Code of Conduct](CODE_OF_CONDUCT.md). We are committed to a harassment-free experience for everyone.
+
+*Built with care — from Cairo to the open web.*