| 1 | # Example Agent Profile DOX |
| 2 | |
| 3 | ## Purpose |
| 4 | |
| 5 | - Own the reference profile used to demonstrate bundled profile layout. |
| 6 | - Show how profile-local prompts, tools, and extensions fit beside `agent.yaml`. |
| 7 | |
| 8 | ## Ownership |
| 9 | |
| 10 | - This reference intentionally has no `agent.yaml`, so it is not discovered as |
| 11 | a selectable profile. |
| 12 | - `prompts/` owns prompt override examples. |
| 13 | - `tools/` owns profile-local tool examples. |
| 14 | - `extensions/` owns profile-local lifecycle extension examples. |
| 15 | |
| 16 | ## Local Contracts |
| 17 | |
| 18 | - Keep this profile generic, minimal, and safe to copy into user or plugin profile work. |
| 19 | - Do not add product behavior here that should live in a real bundled profile. |
| 20 | - Profile-local tools and extensions must follow the same contracts as root tools and extensions. |
| 21 | |
| 22 | ## Work Guidance |
| 23 | |
| 24 | - Prefer simple examples that illustrate structure over complex behavior. |
| 25 | - Update related skill guidance when the example profile layout changes. |
| 26 | |
| 27 | ## Verification |
| 28 | |
| 29 | - Manually inspect YAML and prompt filenames after edits. |
| 30 | - Run profile-loading tests when changing discovery or profile schema assumptions. |
| 31 | |
| 32 | ## Child DOX Index |
| 33 | |
| 34 | No child DOX files. |