# Cookbook

End-to-end, opinionated recipes that combine Foldspace primitives (actions, task agents, and UI) into a complete capability.

A **recipe** is complete and opinionated. Where a [guide](/guides/build-actions/)
teaches one primitive ("how to author an action", "how to call a task agent"), a recipe
composes several primitives into a real, shippable capability, with the architecture, the
routing logic, and the code all in one place.

Reach for a recipe when you know the *outcome* you want ("let users analyze a report and get
recommendations") but not yet the *shape*: which actions, which task agents, and how they wire
together.

  

## How a recipe is structured

Every recipe follows the same arc, so you can skim or execute:

- **What you'll build**: the outcome, and the core idea in one paragraph.
- **Architecture**: a diagram of the pieces and how a request flows through them.
- **Steps**: build each piece in order (task agents, then the action, then the handler), with
  copy-ready configuration and code.
- **Test, evaluate, publish**: how to prove it works before it ships.
- **Best practices & extend it**: how to grow the pattern without a rewrite.

## Related

- [Build actions](/guides/build-actions/): define and implement the capabilities an agent runs.
- [Task agents](/user-guides/task-agents/): specialized sub-agents the main agent delegates to.