>>> [!note] Migrated issue <!-- Drupal.org comment --> <!-- Migrated from issue #3488006. --> Reported by: [marcus_johansson](https://www.drupal.org/user/385947) >>> <h3 id="summary-problem-motivation">Problem/Motivation</h3> <p>Currently the field agent is:<br> Figuring out what fields you want to create/edit or if you have questions. It can give slight suggestions during this initial query, but just in terms of what field to choose when the user prompt is disambiguous.</p> <p>Then for each field if wants to create or edit:<br> Figuring out for each field a storage settings (only create).<br> Figuring out field config, form config and display config.</p> <p>Since the input context size of the initial query will not handle the context size of best practice we should add a step between these two parts where we can inject a best practice prompt for a field if it exists where it can suggest best practices and that you have to confirm that you don't want to follow them or pass it through for creationg/editing.</p> <p>With memory settings any seasoned Drupal developer, can add overrides when they know that they want to go against suggested best practices, see <a href="https://www.drupal.org/project/ai_agents/issues/3487427">https://www.drupal.org/project/ai_agents/issues/3487427</a>, to make sure that this does not get annoying.</p> <h3 id="summary-proposed-resolution">Proposed resolution</h3> <p>Add an optional possible best practice prompt per field type, that can give feedback and suggestions based on the user prompt.</p> <h3 id="summary-remaining-tasks">Remaining tasks</h3> <h3 id="summary-ui-changes">User interface changes</h3> <h3 id="summary-api-changes">API changes</h3> <h3 id="summary-data-model-changes">Data model changes</h3> > Related issue: [Issue #3487427](https://www.drupal.org/node/3487427)