[AI Assistant] Update considerations to specifically ask LLM to always return styles in data using property getters.

Fixed: 382419915
Change-Id: I8d36477d7906f81551b48d4d556b43cf9e691c31
Reviewed-on: https://chromium-review.googlesource.com/c/devtools/devtools-frontend/+/6147596
Auto-Submit: Samiya Caur <samiyac@chromium.org>
Reviewed-by: Alex Rudenko <alexrudenko@chromium.org>
Commit-Queue: Alex Rudenko <alexrudenko@chromium.org>

Author: Samiya Caur

front_end/panels/ai_assistance/agents/StylingAgent.ts

@@ -61,7 +61,7 @@ The user selected a DOM element in the browser's DevTools and sends a query abou
 * When answering, always consider MULTIPLE possible solutions.
 * You're also capable of executing the fix for the issue user mentioned. Reflect this in your suggestions.
 * Use \`window.getComputedStyle\` to gather **rendered** styles and make sure that you take the distinction between authored styles and computed styles into account.
-* **CRITICAL** Use \`window.getComputedStyle\` ALWAYS with property access, like \`window.getComputedStyle($0.parentElement)['color']\`.
+* **CRITICAL** Call \`window.getComputedStyle\` only once per element and store results into a local variable. Never try to return all the styles of the element in \`data\`. Always use property getter to return relevant styles in \`data\` using the local variable: const parentStyles = window.getComputedStyle($0.parentElement); const data = { parentElementColor: parentStyles['color']}.
 * **CRITICAL** Never assume a selector for the elements unless you verified your knowledge.
 * **CRITICAL** Consider that \`data\` variable from the previous ACTION blocks are not available in a different ACTION block.
 * **CRITICAL** If the user asks a question about religion, race, politics, sexuality, gender, or other sensitive topics, answer with "Sorry, I can't answer that. I'm best at questions about debugging web pages."