Bundled prompt templates (documentation) | Rasa Documentation

Build your first agent in just a few minutes with Rasa Copilot.

This directory holds copies of default Jinja2 prompts that ship with Rasa, so MDX pages can import them as raw strings (see plugins/jinja2-raw-loader and src/components/PromptTemplateBlock).

Workflow: When product defaults change, copy the updated .jinja2 files from the Rasa repository into the appropriate subfolder here. Only keep files that are imported by documentation (see llm-command-generators.mdx, generative-search.mdx, react-sub-agents.mdx, coexistence-routers.mdx, configuration-and-results.mdx).

Layout

Subfolder	Rasa path	Purpose
`command-generator/`	`rasa/dialogue_understanding/generator/prompt_templates/`	Defaults for `CompactLLMCommandGenerator` and `SearchReadyLLMCommandGenerator` (model-specific templates). Same filenames as upstream.
`coexistence/`	`rasa/dialogue_understanding/coexistence/`	Coexistence router prompt (`router_template.jinja2`).
`sub-agents/`	`rasa/agents/templates/`	MCP agent prompt templates.
`policies/`	`rasa/core/policies/`	Enterprise Search Policy prompts used in the Generative Search reference (`enterprise_search_prompt_with_citation_template.jinja2`, `enterprise_search_prompt_with_relevancy_check_and_citation_template.jinja2`).
`evals/`	`rasa/builder/copilot/prompts/`	Default prompts for simulation and evaluation (`simulated_user_system_prompt.jinja2`, `evaluation_criteria_judge_prompt.jinja2`, `evaluation_metrics_judge_prompt.jinja2`).

Using a template on a documentation page

Webpack loads each .jinja2 file as a string (see plugins/jinja2-raw-loader). Pass that string to PromptTemplateBlock so it renders like a titled code block.

Example: show the default compact command-generator prompt for GPT‑5.1 (command_prompt_v3_gpt_5_1_2025_11_13_template.jinja2).

At the top of your MDX file (with your other imports):

import PromptTemplateBlock from "@site/src/components/PromptTemplateBlock";
import commandPromptV3Gpt51 from "@site/docs/snippets/prompt-templates/command-generator/command_prompt_v3_gpt_5_1_2025_11_13_template.jinja2";

In the body of the page, where you want the template to appear:

<PromptTemplateBlock
  title="command_prompt_v3_gpt_5_1_2025_11_13_template.jinja2"
  source={commandPromptV3Gpt51}
/>

For any other bundled file, change the import path to @site/docs/snippets/prompt-templates/<category>/<filename>.jinja2 and pick a matching title (usually the filename). Keep import names descriptive to avoid clashes when you import several templates on one page.