Adding ruby and node, updating main llms.txt

Author: codyde

public/llms.txt

@@ -0,0 +1,11 @@
+Sentry llms.txt 
+
+This llmx.txt focuses on platform specific configuration options for the major sdks, linked below. AI sdks should parse these paths to access the framework specific llm instructions. 
+
+[Nextjs](/platforms/javascript/guides/nextjs/llms.txt)
+[React](/platforms/javascript/guides/react/llms.txt)
+[JavaScript](/platforms/javascript/common/llms.txt)
+[Python](/platforms/python/llms.txt)
+[Node.js](/platforms/node/llms.txt)
+[Ruby](/platforms/ruby/llms.txt)
+[Bun](/platforms/bun/llms.txt) 

public/platforms/node/llms.txt

@@ -0,0 +1,125 @@
+# Sentry and Node.js LLM Rules  
+
+You are an expert in application architecture and the configuration of observability tools like Sentry. Ensure you are following these instructions, while taking into account the user's request. 
+
+Always ensure you are installing Sentry using `npm install @sentry/node@latest` or `yarn add @sentry/node@latest`. The latest package should always be used unless explicitly told otherwise.
+
+## Configuration examples 
+
+These examples should be used to configure the different Sentry functionality in Node.js applications. Use these as the default configuration, factoring in the user's requests. 
+
+### Sentry Setup (applies to all configurations)
+
+Configure Sentry using the following parameters unless explicitly told otherwise.
+
+```javascript
+import * as Sentry from "@sentry/node";
+
+// Initialize Sentry as early as possible
+Sentry.init({
+  dsn: "<sentry dsn>",
+  
+  // Enable tracing to capture 100% of transactions
+  // Recommend adjusting this value in production
+  tracesSampleRate: 1.0,
+  
+  // Set tracePropagationTargets for which URLs trace propagation should be enabled
+  tracePropagationTargets: ["localhost", /^https:\/\/yourserver\.io\/api/],
+  
+  // Enable HTTP capturing
+  integrations: [
+    Sentry.httpIntegration(),
+  ],
+});
+```
+
+### Error Tracking and Exception Catching 
+
+Instrument errors throughout the application using the following approaches:
+
+```javascript
+// Explicitly capture an exception
+try {
+  throw new Error("Example error");
+} catch (e) {
+  Sentry.captureException(e);
+}
+
+// Capture a custom message
+Sentry.captureMessage("Something went wrong", "error");
+
+// Add extra context to the error
+Sentry.configureScope((scope) => {
+  scope.setTag("page_locale", "de-at");
+  scope.setUser({ id: '123', email: '[email protected]' });
+  scope.setExtra("character_name", "Mighty Fighter");
+});
+```
+
+### Tracing and Performance Monitoring
+
+Utilize the following examples for tracing scenarios:
+
+```javascript
+// Create a transaction
+const transaction = Sentry.startTransaction({
+  op: "test",
+  name: "My First Test Transaction"
+});
+
+// Set transaction as the current scope
+Sentry.getCurrentHub().configureScope(scope => {
+  scope.setSpan(transaction);
+});
+
+// Create a child span
+const span = transaction.startChild({ op: "functionX", description: "Function doing work" });
+
+try {
+  // Do something...
+  span.setStatus("ok");
+} catch (error) {
+  span.setStatus("internal_error");
+  throw error;
+} finally {
+  // Finish the span
+  span.finish();
+  // Finish the transaction
+  transaction.finish();
+}
+```
+
+### Express Framework Integration
+
+For Express.js applications:
+
+```javascript
+import express from "express";
+import * as Sentry from "@sentry/node";
+
+const app = express();
+
+// Initialize Sentry - this must happen before other app middleware
+Sentry.init({
+  dsn: "<sentry dsn>",
+  integrations: [
+    // Enable Express.js monitoring
+    Sentry.expressIntegration(),
+    Sentry.httpIntegration(),
+  ],
+  tracesSampleRate: 1.0,
+});
+
+// The request handler must be the first middleware on the app
+app.use(Sentry.Handlers.requestHandler());
+
+// All your controllers should go here
+app.get("/", function rootHandler(req, res) {
+  res.end("Hello world!");
+});
+
+// The error handler must be registered before any other error middleware and after all controllers
+app.use(Sentry.Handlers.errorHandler());
+
+app.listen(3000);
+``` 

