vybekiit 0.7.25 → 0.7.27

package/dist/global-skills/instrument-product-analytics/references/ruby.md

@@ -1,10 +1,6 @@
 > AI agents: this is one page from PostHog's docs. Full index of Markdown docs for LLMs: https://posthog.com/llms.txt
 
-# Ruby - Docs
-
-Copy page
-
-# Ruby - Docs
+# Ruby
 
 The `posthog-ruby` library provides tracking functionality on the server-side for applications built in Ruby.
 
@@ -18,8 +14,6 @@ Add this to your `Gemfile`:
 
 Terminal
 
-PostHog AI
-
 ```bash
 gem "posthog-ruby"
 ```
@@ -28,10 +22,9 @@ In your app, set your API key **before** making any calls. If setting a custom `
 
 Ruby
 
-PostHog AI
-
 ```ruby
 require 'posthog'
+
 posthog = PostHog::Client.new({
   api_key: "<ph_project_token>",
   host: "https://us.i.posthog.com",
@@ -47,10 +40,9 @@ Initialize the client with your project token before making any calls:
 
 Ruby
 
-PostHog AI
-
 ```ruby
 require 'posthog'
+
 posthog = PostHog::Client.new({
   api_key: '<ph_project_token>',
   host: 'https://us.i.posthog.com',
@@ -62,20 +54,20 @@ Available client options:
 
 | Option | Type | Default | Description |
 | --- | --- | --- | --- |
-| api_key | String | required | Your PostHog project token. |
-| host | String | https://us.i.posthog.com | Fully qualified PostHog API host. Include the protocol, for example https://us.i.posthog.com or https://eu.i.posthog.com. |
-| personal_api_key | String | nil | Personal API key. Required for local feature flag evaluation and remote config payloads. |
-| max_queue_size | Integer | 10000 | Maximum number of events to keep in the async queue before dropping new events. |
-| batch_size | Integer | 100 | Maximum number of events to send in one async batch. |
-| test_mode | Boolean | false | Keep events queued and do not send them. Useful for tests. |
-| sync_mode | Boolean | false | Send events synchronously on the calling thread. Useful in forking environments like Sidekiq and Resque. |
-| on_error | Proc | no-op | Callback called as on_error.call(status, error) for API or serialization errors. |
-| feature_flags_polling_interval | Integer | 30 | Seconds between local feature flag definition polls. |
-| feature_flag_request_timeout_seconds | Integer | 3 | Timeout, in seconds, for feature flag requests. |
-| before_send | Proc | nil | Callback that receives the event hash before it is queued or sent. Return a modified event hash, or nil to drop the event. |
-| disable_singleton_warning | Boolean | false | Suppress warnings about multiple clients with the same API key. Use only when you intentionally need multiple clients. |
-| skip_ssl_verification | Boolean | false | Disable SSL certificate verification. Intended only for local development or custom deployments. |
-| flag_definition_cache_provider | Object | nil | Provider for distributed feature flag definition caching. See [distributed flag definition caching](#distributed-flag-definition-caching). |
+| `api_key` | String | **required** | Your PostHog project token. |
+| `host` | String | `https://us.i.posthog.com` | Fully qualified PostHog API host. Include the protocol, for example `https://us.i.posthog.com` or `https://eu.i.posthog.com`. |
+| `personal_api_key` | String | `nil` | Personal API key. Required for local feature flag evaluation and remote config payloads. |
+| `max_queue_size` | Integer | `10000` | Maximum number of events to keep in the async queue before dropping new events. |
+| `batch_size` | Integer | `100` | Maximum number of events to send in one async batch. |
+| `test_mode` | Boolean | `false` | Keep events queued and do not send them. Useful for tests. |
+| `sync_mode` | Boolean | `false` | Send events synchronously on the calling thread. Useful in forking environments like Sidekiq and Resque. |
+| `on_error` | Proc | no-op | Callback called as `on_error.call(status, error)` for API or serialization errors. |
+| `feature_flags_polling_interval` | Integer | `30` | Seconds between local feature flag definition polls. |
+| `feature_flag_request_timeout_seconds` | Integer | `3` | Timeout, in seconds, for feature flag requests. |
+| `before_send` | Proc | `nil` | Callback that receives the event hash before it is queued or sent. Return a modified event hash, or `nil` to drop the event. |
+| `disable_singleton_warning` | Boolean | `false` | Suppress warnings about multiple clients with the same API key. Use only when you intentionally need multiple clients. |
+| `skip_ssl_verification` | Boolean | `false` | Disable SSL certificate verification. Intended only for local development or custom deployments. |
+| `flag_definition_cache_provider` | Object | `nil` | Provider for distributed feature flag definition caching. See [distributed flag definition caching](#distributed-flag-definition-caching). |
 
 ### Filtering or modifying events before sending
 
@@ -83,14 +75,13 @@ Use `before_send` to add, modify, or drop events immediately before the SDK queu
 
 Ruby
 
-PostHog AI
-
 ```ruby
 posthog = PostHog::Client.new({
   api_key: '<ph_project_token>',
   before_send: Proc.new do |event|
     event[:properties] ||= {}
     event[:properties]['environment'] = ENV['RACK_ENV']
+
     # Return nil to drop the event
     event[:properties]['internal_user'] == true ? nil : event
   end
@@ -103,8 +94,6 @@ For short-lived scripts, call `flush` before the process exits. Call `shutdown`
 
 Ruby
 
-PostHog AI
-
 ```ruby
 posthog.capture({ distinct_id: 'user_123', event: 'script_finished' })
 posthog.flush
@@ -121,8 +110,6 @@ Identify a user and set their person properties with `identify`:
 
 Ruby
 
-PostHog AI
-
 ```ruby
 posthog.identify({
   distinct_id: 'distinct_id_of_your_user',
@@ -139,8 +126,6 @@ You can send custom events using `capture`:
 
 Ruby
 
-PostHog AI
-
 ```ruby
 posthog.capture({
     distinct_id: 'distinct_id_of_the_user',
@@ -156,8 +141,6 @@ Optionally, you can include additional information with the event by including a
 
 Ruby
 
-PostHog AI
-
 ```ruby
 posthog.capture({
     distinct_id: 'distinct_id_of_the_user',
@@ -175,8 +158,6 @@ If you're aiming for a backend-only implementation of PostHog and won't be captu
 
 Ruby
 
-PostHog AI
-
 ```ruby
 posthog.capture({
     distinct_id: 'distinct_id_of_the_user',
@@ -191,24 +172,22 @@ posthog.capture({
 
 | Field | Type | Description |
 | --- | --- | --- |
-| distinct_id | String | The user ID. If omitted, framework integrations can provide request context; otherwise the SDK generates a UUID and marks the event as personless. |
-| event | String | Event name. Required. |
-| properties | Hash | Event properties. |
-| groups | Hash | Group analytics mapping from group type to group key. |
-| timestamp | Time | When the event occurred. Defaults to the current time. |
-| message_id | String | Optional message ID. |
-| uuid | String | Optional event UUID used for deduplication. Must be a valid UUID. |
-| flags | PostHog::FeatureFlagEvaluations | Snapshot returned by evaluate_flags. Adds $feature/<key> and $active_feature_flags properties without another /flags request. |
-| send_feature_flags | Boolean, Hash, or PostHog::SendFeatureFlagsOptions | Deprecated. Prefer passing flags: from evaluate_flags. |
+| `distinct_id` | String | The user ID. If omitted, framework integrations can provide request context; otherwise the SDK generates a UUID and marks the event as personless. |
+| `event` | String | Event name. Required. |
+| `properties` | Hash | Event properties. |
+| `groups` | Hash | Group analytics mapping from group type to group key. |
+| `timestamp` | Time | When the event occurred. Defaults to the current time. |
+| `message_id` | String | Optional message ID. |
+| `uuid` | String | Optional event UUID used for deduplication. Must be a valid UUID. |
+| `flags` | `PostHog::FeatureFlagEvaluations` | Snapshot returned by `evaluate_flags`. Adds `$feature/<key>` and `$active_feature_flags` properties without another `/flags` request. |
+| `send_feature_flags` | Boolean, Hash, or `PostHog::SendFeatureFlagsOptions` | Deprecated. Prefer passing `flags:` from `evaluate_flags`. |
 
 ## Person profiles and properties
 
-The Ruby SDK captures identified events by default. These create [person profiles](/docs/data/persons.md). To set [person properties](/docs/data/user-properties.md) in these profiles, include them when capturing an event:
+The Ruby SDK captures identified events by default. These create [person profiles](/docs/data/persons.md). To set [person properties](/docs/product-analytics/person-properties.md) in these profiles, include them when capturing an event:
 
 Ruby
 
-PostHog AI
-
 ```ruby
 posthog.capture({
     distinct_id: 'distinct_id',
@@ -220,14 +199,12 @@ posthog.capture({
 })
 ```
 
-For more details on the difference between `$set` and `$set_once`, see our [person properties docs](/docs/data/user-properties.md#what-is-the-difference-between-set-and-set_once).
+For more details on the difference between `$set` and `$set_once`, see our [person properties docs](/docs/product-analytics/person-properties.md#what-is-the-difference-between-set-and-set_once).
 
 To capture [anonymous events](/docs/data/anonymous-vs-identified-events.md) without person profiles, set the event's `$process_person_profile` property to `false`:
 
 Ruby
 
-PostHog AI
-
 ```ruby
 posthog.capture({
     distinct_id: 'distinct_id',
@@ -246,8 +223,6 @@ In this case, you can use `alias` to assign another distinct ID to the same user
 
 Ruby
 
-PostHog AI
-
 ```ruby
 posthog.alias({
   distinct_id: 'distinct_id',
@@ -255,7 +230,7 @@ posthog.alias({
 })
 ```
 
-We strongly recommend reading our docs on [alias](/docs/data/identify.md#alias-assigning-multiple-distinct-ids-to-the-same-user) to best understand how to correctly use this method.
+We strongly recommend reading our docs on [alias](/docs/product-analytics/identify.md#alias-assigning-multiple-distinct-ids-to-the-same-user) to best understand how to correctly use this method.
 
 ## Feature flags
 
@@ -271,10 +246,9 @@ Call `posthog.evaluate_flags()` once for the user, then read values from the ret
 
 Ruby
 
-PostHog AI
-
 ```ruby
 flags = posthog.evaluate_flags('distinct_id_of_your_user')
+
 if flags.enabled?('flag-key')
     # Do something differently for this user
     # Optional: fetch the payload
@@ -286,11 +260,11 @@ end
 
 Ruby
 
-PostHog AI
-
 ```ruby
 flags = posthog.evaluate_flags('distinct_id_of_your_user')
+
 enabled_variant = flags.get_flag('flag-key')
+
 if enabled_variant == 'variant-key' # replace 'variant-key' with the key of your variant
     # Do something differently for this user
     # Optional: fetch the payload
@@ -316,13 +290,13 @@ Pass the same `flags` object that you used for branching. This attaches the exac
 
 Ruby
 
-PostHog AI
-
 ```ruby
 flags = posthog.evaluate_flags('distinct_id_of_your_user')
+
 if flags.enabled?('flag-key')
     # Do something differently for this user
 end
+
 posthog.capture({
     distinct_id: 'distinct_id_of_your_user',
     event: 'event_name',
@@ -336,8 +310,6 @@ To reduce event property bloat, pass a filtered snapshot:
 
 Ruby
 
-PostHog AI
-
 ```ruby
 # Attach only flags accessed with enabled?() or get_flag() before this call
 posthog.capture({
@@ -345,6 +317,7 @@ posthog.capture({
     event: 'event_name',
     flags: flags.only_accessed,
 })
+
 # Attach only specific flags
 posthog.capture({
     distinct_id: 'distinct_id_of_your_user',
@@ -361,8 +334,6 @@ In the event properties, include `$feature/feature_flag_name: variant_key`:
 
 Ruby
 
-PostHog AI
-
 ```ruby
 posthog.capture({
     distinct_id: 'distinct_id_of_your_user',
@@ -380,8 +351,6 @@ By default, `evaluate_flags()` evaluates every flag for the user. If you only ne
 
 Ruby
 
-PostHog AI
-
 ```ruby
 flags = posthog.evaluate_flags(
     'distinct_id_of_your_user',
@@ -395,8 +364,6 @@ If you want to skip the remote `/flags` request and only use locally cached defi
 
 Ruby
 
-PostHog AI
-
 ```ruby
 flags = posthog.evaluate_flags(
     'distinct_id_of_your_user',
@@ -410,8 +377,6 @@ Pass `disable_geoip: true` to disable GeoIP lookup for remote flag evaluation:
 
 Ruby
 
-PostHog AI
-
 ```ruby
 flags = posthog.evaluate_flags(
     'distinct_id_of_your_user',
@@ -437,8 +402,6 @@ For example:
 
 Ruby
 
-PostHog AI
-
 ```ruby
 flags = posthog.evaluate_flags(
     'distinct_id_of_the_user',
@@ -458,6 +421,7 @@ flags = posthog.evaluate_flags(
         },
     },
 )
+
 if flags.enabled?('flag-key')
     # Do something differently for this user
 end
@@ -496,8 +460,6 @@ You can configure the `feature_flag_request_timeout_seconds` parameter when init
 
 Ruby
 
-PostHog AI
-
 ```ruby
 posthog = PostHog::Client.new({
     # rest of your configuration...
@@ -511,11 +473,11 @@ The following methods are still available during the migration period, but are d
 
 | Method | Replacement |
 | --- | --- |
-| posthog.is_feature_enabled(flag_key, distinct_id, ...) | posthog.evaluate_flags(distinct_id, ...).enabled?(flag_key) |
-| posthog.get_feature_flag(flag_key, distinct_id, ...) | posthog.evaluate_flags(distinct_id, ...).get_flag(flag_key) |
-| posthog.get_feature_flag_payload(flag_key, distinct_id, ...) | posthog.evaluate_flags(distinct_id, ...).get_flag_payload(flag_key) |
-| posthog.get_feature_flag_result(flag_key, distinct_id, ...) | posthog.evaluate_flags(distinct_id, ...) and read get_flag / get_flag_payload |
-| posthog.capture({ ..., send_feature_flags: true }) | posthog.capture({ ..., flags: flags }) |
+| `posthog.is_feature_enabled(flag_key, distinct_id, ...)` | `posthog.evaluate_flags(distinct_id, ...).enabled?(flag_key)` |
+| `posthog.get_feature_flag(flag_key, distinct_id, ...)` | `posthog.evaluate_flags(distinct_id, ...).get_flag(flag_key)` |
+| `posthog.get_feature_flag_payload(flag_key, distinct_id, ...)` | `posthog.evaluate_flags(distinct_id, ...).get_flag_payload(flag_key)` |
+| `posthog.get_feature_flag_result(flag_key, distinct_id, ...)` | `posthog.evaluate_flags(distinct_id, ...)` and read `get_flag` / `get_flag_payload` |
+| `posthog.capture({ ..., send_feature_flags: true })` | `posthog.capture({ ..., flags: flags })` |
 
 ### Local Evaluation
 
@@ -531,8 +493,6 @@ If you have `preload_app true` in your unicorn config, you can use the [`after_f
 
 Ruby
 
-PostHog AI
-
 ```ruby
 after_fork do |_server, _worker|
   $posthog = PostHog::Client.new({
@@ -550,8 +510,6 @@ If you use Puma with multiple workers, you can use the `on_worker_boot` hook (wh
 
 Ruby
 
-PostHog AI
-
 ```ruby
 on_worker_boot do
   $posthog = PostHog::Client.new({
@@ -574,8 +532,6 @@ end
 
 Ruby
 
-PostHog AI
-
 ```ruby
 posthog = PostHog::Client.new({
   api_key: '<ph_project_token>',
@@ -590,8 +546,6 @@ Use `get_remote_config_payload` to fetch the decrypted remote config payload for
 
 Ruby
 
-PostHog AI
-
 ```ruby
 payload = posthog.get_remote_config_payload('flag-key')
 ```
@@ -602,11 +556,10 @@ Since [experiments](/docs/experiments/start-here.md) use feature flags, the code
 
 Ruby
 
-PostHog AI
-
 ```ruby
 flags = posthog.evaluate_flags('user_distinct_id')
 variant = flags.get_flag('experiment-feature-flag-key')
+
 if variant == 'variant-name'
     # Do something
 end
@@ -624,8 +577,6 @@ Capture an event and associate it with a group:
 
 Ruby
 
-PostHog AI
-
 ```ruby
 posthog.capture({
     distinct_id: 'distinct_id_of_the_user',
@@ -644,8 +595,6 @@ Update properties on a group:
 
 Ruby
 
-PostHog AI
-
 ```ruby
 posthog.group_identify({
   group_type: 'company',
@@ -672,8 +621,6 @@ For non-Rails Ruby applications, you can manually capture exceptions with `captu
 
 Ruby
 
-PostHog AI
-
 ```ruby
 begin
   # Code that might raise an exception
@@ -693,17 +640,15 @@ The `capture_exception` method accepts the following parameters:
 
 | Parameter | Type | Description |
 | --- | --- | --- |
-| exception | Exception, String, or exception-like object | The exception to capture. Required. |
-| distinct_id | String | The distinct ID of the user. Optional; request context can provide a default, otherwise the SDK generates a UUID. |
-| additional_properties | Hash | Additional properties to attach to the exception event. Optional. |
-| flags | PostHog::FeatureFlagEvaluations | Optional keyword argument. Adds the same feature flag properties as capture({ flags: flags }). |
+| `exception` | `Exception`, `String`, or exception-like object | The exception to capture. Required. |
+| `distinct_id` | `String` | The distinct ID of the user. Optional; request context can provide a default, otherwise the SDK generates a UUID. |
+| `additional_properties` | `Hash` | Additional properties to attach to the exception event. Optional. |
+| `flags` | `PostHog::FeatureFlagEvaluations` | Optional keyword argument. Adds the same feature flag properties as `capture({ flags: flags })`. |
 
 You can also override the [fingerprint](/docs/error-tracking/fingerprints.md) to customize how exceptions are grouped into issues:
 
 Ruby
 
-PostHog AI
-
 ```ruby
 posthog.capture_exception(
   e,
@@ -720,8 +665,6 @@ The Ruby SDK logs warnings by default. You can change the log level to `DEBUG` t
 
 Ruby
 
-PostHog AI
-
 ```ruby
 posthog.logger.level = Logger::DEBUG
 ```
@@ -730,8 +673,6 @@ You can also replace the SDK logger globally:
 
 Ruby
 
-PostHog AI
-
 ```ruby
 PostHog::Logging.logger = Rails.logger
 ```
@@ -742,11 +683,10 @@ When `test_mode: true`, events remain queued. You can inspect and clear the queu
 
 Ruby
 
-PostHog AI
-
 ```ruby
 posthog = PostHog::Client.new({ api_key: '<ph_project_token>', test_mode: true })
 posthog.capture({ distinct_id: 'user_123', event: 'test_event' })
+
 posthog.queued_messages
 posthog.dequeue_last_message
 posthog.clear

package/dist/global-skills/instrument-product-analytics/references/svelte.md

@@ -1,10 +1,6 @@
 > AI agents: this is one page from PostHog's docs. Full index of Markdown docs for LLMs: https://posthog.com/llms.txt
 
-# Svelte - Docs
-
-Copy page
-
-# Svelte - Docs
+# Svelte
 
 PostHog makes it easy to get data about traffic and usage of your [Svelte](https://svelte.dev/) app. Integrating PostHog into your site enables analytics about user behavior, custom events capture, session recordings, feature flags, and more.
 
@@ -24,8 +20,6 @@ Or, to integrate manually, continue with the rest of this guide.
 
 Install `posthog-js` using your package manager:
 
-PostHog AI
-
 ### npm
 
 ```bash
@@ -52,8 +46,6 @@ bun add posthog-js
 
 > **If your site sets a Content-Security-Policy**, it needs to allow PostHog. This applies to the snippet and to package installs alike: the SDK lazy-loads extra bundles (session replay, surveys) from PostHog's CDN, and sends events to the ingestion host. PostHog serves from subdomains of `posthog.com` that change over time, so allow the wildcard:
 >
-> PostHog AI
->
 > ```
 > script-src 'self' https://*.posthog.com;
 > connect-src 'self' https://*.posthog.com;
@@ -66,11 +58,10 @@ Then, if you haven't created a root [layout](https://kit.svelte.dev/docs/routing
 
 routes/+layout.js
 
-PostHog AI
-
 ```javascript
 import posthog from 'posthog-js'
 import { browser } from '$app/environment';
+
 export const load = async () => {
   if (browser) {
     posthog.init('<ph_project_token>', {
@@ -78,6 +69,7 @@ export const load = async () => {
       defaults: '2026-05-30',
     })
   }
+
   return
 };
 ```
@@ -96,8 +88,6 @@ If your app calls your own backend, `tracing_headers` adds `X-POSTHOG-DISTINCT-I
 
 JavaScript
 
-PostHog AI
-
 ```javascript
 posthog.init('<ph_project_token>', {
   api_host: 'https://us.i.posthog.com',
@@ -134,14 +124,16 @@ For certain features like [heatmaps](/docs/toolbar/heatmaps.md), your Web Applic
 
 **US**: `44.205.89.55`, `52.4.194.122`, `44.208.188.173`
 
-These are public, stable IPs used by PostHog services (e.g., Celery tasks for snapshots).
+These are public, stable IPs used by PostHog services.
+
+PostHog captures heatmap screenshots using [Browserless](https://www.browserless.io), which has its own IP addresses. Browserless [publishes the current list here](https://docs.browserless.io/baas/troubleshooting/whitelisting-ips).
+
+An allowlist does not help when your app has a private address. For apps on an internal network, see [internal and intranet applications](/docs/session-replay/troubleshooting.md#internal-and-intranet-applications).
 
 ## Server-side setup
 
 Install `posthog-node` using your package manager:
 
-PostHog AI
-
 ### npm
 
 ```bash
@@ -170,16 +162,17 @@ Then, initialize the PostHog Node client where you'd like to use it on the serve
 
 routes/+page.server.js
 
-PostHog AI
-
 ```javascript
 import { PostHog } from 'posthog-node';
+
 export async function load() {
   const posthog = new PostHog('<ph_project_token>', { host: 'https://us.i.posthog.com' });
+
   posthog.capture({
     distinctId: 'distinct_id_of_the_user',
     event: 'event_name',
   })
+
   await posthog.shutdown()
 }
 ```
@@ -192,20 +185,21 @@ To use client-side feature flags, import PostHog into your Svelte component and
 
 routes/+page.svelte
 
-PostHog AI
-
 ```javascript
 <script>
   import posthog from 'posthog-js'
   import { browser } from '$app/environment'
   import { onMount } from 'svelte'
+
   let coolFeature = $state(false)
+
   onMount(() => {
     if (browser) {
       coolFeature = posthog.isFeatureEnabled('cool-feature')
     }
   })
 </script>
+
 {#if coolFeature}
   <p>Welcome to the cool feature!</p>
 {/if}
@@ -215,20 +209,22 @@ To use server-side feature flags, import PostHog into your SvelteKit `load` func
 
 routes/+page.server.js
 
-PostHog AI
-
 ```javascript
 import { PostHog } from 'posthog-node';
+
 const client = new PostHog(
   '<ph_project_token>',
   { host: 'https://us.i.posthog.com' }
 );
+
 export async function load() {
   const distinctId = 'distinct_id_of_the_user';
+
   const megaFeature = await client.isFeatureEnabled(
     'mega-feature',
     distinctId
   );
+
   return {
     megaFeature
   };
@@ -245,8 +241,6 @@ To fix this, set the config to not use relative paths in `svelte.config.js`:
 
 JavaScript
 
-PostHog AI
-
 ```javascript
 kit: {
      paths: {