agency-voice-interface — Cursor Rules

It's crucial to understand the distinction between standalone tools and Agency Swarm agencies within this project: • Standalone Tools (/tools directory): • Located in the /tools directory • Must be adapted from Agency-Swarm standards • Developed as individual, reusable components • Follow specific guidelines for standalone tool development • Agency Swarm Agencies (/agencies directory): • Located in the /agencies directory • Follow normal Agency Swarm development practices • Organized into agencies and agents with their respective tools Now, let's delve into the specific instructions for Agency Swarm development, which primarily applies to the /agencies directory. --- Start of Agency Swarm Framework Instructions ---

Agency Swarm started as a desire and effort of Arsenii Shatokhin (aka VRSEN) to fully automate his AI Agency with AI. By building this framework, we aim to simplify the agent creation process and enable anyone to create a collaborative swarm of agents (Agencies), each with distinct roles and capabilities.

• Customizable Agent Roles: Define roles like CEO, virtual assistant, developer, etc., and customize their functionalities with Assistants API. • Full Control Over Prompts: Avoid conflicts and restrictions of pre-defined prompts, allowing full customization. • Tool Creation: Tools within Agency Swarm are created using pydantic, which provides a convenient interface and automatic type validation. • Efficient Communication: Agents communicate through a specially designed "send message" tool based on their own descriptions. • State Management: Agency Swarm efficiently manages the state of your assistants on OpenAI, maintaining it in a special settings.json file. • Deployable in Production: Agency Swarm is designed to be reliable and easily deployable in production environments.

Tools are the specific actions that agents can perform. They are defined in the tools folder. When creating a tool, you are defining a new class that extends BaseTool from agency_swarm.tools. This process involves several key steps, outlined below. 1.1. Import Necessary Modules Start by importing BaseTool from agency_swarm.tools and Field from pydantic. These imports will serve as the foundation for your custom tool class. Import any additional packages necessary to implement the tool's logic based on the user's requirements. Import load_dotenv from dotenv to load the environment variables. 1.2. Define Your Tool Class Create a new class that inherits from BaseTool. This class will encapsulate the functionality of your tool. BaseTool class inherits from the Pydantic's BaseModel class. 1.3. Specify Tool Fields Define the fields your tool will use, utilizing Pydantic's Field for clear descriptions and validation. These fields represent the inputs your tool will work with, including only variables that vary with each use. Define any constant variables globally. 1.4. Implement the run Method The run method is where your tool's logic is executed. Use the fields defined earlier to perform the tool's intended task. It must contain the actual fully functional correct python code. It can utilize various python packages, previously imported in step 1.