Imported from davisuga/wonderpharma (
AGENTS.md). Install upstream withnpx skills add davisuga/wonderpharma. Copyright stays with the author.
Home Assignment - Agent Engineer stack: Bun, sqlite, typescript, next, prisma, mastra.ai The CoreRequirements is the MOST IMPORTANT THING. EVERYTHING you do is 1000% aligned with CoreRequirements
- Assignment Objectives - Build real-time conversational AI pharmacy agent, on OpenAI API. The agent expected to handle workflows through tools: prescription management, inventory control, and customer service. Requirements
- AI Agent - Implement real-time text streaming AI agent based on GPT-5 (key provided separately). The agent is state-less, and can talk both in Hebrew and English.
- Tool - Design and implement agent’s tools
- Database - Create a synthetic database of 10 users and 5 medicals.
- UI - Interact with the agent.
- Multi-Step Flow - Design and implement at least three distinct multi-step flows the agent can execute
- Evaluation Plan - Provide an evaluation plan for your agent.
- Docker - Wrap your project in a Docker file. Guidelines
- Backend Language - Python, JavaScript, TypeScript or Go (no limitation for the frontend).
- AI assistant - You may collaborate with any AI assistant (Claude Code, Codex, etc.) during development. However, you are expected to be prepared to explain the code and answer questions about implementation decisions. Agent Requirements These are the minimum requirements the agent must meet. You may propose and include additional requirements if you believe they are important for production readiness.
- Provide factual information about medications.
- Explain dosage and usage instructions.
- Confirm prescription requirements.
- Check availability in stock.
- Identify active ingredients.
- No medical advice, no encouragement to purchase, no diagnosis.
- Redirect to a healthcare professional or general resources for advice requests.
- Streaming Flows to Design The agent should be able to execute at least three distinct multi-step flows. A multi-step flow is the expected sequence of actions an agent follows in a real use case, covering all the steps a professional would take when assisting a customer from the start of their request to its resolution. Define each flow, describe the expected sequence, and outline how the agent will use the functions and respond. Function (Tool) Design Requirements At minimum, design 3 different tools, for example:
- get_medication_by_name: Inputs, outputs, example responses, error handling, fallback logic.
- Additional tools may be added if justified. For each function, document:
- Name and purpose
- Inputs (parameters, types)
- Output schema (fields, types)
- Error handling
- Fallback behavior Deliverables
- README.md - Explanation of the project and its architecture, explanation of how to run the Docker.
- Multi-Step Flow - Three multi-step workflow demonstrations.
- Evidence - 2-3 screenshots of conversations.
- Evaluation Plan - Evaluate the Agent flows. Evaluation Criteria
- Tool/API design clarity.
- Prompt quality and integration of API usage.
- Multi-step interaction handling.
- Policy adherence.
- Testing rigor (coverage in Hebrew, multiple variations per flow).
- Quality and completeness of flow designs.