Building effective agents
Workflow vocabulary and the distinction between predefined workflows and agent-controlled execution.
Read the primary referenceFive source collections. Thirty-six approaches and building blocks. One consistent way to understand and use them.
A workflow controls execution. A planning pattern shapes a plan. A skill supplies context. An adapter is infrastructure. These are not all competing system architectures.
The conversation template adapts behavior to one assistant. The runtime template assumes real tools and execution support. Neither creates concurrency, permissions, or durable state by itself.
Prompts, example tasks, practical notes, and diagrams are original editorial material. They are not official vendor prompts or benchmarked guarantees. Test them on your own tasks.
The catalog normalizes common aliases while preserving important distinctions. The LangGraph page is a companion reference within the LangChain collection. This is not a claim to cover every agentic pattern ever proposed.
Workflow vocabulary and the distinction between predefined workflows and agent-controlled execution.
Read the primary referenceCoordination topologies, handoffs, group conversations, and adaptive task-ledger orchestration.
Read the primary referenceSingle-agent and multi-agent flows, loops, hierarchies, swarms, and human checkpoints.
Read the primary referenceThe 18-pattern research catalogue, including goal creation, planning, reflection, and supporting components.
Read the primary referenceSubagents, handoffs, skills, routing, and custom workflows.
Read the primary referenceA companion implementation reference for workflow and agent compositions.
Read the primary referenceDynamic decomposition creates work packages. A subagent is a call/return boundary. They often work together, but a specialist call does not require a full planning supervisor.
A second perspective in one chat can be useful, but it is not a separate agent execution. Cross-reflection separates the reviewer; evaluator–optimizer adds the feedback loop.
One-shot describes planning-call cadence. Single-path describes the number of candidate paths. A one-shot call can generate alternatives; one path can be developed incrementally.
Feedback improves a proposal. Explicit approval authorizes a specific action. A system must not substitute one for the other.
These distinctions are editorial synthesis. Follow the linked source definitions and your runtime's actual semantics.
Export all 72 original system prompts and their example tasks as one Markdown file, with source links.
Privacy: this site makes no AI calls. Theme, prompt mode, and saved patterns use local browser storage. When Cloudflare Zaraz is enabled, the site sends action names and limited details such as pattern IDs and category names to Cloudflare. Search text and copied content are never included in these events. External source links open only when you choose them.