Objective: Add a custom AI agent that can create PPM images using natural language instructions.
This guide walks through adding a new Image Artist agent to the modular agent supervisor system. The agent will understand human-readable prompts like:
"Draw a PPM image of size 200 by 200, add a square at coordinate 10,10 with a size of 20 pixels in red color, then add 10 circles of varying sizes and colors randomly around the image, and write the file as image.ppm"
| #!/bin/bash | |
| if [ "$#" -ne 3 ]; then | |
| echo "Usage: $0 <ORG_NAME> <GITHUB_TOKEN> <MEMBERS_FILE>" | |
| exit 1 | |
| fi | |
| ORG_NAME="$1" | |
| GITHUB_TOKEN="$2" | |
| MEMBERS_FILE="$3" |
This primer serves as an absolute beginner's introduction to Neo4j, assuming no prior knowledge of databases, graphs, or programming beyond basic computer literacy. It breaks down the foundational concepts into digestible steps, explaining "why" before "how," and using simple analogies. The focus is on pure Neo4j groundwork, with practical, code-driven examples using Python and Cypher. No advanced topics like RAG (Retrieval-Augmented Generation) are covered here—this is just the essentials to get you started.
Structure: One sprint with 4 modules for quick pacing (1-2 hours total). Code uses Python (basic level) and Cypher. If you don't have Python installed, download it from https://www.python.org/downloads/ and follow the installation instructions for your operating system.
Estimated time: 30-45 minutes per module.
| <!DOCTYPE html> | |
| <html lang="en"> | |
| <head> | |
| <meta charset="UTF-8"> | |
| <meta name="viewport" content="width=device-width, initial-scale=1.0"> | |
| <title>Simple Calculator</title> | |
| <style> | |
| body { | |
| font-family: Arial, sans-serif; | |
| max-width: 400px; |
This task list breaks down Epic 4 for ReplyNow into sequential, actionable steps. Each task includes dependencies (if any), estimated effort (low/medium/high based on complexity in vanilla HTML/CSS/JS), and success criteria. Tasks are grouped by feature for clarity but can be tackled in order. Assume the project setup from Epics 1-3 (e.g., index.html, styles.css, separate JS files like input.js, replyGenerator.js, output.js, and a main.js) is in place. This epic focuses on enforcing modularity and SOLID principles without adding new features—refactor if needed. Use Git for version control—commit after each major task.
This task list breaks down Epic 3 for ReplyNow into sequential, actionable steps. Each task includes dependencies (if any), estimated effort (low/medium/high based on complexity in vanilla HTML/CSS/JS), and success criteria. Tasks are grouped by feature for clarity but can be tackled in order. Assume the project setup from Epics 1 and 2 (e.g., index.html with form and output, styles.css with basic styles, JS modules) is in place. Use Git for version control—commit after each major task.
This task list breaks down Epic 2 for ReplyNow into sequential, actionable steps. Each task includes dependencies (if any), estimated effort (low/medium/high based on complexity in vanilla HTML/CSS/JS), and success criteria. Tasks are grouped by feature for clarity but can be tackled in order. Assume the project setup from Epic 1 (e.g., index.html with form, styles.css, app.js with module files like output.js) is in place. Use Git for version control—commit after each major task.
<textarea> element to index.html for displaying the generated reply.
This task list breaks down Epic 1 for ReplyNow into sequential, actionable steps. Each task includes dependencies (if any), estimated effort (low/medium/high based on complexity in vanilla HTML/CSS/JS), and success criteria. Tasks are grouped by feature for clarity but can be tackled in order. Assume a basic project setup (e.g., index.html, styles.css, app.js with module files) is already in place. Use Git for version control—commit after each major task.
<textarea> to index.html for users to paste the incoming email.