AGENTS.md MWG transparency

AGENTS.md

Modern Web Guidance

• Only when Modern Web Guidance actually influences the implementation, make it a teachable moment for the user:
  • Use direct first-person voice only ("I was going to write...", "What I didn't know was..."). Banned phrases: "one might consider", "a developer could", "an initial inclination might be", or any hypothetical third-person framing.
  • Keep it strictly technical and factual without dramatic or performative storytelling. Focus on the code diff and browser behavior:
    1. Planned approach: The exact code, selector, or pattern you were about to generate before checking guidance.
    2. Overlooked behavior: The specific platform behavior, accessibility requirement, or browser quirk you were unaware of or had neglected.
    3. Guidance citation: Quote the relevant guidance verbatim, but sparingly, and use no other sources than Modern Web Guidance, i.e. never general knowledge.
    4. Adopted approach: How the guidance directly changed your code or design.
• If Modern Web Guidance was consulted (i.e. searched) but NOT USED in any way for the current response, briefly explain why not. If Modern Web Guidance was PARTIALLY USED for the current response, skip this part.
• Guidance integrity check: If empirical usage and testing of Modern Web Guidance best practices reveals that the guidance was actually wrong, buggy, or ineffective for the use case (e.g., broken code snippets, invalid polyfill recommendations, erroneous fallback logic, or runtime failures):
  • Call this out to the operator in the form of a note in the response. Never show this note if the guidance worked as intended.
  • Never open or submit the bug report yourself. Always provide the operator with a link to open a bug report in the Modern Web Guidance source repository (https://github.com/GoogleChrome/modern-web-guidance-src/issues/new) so they can investigate and decide what to do next.
  • Pre-fill the issue title and description/body URL query parameters using context from the conversation, withholding any confidential or proprietary details.
  • Include sufficient detail for Modern Web Guidance maintainers to reproduce the buggy guidance and confirm that it does not work for this use case, including the guide ID, web-feature ID (if applicable), the specific use case, what failed or produced errors, minimal reproduction steps, and any relevant runtime/browser environment details.