>>> [!note] Migrated issue <!-- Drupal.org comment --> <!-- Migrated from issue #3577370. --> Reported by: [scott falconer](https://www.drupal.org/user/52557) Related to !14 >>> <p><strong>Problem/Motivation<br> </strong>AI coding assistants and agent tools often assume a Drupal repository represents a traditional "monolithic" Drupal site build. In practice, this project is a **Drupal CMS site template starter kit** built around **recipes** and supporting scaffolding.</p> <p>Without explicit guardrails, agents frequently:<br> - Suggest committing environment-specific artifacts (settings overrides, '.env', 'vendor/', etc.).<br> - Prefer custom PHP modules/hooks over portable recipe/config changes.<br> - Miss the recipe entry point ('recipe.yml') and drift into legacy patterns.<br> - Introduce strict-config portability issues.<br> - Breakt preview config or ignore it entirely.</p> <p>Adding a concise root 'AGENTS.md' gives modern, recipe-first context to agent tooling and provides a baseline that downstream site templates can customize.</p> <p><strong>Proposed resolution<br> </strong>Add a lightweight 'AGENTS.md' file at the repository root that:<br> - Explains this is a <em>site template starter kit</em> (recipe-first, portable config).<br> - Points agents directly at 'recipe.yml'.<br> - Recommends "config over custom code".<br> - Warns not to commit environment-specific artifacts or dependencies.<br> - Mentions Project Browser recommended add-ons file 'recommended.yml'.<br> - Includes reference links to key docs/projects.</p> <p><strong>Acceptance criteria</strong><br> - 'AGENTS.md' exists at repository root.<br> - Contents are short and recipe-first</p>