Skip to content

Commit d4626e7

Browse files
authored
Update README.md
1 parent 51df236 commit d4626e7

File tree

1 file changed

+11
-0
lines changed

1 file changed

+11
-0
lines changed

building-effective-agents/README.md

+11
Original file line numberDiff line numberDiff line change
@@ -20,6 +20,8 @@ All of these examples focus on performing specific tasks, rather than do-it-all
2020

2121
### Prompt chaining
2222

23+
![prompt-chaining](https://github.com/user-attachments/assets/498e8482-5cbb-4f60-a03f-5728c38a9cc3)
24+
2325
Breaking down a task into a series of steps, guided through a pre-determined sequence.
2426

2527
#### Prompt chaining task
@@ -32,6 +34,9 @@ View the Trigger.dev prompt chaining task code: [src/trigger/trigger/translate-c
3234

3335
### Routing
3436

37+
![routing](https://github.com/user-attachments/assets/6d94c5b8-b9ae-4b56-ad64-007ff7ea30a0)
38+
39+
3540
You can think of routing as an AI traffic controller. Instead of forcing one LLM to handle everything, you first figure out what type of task you're dealing with, then send it to the right specialist.
3641

3742
#### Routing task
@@ -45,6 +50,8 @@ View the Trigger.dev routing task code: [src/trigger/trigger/routing-questions.t
4550

4651
### Parallelization
4752

53+
![parallelization](https://github.com/user-attachments/assets/d4c51caa-ebfe-4893-85b0-10825649681d)
54+
4855
Sometimes you need to do multiple things at once – that's where parallelization comes in. Rather than working through tasks one by one, you split them up and run them simultaneously. This is where batch.triggerByTaskAndWait shines, allowing you to execute multiple tasks in parallel and efficiently coordinate their responses.
4956

5057
#### Parallelization task
@@ -61,6 +68,8 @@ View the Trigger.dev parallelization task code: [src/trigger/trigger/parallel-ll
6168

6269
### Orchestrator-workers
6370

71+
![orchestrator-workers](https://github.com/user-attachments/assets/46ef2a06-fb8e-4843-a95a-7f251cc9fd20)
72+
6473
This pattern is like having a project manager (the orchestrator) who breaks down a big job into smaller tasks and assigns them to specialists (the workers). The orchestrator keeps track of everything and puts all the pieces back together at the end. Using batch.triggerByTaskAndWait, it efficiently coordinates multiple tasks while maintaining clear control over the entire workflow.
6574

6675
#### Orchestrator-workers task
@@ -74,6 +83,8 @@ View the Trigger.dev orchestrator-workers task code: [src/trigger/trigger/orches
7483

7584
### Evaluator-optimizer
7685

86+
![evaluator-optimizer](https://github.com/user-attachments/assets/ddddd1ff-1aef-4e4f-901b-47c69f992826)
87+
7788
Here's where you add quality control to your AI system. The evaluator checks the output, and if it's not quite right, the optimizer suggests improvements. Think of it as having a friendly editor who reviews your work and helps make it better.
7889

7990
#### Evaluator-optimizer task

0 commit comments

Comments
 (0)