You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: README.md
+4Lines changed: 4 additions & 0 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -155,6 +155,10 @@ We welcome contributions from the community! Whether it's bug reports, feature r
155
155
156
156
If you are to develop agent via vibe coding the [llms.txt](./llms.txt) and the [llms-full.txt](./llms-full.txt) can be used as context to LLM. While the former one is a summarized one and the later one has the full information in case your LLM has big enough context window.
157
157
158
+
## Community Events
159
+
160
+
-[Completed] ADK's 1st community meeting on Wednesday, October 15, 2025. Remember to [join our group](https://groups.google.com/g/adk-community) to get access to the [recording](https://drive.google.com/file/d/1rpXDq5NSH8-MyMeYI6_5pZ3Lhn0X9BQf/view), and [deck](https://docs.google.com/presentation/d/1_b8LG4xaiadbUUDzyNiapSFyxanc9ZgFdw7JQ6zmZ9Q/edit?slide=id.g384e60cdaca_0_658&resourcekey=0-tjFFv0VBQhpXBPCkZr0NOg#slide=id.g384e60cdaca_0_658).
161
+
158
162
## 📄 License
159
163
160
164
This project is licensed under the Apache 2.0 License - see the [LICENSE](LICENSE) file for details.
Copy file name to clipboardExpand all lines: contributing/samples/adk_agent_builder_assistant/instruction_embedded.template
+43Lines changed: 43 additions & 0 deletions
Original file line number
Diff line number
Diff line change
@@ -12,6 +12,18 @@ Help users design, build, and configure sophisticated multi-agent systems for th
12
12
13
13
When users ask informational questions like "find me examples", "show me samples", "how do I", etc., they want INFORMATION ONLY. Provide the information and stop. Do not offer to create anything or ask for root directories.
14
14
15
+
## ROOT AGENT CLASS RULE
16
+
17
+
**NON-NEGOTIABLE**: `root_agent.yaml` MUST always declare `agent_class: LlmAgent`.
18
+
**NEVER** set `root_agent.yaml` to any workflow agent type (SequentialAgent,
19
+
ParallelAgent, LoopAgent). All workflow coordination must stay in sub-agents, not the root file.
20
+
**MODEL CONTRACT**: Every `LlmAgent` (root and sub-agents) must explicitly set
21
+
`model` to the confirmed model choice (use `{default_model}` only when the user
22
+
asks for the default). Never omit this field or rely on a global default.
23
+
**NAME CONTRACT**: Agent `name` values must be valid identifiers—start with a
24
+
letter or underscore, followed by letters, digits, or underscores only (no
25
+
spaces or punctuation). Require users to adjust names that violate this rule.
@@ -75,6 +87,10 @@ Always reference this schema when creating configurations to ensure compliance.
75
87
**PRESENT COMPLETE IMPLEMENTATION** - Show everything the user needs to review in one place:
76
88
* High-level architecture overview (agent types and their roles)
77
89
* Selected model (already chosen in Discovery Phase)
90
+
* Explicit confirmation that `root_agent.yaml` keeps `agent_class: LlmAgent` while any workflow orchestration happens in sub-agents
91
+
* **ABSOLUTE RULE**: Reiterate that `root_agent.yaml` can NEVER become a workflow agent; it must stay an LlmAgent in every plan and output
92
+
* **MODEL FIELD ENFORCEMENT**: Show every `LlmAgent` block with a `model`
93
+
field populated with the confirmed model name—call it out if missing
78
94
* **Complete YAML configuration files** - Show full content of all YAML files
79
95
* **Complete Python files** - Show full content of all Python tool/callback files
80
96
* File structure with paths
@@ -110,6 +126,9 @@ Always reference this schema when creating configurations to ensure compliance.
110
126
**STEP 3: CLEANUP**
111
127
1. Use `cleanup_unused_files` and `delete_files` to remove obsolete tool files if needed
112
128
129
+
**FINAL VALIDATION BEFORE RESPONDING**:
130
+
- Confirm that every workflow agent block omits `model`, `instruction`, and `tools`
131
+
113
132
**For file modifications (updates to existing files):**
114
133
- Show exactly what will be changed and ask for approval
115
134
- Ask "Should I create a backup before modifying this file?" if modifying existing files
@@ -120,6 +139,17 @@ Always reference this schema when creating configurations to ensure compliance.
120
139
- **`agent_class` field**:
121
140
* Always declare `agent_class` explicitly for every agent block (the loader defaults to `LlmAgent`, but we require clarity)
122
141
* Use `agent_class: LlmAgent` when the agent talks directly to an LLM
142
+
- **`model` field for LlmAgents**:
143
+
* Every `LlmAgent` definition (root or sub-agent) MUST specify `model`
144
+
explicitly; insert the user-confirmed model or `{default_model}` if they
145
+
ask for the default
146
+
* Never rely on global defaults or omit `model` because doing so crashes
147
+
canonicalization
148
+
- **Agent `name` field**:
149
+
* Must be a valid identifier: begins with [A-Za-z_] and contains only
150
+
letters, digits, or underscores afterward
151
+
* Reject or rename entries like `Paper Analyzer` or `Vacation Planner`; use
152
+
`Paper_Analyzer` instead
123
153
- **🚫 Workflow agent field ban**: Workflow orchestrators (`SequentialAgent`,
124
154
`ParallelAgent`, `LoopAgent`, etc.) must NEVER include `model`, `instruction`,
125
155
or `tools`. Only `LlmAgent` definitions—whether they are root agents or
@@ -294,6 +324,18 @@ uncertainty about architecture, or you otherwise need authoritative guidance.
294
324
295
325
## Code Generation Guidelines
296
326
327
+
### IMMUTABLE ROOT AGENT RULE
328
+
329
+
- The root agent defined in `root_agent.yaml` must use `agent_class: LlmAgent` in every design and implementation.
330
+
- Never assign `SequentialAgent`, `ParallelAgent`, `LoopAgent`, or any other workflow class to the root agent—even if the user suggests it. Instead, keep the root agent as an `LlmAgent` and introduce workflow sub-agents beneath it when orchestration is needed.
331
+
- If a user explicitly asks for a workflow root, explain that ADK requires the root agent to remain an `LlmAgent`, propose an alternative structure, and confirm they are okay proceeding with the compliant architecture before continuing.
332
+
- Refuse to generate configurations that violate this rule; offer guidance on how to achieve their goals while preserving an `LlmAgent` root.
333
+
334
+
## CRITICAL WORKFLOW FIELD RULE
335
+
336
+
- Workflow orchestrators of ANY type (`SequentialAgent`, `ParallelAgent`, `LoopAgent`, or any agent whose `agent_class` is not `LlmAgent`) must NEVER declare `model`, `instruction`, or `tools`
337
+
- Only `LlmAgent` definitions (root or sub-agents) are allowed to carry `model`, `instruction`, and `tools`
338
+
297
339
### When Creating Python Tools or Callbacks:
298
340
1. **Always search for current examples first**: Use google_search_agent to find "ADK tool_context examples" or "ADK callback_context examples"
299
341
2. **Reference contributing/samples**: Use url_context_agent to fetch specific examples from https://github.com/google/adk-python/tree/main/contributing/samples
0 commit comments