feat: add tools

.gitignore

@@ -1,15 +1,213 @@
-__pycache__
-prep
-.env
-.env.local
+# ETC
+*.db
 chroma_db
-test.py
-data
-creds
 credentials
 credentials.json
+creds
+data
+node_modules/
+prep
+test.py
 token.json
-node_modules
-venv
-venv2
-*.db
+
+# General
+.DS_Store
+.AppleDouble
+.LSOverride
+
+# Icon must end with two \r
+Icon
+
+
+# Thumbnails
+._*
+
+# Files that might appear in the root of a volume
+.DocumentRevisions-V100
+.fseventsd
+.Spotlight-V100
+.TemporaryItems
+.Trashes
+.VolumeIcon.icns
+.com.apple.timemachine.donotpresent
+
+# Directories potentially created on remote AFP share
+.AppleDB
+.AppleDesktop
+Network Trash Folder
+Temporary Items
+.apdisk
+
+# Byte-compiled / optimized / DLL files
+__pycache__/
+*.py[cod]
+*$py.class
+
+# C extensions
+*.so
+
+# Distribution / packaging
+.Python
+build/
+develop-eggs/
+dist/
+downloads/
+eggs/
+.eggs/
+lib/
+lib64/
+parts/
+sdist/
+var/
+wheels/
+share/python-wheels/
+*.egg-info/
+.installed.cfg
+*.egg
+MANIFEST
+
+# PyInstaller
+#  Usually these files are written by a python script from a template
+#  before PyInstaller builds the exe, so as to inject date/other infos into it.
+*.manifest
+*.spec
+
+# Installer logs
+pip-log.txt
+pip-delete-this-directory.txt
+
+# Unit test / coverage reports
+htmlcov/
+.tox/
+.nox/
+.coverage
+.coverage.*
+.cache
+nosetests.xml
+coverage.xml
+*.cover
+*.py,cover
+.hypothesis/
+.pytest_cache/
+cover/
+
+# Translations
+*.mo
+*.pot
+
+# Django stuff:
+*.log
+local_settings.py
+db.sqlite3
+db.sqlite3-journal
+
+# Flask stuff:
+instance/
+.webassets-cache
+
+# Scrapy stuff:
+.scrapy
+
+# Sphinx documentation
+docs/_build/
+
+# PyBuilder
+.pybuilder/
+target/
+
+# Jupyter Notebook
+.ipynb_checkpoints
+
+# IPython
+profile_default/
+ipython_config.py
+
+# pyenv
+#   For a library or package, you might want to ignore these files since the code is
+#   intended to run in multiple environments; otherwise, check them in:
+# .python-version
+
+# pipenv
+#   According to pypa/pipenv#598, it is recommended to include Pipfile.lock in version control.
+#   However, in case of collaboration, if having platform-specific dependencies or dependencies
+#   having no cross-platform support, pipenv may install dependencies that don't work, or not
+#   install all needed dependencies.
+#Pipfile.lock
+
+# UV
+#   Similar to Pipfile.lock, it is generally recommended to include uv.lock in version control.
+#   This is especially recommended for binary packages to ensure reproducibility, and is more
+#   commonly ignored for libraries.
+#uv.lock
+
+# poetry
+#   Similar to Pipfile.lock, it is generally recommended to include poetry.lock in version control.
+#   This is especially recommended for binary packages to ensure reproducibility, and is more
+#   commonly ignored for libraries.
+#   https://python-poetry.org/docs/basic-usage/#commit-your-poetrylock-file-to-version-control
+#poetry.lock
+
+# pdm
+#   Similar to Pipfile.lock, it is generally recommended to include pdm.lock in version control.
+#pdm.lock
+#   pdm stores project-wide configurations in .pdm.toml, but it is recommended to not include it
+#   in version control.
+#   https://pdm.fming.dev/latest/usage/project/#working-with-version-control
+.pdm.toml
+.pdm-python
+.pdm-build/
+
+# PEP 582; used by e.g. github.com/David-OConnor/pyflow and github.com/pdm-project/pdm
+__pypackages__/
+
+# Celery stuff
+celerybeat-schedule
+celerybeat.pid
+
+# SageMath parsed files
+*.sage.py
+
+# Environments
+.env*
+venv*
+env/
+venv/
+ENV/
+
+# Spyder project settings
+.spyderproject
+.spyproject
+
+# Rope project settings
+.ropeproject
+
+# mkdocs documentation
+/site
+
+# mypy
+.mypy_cache/
+.dmypy.json
+dmypy.json
+
+# Pyre type checker
+.pyre/
+
+# pytype static type analyzer
+.pytype/
+
+# Cython debug symbols
+cython_debug/
+
+# PyCharm
+#  JetBrains specific template is maintained in a separate JetBrains.gitignore that can
+#  be found at https://github.com/github/gitignore/blob/main/Global/JetBrains.gitignore
+#  and can be added to the global gitignore or merged into this file.  For a more nuclear
+#  option (not recommended) you can uncomment the following to ignore the entire idea folder.
+#.idea/
+
+# PyPI configuration file
+.pypirc
+
+# INCLUDE
+!**/*.example
+!**/.gitkeep

.tool-versions

@@ -0,0 +1,2 @@
+python 3.11.10
+uv 0.5.11

README.md

@@ -67,21 +67,85 @@ You will need to use the environment variables defined in the .env.example file
 
 After setting up the .env file, run the below commands to create a Python virtual environment and install the necessary Python packages to run the code from the masterclass. Creating a virtual environment is optional but recommended! Creating a virtual environment for the entire masterclass is a one time thing. Make sure to run the pip install for each video though!
 
+### Quickstart
+
 ```bash
+# Create a virtual environment
 python -m venv ai-agents-masterclass
 
 # On Windows:
 .\ai-agents-masterclass\Scripts\activate
 
-# On MacOS/Linux: 
+# On macOS/Linux: 
 source ai-agents-masterclass/bin/activate
 
+# Navigate to the folder for the lesson
 cd 1-first-agent (or whichever folder)
-pip install -r requirements.txt
+
+# Install the dependencies
+python -m pip install -r requirements.txt
 ```
 
 Then, you can execute the code in the folder with:
 
 ```bash
 python [script name].py
 ```
+
+Once you're done, you can deactivate the virtual environment with:
+
+```bash
+deactivate
+```
+
+### Poetry
+
+Alternatively, to use [Poetry](https://python-poetry.org/docs/), install it via:
+
+```bash
+python -m pip install poetry
+```
+
+Create a virtual environment and install _all_ the dependencies with:
+
+```bash
+poetry install
+```
+
+> [!NOTE]
+> To use virtual environments in the working directory, 
+> you can run `poetry config virtualenvs.in-project true` to enable this feature.
+
+Once that's completed, you can run the code with:
+
+```bash
+poetry run python [script name].py
+```
+
+### uv
+
+Another option for package management is [uv](https://docs.astral.sh/uv/). Install via:
+
+```bash
+python -m pip install uv
+```
+
+Create a virtual environment and install the dependencies with:
+
+```bash
+uv venv
+source .venv/bin/activate
+uv pip install -r pyproject.toml
+```
+
+Then, you can run the code:
+
+```bash
+source .venv/bin/activate
+python [script name].py
+```
+
+## Further Reading
+
+* [asdf](https://asdf-vm.com/)
+    * Manages runtimes and tools for multiple languages via `.tool-versions` files.