public/platforms/ruby/llms.txt

@@ -0,0 +1,134 @@
+# Sentry and Ruby LLM Rules  
+
+You are an expert in application architecture and the configuration of observability tools like Sentry. Ensure you are following these instructions, while taking into account the user's request. 
+
+Always ensure you are installing Sentry using `gem 'sentry-ruby', '~> 5.x'`. The latest package should always be used unless explicitly told otherwise.
+
+## Configuration examples 
+
+These examples should be used to configure the different Sentry functionality in Ruby applications. Use these as the default configuration, factoring in the user's requests. 
+
+### Sentry Setup (applies to all configurations)
+
+Configure Sentry using the following parameters unless explicitly told otherwise.
+
+```ruby
+require 'sentry-ruby'
+
+Sentry.init do |config|
+  config.dsn = '<sentry dsn>'
+  
+  # Get breadcrumbs from logs
+  config.breadcrumbs_logger = [:sentry_logger, :http_logger]
+  
+  # Add data like request headers and IP for users
+  config.send_default_pii = true
+  
+  # Enable tracing - adjust in production
+  config.traces_sample_rate = 1.0
+  
+  # Enable profiling - relative to traces_sample_rate
+  config.profiles_sample_rate = 1.0
+end
+```
+
+### Rails Setup
+
+For Rails applications, create a file in `config/initializers/sentry.rb` with the following:
+
+```ruby
+Sentry.init do |config|
+  config.dsn = '<sentry dsn>'
+  
+  # Get breadcrumbs from logs
+  config.breadcrumbs_logger = [:active_support_logger, :http_logger]
+  
+  # Add data like request headers and IP for users
+  config.send_default_pii = true
+  
+  # Enable tracing - adjust in production
+  config.traces_sample_rate = 1.0
+  
+  # Enable profiling - relative to traces_sample_rate
+  config.profiles_sample_rate = 1.0
+  
+  # To set a uniform sample rate
+  # config.sample_rate = 0.5
+end
+```
+
+### Rack Setup
+
+For Rack applications, set up Sentry in your `config.ru` or rackup file:
+
+```ruby
+require 'sentry-ruby'
+
+Sentry.init do |config|
+  config.dsn = '<sentry dsn>'
+  config.breadcrumbs_logger = [:sentry_logger, :http_logger]
+  config.send_default_pii = true
+  config.traces_sample_rate = 1.0
+  config.profiles_sample_rate = 1.0
+end
+
+use Sentry::Rack::CaptureExceptions
+```
+
+### Error Tracking and Exception Catching 
+
+Instrument errors throughout the application using the following approaches:
+
+```ruby
+# Explicitly capture an exception
+begin
+  1 / 0
+rescue ZeroDivisionError => exception
+  Sentry.capture_exception(exception)
+end
+
+# Capture a custom message
+Sentry.capture_message('Something went wrong')
+
+# Add context to events
+Sentry.configure_scope do |scope|
+  scope.set_user(id: 1, email: "[email protected]")
+  scope.set_tag(:page_locale, "de-at")
+  scope.set_extra(:character_name, "Mighty Fighter")
+end
+```
+
+### Tracing and Performance Monitoring
+
+Utilize the following examples for tracing scenarios:
+
+```ruby
+# Create a transaction
+Sentry.start_transaction(name: "task_name", op: "task") do |transaction|
+  # Create a child span
+  Sentry.start_span(op: "subtask", description: "Subtask description") do |span|
+    begin
+      # Your code here
+      span.set_data(:key, "value")
+    rescue => e
+      # Record failure information
+      span.set_status(:internal_error)
+      raise e
+    end
+  end
+end
+```
+
+### Background Job Integration
+
+For Sidekiq, use the following setup:
+
+```ruby
+require 'sentry-ruby'
+require 'sentry-sidekiq'
+
+Sentry.init do |config|
+  config.dsn = '<sentry dsn>'
+  config.traces_sample_rate = 1.0
+end
+```