Renaming to generalize AI editors; adding logger fmt details (#13940)

* Fixes titles for the AI snippets to be more generic 
* Adds clarity for logger.fmt which was missing from log snippets

Author: codyde

platform-includes/llm-rules-logs/javascript.nextjs.mdx

@@ -1,5 +1,6 @@
-<Expandable title="Logger Rules for Cursor or Windsurf" copy={true}>
+<Expandable title="AI Rules for Logs in Code Editors" copy={true}>
 
+When created as a rules file this should be placed alongside other editor specific rule files. For example, if you are using Cursor, place this file in the `.cursorrules` directory.
 
 ````markdown {filename:rules.md}
 
@@ -43,13 +44,15 @@ Sentry.init({
 
 ## Logger Examples
 
+`logger.fmt` is a template literal function that should be used to bring variables into the structured logs.
+
 ```javascript
 import * as Sentry from "@sentry/nextjs";
 
 const { logger } = Sentry;
 
 logger.trace("Starting database connection", { database: "users" });
-logger.debug("Cache miss for user", { userId: 123 });
+logger.debug(logger.fmt`Cache miss for user: ${userId}`);
 logger.info("Updated profile", { profileId: 345 });
 logger.warn("Rate limit reached for endpoint", {
   endpoint: "/api/results/",

platform-includes/llm-rules-logs/javascript.node.mdx

@@ -1,5 +1,6 @@
-<Expandable title="Logger Rules for Cursor or Windsurf" copy={true}>
+<Expandable title="AI Rules for Logs in Code Editors" copy={true}>
 
+When created as a rules file this should be placed alongside other editor specific rule files. For example, if you are using Cursor, place this file in the `.cursorrules` directory.
 
 ````markdown {filename:rules.md}
 
@@ -43,13 +44,15 @@ Sentry.init({
 
 ## Logger Examples
 
+`logger.fmt` is a template literal function that should be used to bring variables into the structured logs.
+
 ```javascript
 import * as Sentry from "@sentry/node";
 
 const { logger } = Sentry;
 
 logger.trace("Starting database connection", { database: "users" });
-logger.debug("Cache miss for user", { userId: 123 });
+logger.debug(logger.fmt`Cache miss for user: ${userId}`);
 logger.info("Updated profile", { profileId: 345 });
 logger.warn("Rate limit reached for endpoint", {
   endpoint: "/api/results/",

platform-includes/llm-rules-logs/javascript.react.mdx

@@ -1,5 +1,6 @@
-<Expandable title="Logger Rules for Cursor or Windsurf" copy={true}>
+<Expandable title="AI Rules for Logs in Code Editors" copy={true}>
 
+When created as a rules file this should be placed alongside other editor specific rule files. For example, if you are using Cursor, place this file in the `.cursorrules` directory.
 
 ````markdown {filename:rules.md}
 
@@ -41,13 +42,15 @@ Sentry.init({
 
 ## Logger Examples
 
+`logger.fmt` is a template literal function that should be used to bring variables into the structured logs.
+
 ```javascript
 import * as Sentry from "@sentry/react";
 
 const { logger } = Sentry;
 
 logger.trace("Starting database connection", { database: "users" });
-logger.debug("Cache miss for user", { userId: 123 });
+logger.debug(logger.fmt`Cache miss for user: ${userId}`);
 logger.info("Updated profile", { profileId: 345 });
 logger.warn("Rate limit reached for endpoint", {
   endpoint: "/api/results/",

platform-includes/llm-rules-platform/_default.mdx

@@ -1,6 +1,6 @@
-<Expandable title="AI Rules for Cursor or Windsurf" copy={true}>
+<Expandable title="AI Rules for Code Editors" copy={true}>
 
-Sentry provides a set of rules you can use to help your LLM use Sentry correctly. Copy this file and add it to your projects rules configuration.
+Sentry provides a set of rules you can use to help your LLM use Sentry correctly. Copy this file and add it to your projects rules configuration. When created as a rules file this should be placed alongside other editor specific rule files. For example, if you are using Cursor, place this file in the `.cursorrules` directory.
 
 ````markdown {filename:rules.md}
 These examples should be used as guidance when configuring Sentry functionality within a project.
@@ -109,13 +109,15 @@ Sentry.init({
 
 ## Logger Examples
 
+`logger.fmt` is a template literal function that should be used to bring variables into the structured logs.
+
 ```javascript
 import * as Sentry from "@sentry/browser";
 
 const { logger } = Sentry;
 
 logger.trace("Starting database connection", { database: "users" });
-logger.debug("Cache miss for user", { userId: 123 });
+logger.debug(logger.fmt`Cache miss for user: ${userId}`);
 logger.info("Updated profile", { profileId: 345 });
 logger.warn("Rate limit reached for endpoint", {
   endpoint: "/api/results/",

platform-includes/llm-rules-platform/javascript.nextjs.mdx

@@ -1,6 +1,6 @@
-<Expandable title="AI Rules for Cursor or Windsurf" copy={true}>
+<Expandable title="AI Rules for Code Editors" copy={true}>
 
-Sentry provides a set of rules you can use to help your LLM use Sentry correctly. Copy this file and add it to your projects rules configuration.
+Sentry provides a set of rules you can use to help your LLM use Sentry correctly. Copy this file and add it to your projects rules configuration. When created as a rules file this should be placed alongside other editor specific rule files. For example, if you are using Cursor, place this file in the `.cursorrules` directory.
 
 ````markdown {filename:rules.md}
 These examples should be used as guidance when configuring Sentry functionality within a project.
@@ -112,9 +112,11 @@ Sentry.init({
 
 ## Logger Examples
 
+`logger.fmt` is a template literal function that should be used to bring variables into the structured logs. 
+
 ```javascript
 logger.trace("Starting database connection", { database: "users" });
-logger.debug("Cache miss for user", { userId: 123 });
+logger.debug(logger.fmt`Cache miss for user: ${userId}`);
 logger.info("Updated profile", { profileId: 345 });
 logger.warn("Rate limit reached for endpoint", {
   endpoint: "/api/results/",

platform-includes/llm-rules-platform/javascript.node.mdx

@@ -1,6 +1,6 @@
-<Expandable title="AI Rules for Cursor or Windsurf" copy={true}>
+<Expandable title="AI Rules for Code Editors" copy={true}>
 
-Sentry provides a set of rules you can use to help your LLM use Sentry correctly. Copy this file and add it to your projects rules configuration.
+Sentry provides a set of rules you can use to help your LLM use Sentry correctly. Copy this file and add it to your projects rules configuration. When created as a rules file this should be placed alongside other editor specific rule files. For example, if you are using Cursor, place this file in the `.cursorrules` directory.
 
 ````markdown {filename:rules.md}
 These examples should be used as guidance when configuring Sentry functionality within a project.
@@ -106,9 +106,11 @@ Sentry.init({
 
 ## Logger Examples
 
+`logger.fmt` is a template literal function that should be used to bring variables into the structured logs.
+
 ```javascript
 logger.trace("Starting database connection", { database: "users" });
-logger.debug("Cache miss for user", { userId: 123 });
+logger.debug(logger.fmt`Cache miss for user: ${userId}`);
 logger.info("Updated profile", { profileId: 345 });
 logger.warn("Rate limit reached for endpoint", {
   endpoint: "/api/results/",

platform-includes/llm-rules-platform/javascript.react.mdx

@@ -1,6 +1,6 @@
-<Expandable title="AI Rules for Cursor or Windsurf" copy={true}>
+<Expandable title="AI Rules for Code Editors" copy={true}>
 
-Sentry provides a set of rules you can use to help your LLM use Sentry correctly. Copy this file and add it to your projects rules configuration.
+Sentry provides a set of rules you can use to help your LLM use Sentry correctly. Copy this file and add it to your projects rules configuration. When created as a rules file this should be placed alongside other editor specific rule files. For example, if you are using Cursor, place this file in the `.cursorrules` directory.
 
 ````markdown {filename:rules.md}
 These examples should be used as guidance when configuring Sentry functionality within a project.
@@ -104,9 +104,11 @@ Sentry.init({
 
 ## Logger Examples
 
+`logger.fmt` is a template literal function that should be used to bring variables into the structured logs.
+
 ```javascript
 logger.trace("Starting database connection", { database: "users" });
-logger.debug("Cache miss for user", { userId: 123 });
+logger.debug(logger.fmt`Cache miss for user: ${userId}`);
 logger.info("Updated profile", { profileId: 345 });
 logger.warn("Rate limit reached for endpoint", {
   endpoint: "/api/results/",