vybekiit 0.7.4 → 0.7.7

package/dist/global-skills/firebase-ai-logic-basics/references/flutter_setup.md

@@ -62,9 +62,12 @@ Use `FirebaseAI.googleAI` for the **Gemini Developer API**.
 
 > [!IMPORTANT] **Choose the Right API Provider:** Always use
 > `FirebaseAI.googleAI` (Gemini Developer API) as the default for prototyping
-> and standard use. Avoid using the Vertex AI Gemini API unless your application
-> specifically requires enterprise-grade scalability and is configured for the
-> Blaze plan.
+> and standard use. Avoid using the Agent Platform Gemini API (formerly branded
+> Vertex AI) unless the app and business use case specifically require
+> enterprise-grade scalability or data residency requirements. Note that the
+> Gemini Developer API *usually does not* require the Firebase project to be on
+> the pay-as-you-go Blaze pricing plan; however, the Agent Platform Gemini API
+> does require the Blaze plan.
 
 ### Text Generation
 

package/dist/global-skills/firebase-app-hosting-basics/SKILL.md

@@ -1,6 +1,9 @@
 ---
 name: firebase-app-hosting-basics
-description: Deploy and manage web apps with Firebase App Hosting. Use this skill when deploying Next.js/Angular apps with backends.
+description: >-
+  Deploys and manages full-stack web applications (Next.js, Angular) with Server-Side Rendering (SSR) using Firebase App Hosting. Use when deploying Next.js/Angular apps, configuring apphosting.yaml or firebase.json apphosting blocks, managing secrets, setting up GitHub CI/CD, or configuring Blaze billing requirements. Don't use for classic static web hosting, Auth, Firestore, Crashlytics, or Xcode.
+metadata:
+  category: Serverless
 ---
 
 # App Hosting Basics
@@ -36,6 +39,7 @@ to upgrade their plan.
 This is the recommended flow for most users.
 
 1. Configure `firebase.json` with an `apphosting` block.
+   
    ```json
    {
      "apphosting": {

package/dist/global-skills/firebase-auth-basics/SKILL.md

@@ -2,6 +2,8 @@
 name: firebase-auth-basics
 description: Guide for setting up and using Firebase Authentication. Use this skill when the user's app requires user sign-in, user management, or secure data access using auth rules.
 compatibility: This skill is best used with the Firebase CLI, but does not require it. Firebase CLI can be accessed through `npx -y firebase-tools@latest`.
+metadata:
+  category: Identity
 ---
 
 ## Prerequisites
@@ -64,13 +66,13 @@ Configure Firebase Authentication in `firebase.json` by adding an 'auth' block:
 ```
 {
   "auth": {
+  "authorizedDomains": ["localhost"],
     "providers": {
       "anonymous": true,
       "emailPassword": true,
       "googleSignIn": {
         "oAuthBrandDisplayName": "Your Brand Name",
-        "supportEmail": "support@example.com",
-        "authorizedRedirectUris": ["https://example.com", "http://localhost"]
+        "supportEmail": "support@example.com"
       }
     }
   }

package/dist/global-skills/firebase-basics/SKILL.md

@@ -1,11 +1,9 @@
 ---
 name: firebase-basics
 description: >-
-  Provides foundational setup, authentication, and project management workflows
-  for Firebase using the Firebase CLI. Use when checking Firebase CLI version
-  (must use 'npx -y firebase-tools@latest --version'), initializing a Firebase
-  environment, authenticating, setting active projects, or setting up `google-services.json`
-  or `GoogleService-Info.plist` files.
+  Provides foundational Firebase CLI setup, CLI installation, version checks (`firebase-tools@latest --version`), CLI login (including --no-localhost), project creation, project selection (`firebase use`), and app config file downloads (`google-services.json`, `GoogleService-Info.plist`). Use ONLY for CLI login, project creation/switching, or downloading app config files. Don't use for Firebase Hosting deploy, Firestore, Auth, App Hosting, Data Connect, Crashlytics, or Remote Config.
+metadata:
+  category: CloudInfrastructureAndServices
 ---
 
 # Prerequisites
@@ -63,6 +61,7 @@ Complete these setup steps before proceeding:
         user if this is the intended project.
      1. If not, or if no project is active, set the project provided by the
         user:
+        
         ```bash
         npx -y firebase-tools@latest use <PROJECT_ID>
         ```
@@ -143,6 +142,7 @@ Adhere to these principles:
 - **Login Issues:** If the browser fails to open during the login step, use
   `npx -y firebase-tools@latest login --no-localhost` instead.
 - **Genkit:** If using Genkit, install the skills:
+  
   ```bash
   npx skills add genkit-ai/skills
   ```

package/dist/global-skills/firebase-crashlytics/SKILL.md

@@ -2,6 +2,8 @@
 name: firebase-crashlytics
 description: Comprehensive guide for Firebase Crashlytics, including provisioning and SDK usage. Use this skill when the user needs help setting up Crashlytics, adding crash reporting, or using the Crashlytics SDK in their application.
 compatibility: This skill is best used with the Firebase CLI, but does not require it. Firebase CLI can be accessed through `npx -y firebase-tools@latest`.
+metadata:
+  category: CloudObservabilityAndMonitoring
 ---
 
 # Crashlytics

package/dist/global-skills/firebase-data-connect/SKILL.md

@@ -1,6 +1,8 @@
 ---
 name: firebase-data-connect
 description: Builds and deploys Firebase SQL Connect (aka Firebase Data Connect) backends with PostgreSQL securely. Use when designing schemas with tables and relations, writing authorized queries and mutations, configuring real-time data updates, or generating type-safe SDKs. Use when you need a relational database with Firebase, or when the user mentions SQL Connect or Data Connect.
+metadata:
+  category: Databases
 ---
 
 # Firebase SQL Connect

package/dist/global-skills/firebase-firestore/SKILL.md

@@ -1,13 +1,10 @@
 ---
 name: firebase-firestore
 description: >-
-  Sets up, manages, and executes queries against Cloud Firestore database
-  instances, including advanced native full-text search and relational joins
-  using pipelines. You MUST unconditionally activate this skill if you plan to
-  use Firestore in any way. Use when listing or creating Firestore databases,
-  configuring security rules, designing data models, writing client SDK
-  queries (including search/joins), or checking indexes.
+  Sets up, manages, queries, and configures Cloud Firestore databases (Standard/Enterprise edition), including data modeling, security rules, indexes, and SDK integrations (Web, Python, iOS, Android, Flutter). Use when creating/listing Firestore databases, defining data models/indexes, writing SDK queries, or integrating Firestore SDKs. Don't use for Firebase Hosting, Data Connect, Auth, Storage/GCS, Crashlytics, Functions, or BigQuery.
 compatibility: This skill is best used with the Firebase CLI, but does not require it. Firebase CLI can be accessed through `npx -y firebase-tools@latest`.
+metadata:
+  category: Databases
 ---
 
 # Cloud Firestore Database and Operations

package/dist/global-skills/firebase-hosting-basics/SKILL.md

@@ -1,6 +1,9 @@
 ---
 name: firebase-hosting-basics
-description: Skill for working with Firebase Hosting (Classic). Use this when you want to deploy static web apps, Single Page Apps (SPAs), or simple microservices. Do NOT use for Firebase App Hosting.
+description: >-
+  Deploys and configures classic Firebase Hosting for static websites, single-page apps (SPAs), and microservices. Use when deploying static sites/SPAs, setting up custom domains, configuring firebase.json hosting settings (redirects, rewrites, headers, multi-site), or managing preview channels. Don't use for Firebase App Hosting (Next.js/SSR), Auth, Firestore queries/rules, Data Connect, or Crashlytics.
+metadata:
+  category: Serverless
 ---
 
 # hosting-basics

package/dist/global-skills/firebase-remote-config-basics/SKILL.md

@@ -1,7 +1,10 @@
 ---
 name: firebase-remote-config-basics
-description: Comprehensive guide for Firebase Remote Config, including template management and SDK usage. Use this skill when the user needs help setting up Remote Config, managing feature flags, or updating app behavior dynamically.
+description: >-
+  Manages Firebase Remote Config templates, feature flags, loading strategies, and SDKs (Android, iOS). Use when downloading/deploying remoteconfig JSON templates, managing version history/feature flags, setting in-app defaults, fetchAndActivate(), real-time listeners, or SDK setup. Don't use for Firebase Hosting, Auth, Firestore, Data Connect, Crashlytics, or App Hosting.
 compatibility: This skill is best used with the Firebase CLI, but does not require it. Firebase CLI can be accessed through `npx -y firebase-tools@latest`.
+metadata:
+  category: ApplicationDevelopment
 ---
 
 # Remote Config
@@ -102,6 +105,7 @@ history through the terminal:
   ```
 
   - Deploy: Execute the partial deployment command
+    
     ```bash
     npx -y firebase-tools@latest deploy --only remoteconfig
     ```

package/dist/global-skills/firebase-security-rules-auditor/SKILL.md

@@ -1,6 +1,9 @@
 ---
 name: firebase-security-rules-auditor
-description: A skill to evaluate how secure Firestore security rules are. Use this when Firestore security rules are updated to ensure that the generated rules are extremely secure and robust.
+description: >-
+  Audits Firebase (Firestore, Cloud Storage) security rules for vulnerabilities, privilege escalation, role bypasses, create vs update inconsistencies, resource exhaustion, type safety, size limits, and hasOnly ownership checks. Use when auditing/reviewing rules, running red-team rule assessments, or scoring against auditor checklists. Don't use for Firebase CLI (login, deploy), Auth, Crashlytics, Remote Config, or database queries.
+metadata:
+  category: CloudSecurity
 ---
 
 # Overview

package/dist/global-skills/harden/SKILL.md

@@ -77,7 +77,8 @@ translate every error · celebrate. You do all the work; the builder just approv
 8. **Database safety.** Confirm all data access uses `@vybekiit/db` (no raw SQL). Grep for `$executeRaw`
    or string-built queries and replace them. Run `vybekiit apply-preset audit_log` and confirm RLS on
    buyer tables (`platform-skills/db-presets-vybekiit.md`).
-   **Verify:** `vybekiit verify-presets audit_log`; no raw SQL in the app; zod on every API body.
+   **Verify:** `vybekiit verify-presets audit_log`; no raw SQL in the app; Effect Schema decodes every
+   API request; RLS policies match who should see each row.
 
 9. **Optional edge KV (agent-only).** `@vybekiit/kv` may back feature flags when you extend hardening —
    never Redis or Upstash for buyers. Client-side cache is `@vybekiit/client-state` (TanStack Query).

package/dist/global-skills/instrument-feature-flags/SKILL.md

@@ -77,6 +77,7 @@ STEP 6: Set up environment variables.
 - `references/next-js.md` - Next.js - docs
 - `references/adding-feature-flag-code.md` - Adding feature flag code - docs
 - `references/best-practices.md` - Best practices for production-ready flags - docs
+- `references/COMMANDMENTS.md` - Framework-specific rules the integration must follow
 
 Each platform reference contains SDK-specific installation, flag evaluation, and code examples. Find the one matching the user's stack. If unlisted, use the API reference as a fallback.
 

package/dist/global-skills/instrument-feature-flags/references/COMMANDMENTS.md

@@ -0,0 +1,5 @@
+# Framework rules
+
+Follow these when integrating PostHog into this framework.
+
+- A missing PostHog configuration must never break the app — read keys optionally (never a required setting), guard init and capture behind their presence, and keep build and boot working with no PostHog environment set — but never silently: in development or debug builds fail loudly, using the language's idiomatic error, with the message "<VAR> variable required by PostHog is missing or un-configured, this causes events to be silently missed. This error stops appearing once <VAR> is configured" (substituting the actual variable name); production stays a no-op

package/dist/global-skills/instrument-feature-flags/references/adding-feature-flag-code.md

@@ -1,3 +1,9 @@
+> AI agents: this is one page from PostHog's docs. Full index of Markdown docs for LLMs: https://posthog.com/llms.txt
+
+# Adding feature flag code - Docs
+
+Copy page
+
 # Adding feature flag code - Docs
 
 Once you've created your feature flag in PostHog, the next step is to add your code:
@@ -3569,10 +3575,6 @@ The list of properties that this overrides:
 6.  `$geoip_postal_code`
 7.  `$geoip_time_zone`
 
-### Community questions
-
-Ask a question
-
 ### Was this page useful?
 
 HelpfulCould be better

package/dist/global-skills/instrument-feature-flags/references/android.md

@@ -1,3 +1,9 @@
+> AI agents: this is one page from PostHog's docs. Full index of Markdown docs for LLMs: https://posthog.com/llms.txt
+
+# Android Feature Flags installation - Docs
+
+Copy page
+
 # Android Feature Flags installation - Docs
 
 1.  1
@@ -137,10 +143,6 @@
     | [How to do a phased rollout](/tutorials/phased-rollout.md) | Gradually roll out features to minimize risk |
     | [More tutorials](/docs/feature-flags/tutorials.md) | Other real-world examples and use cases |
 
-### Community questions
-
-Ask a question
-
 ### Was this page useful?
 
 HelpfulCould be better

package/dist/global-skills/instrument-feature-flags/references/api.md

@@ -1,3 +1,9 @@
+> AI agents: this is one page from PostHog's docs. Full index of Markdown docs for LLMs: https://posthog.com/llms.txt
+
+# API Feature Flags installation - Docs
+
+Copy page
+
 # API Feature Flags installation - Docs
 
 1.  1
@@ -185,10 +191,6 @@
     | [How to do a phased rollout](/tutorials/phased-rollout.md) | Gradually roll out features to minimize risk |
     | [More tutorials](/docs/feature-flags/tutorials.md) | Other real-world examples and use cases |
 
-### Community questions
-
-Ask a question
-
 ### Was this page useful?
 
 HelpfulCould be better

package/dist/global-skills/instrument-feature-flags/references/best-practices.md

@@ -1,3 +1,9 @@
+> AI agents: this is one page from PostHog's docs. Full index of Markdown docs for LLMs: https://posthog.com/llms.txt
+
+# Best practices for production-ready flags - Docs
+
+Copy page
+
 # Best practices for production-ready flags - Docs
 
 ## Checklist
@@ -222,10 +228,6 @@ Stale flags are the most common source of unnecessary cost. Beyond cleaning up f
 -   [Local evaluation](/docs/feature-flags/local-evaluation.md) – server-side evaluation for explicit input control
 -   [Bootstrapping](/docs/feature-flags/bootstrapping.md) – having flag values before the page renders
 
-### Community questions
-
-Ask a question
-
 ### Was this page useful?
 
 HelpfulCould be better

package/dist/global-skills/instrument-feature-flags/references/django.md

@@ -1,3 +1,9 @@
+> AI agents: this is one page from PostHog's docs. Full index of Markdown docs for LLMs: https://posthog.com/llms.txt
+
+# Django - Docs
+
+Copy page
+
 # Django - Docs
 
 PostHog makes it easy to get data about traffic and usage of your Django app. Integrating PostHog enables analytics, custom events capture, feature flags, error tracking, and more.
@@ -14,12 +20,12 @@ Install PostHog for Django in seconds with our wizard by running this prompt wit
 
 Or, to integrate manually, continue with the rest of this guide.
 
+> These docs cover version `7.x` of the Python SDK, which requires Python 3.10 or higher. On Python 3.9? See [supported versions](#supported-versions).
+
 ## Installation
 
 To start, run `pip install posthog` to install PostHog’s Python SDK.
 
-> **Note:** Version `7.x` of the PostHog Python SDK requires Python 3.10 or higher.
-
 Then, configure PostHog in your app config so it's initialized when Django starts:
 
 your\_app/apps.py
@@ -90,6 +96,8 @@ Events captured without a context or explicit `distinct_id` are sent as [anonymo
 >         capture("foo_viewed")
 >     return {"status": "ok"}
 > ```
+>
+> When possible, write a small piece of **middleware** that resolves your authenticated user, wrap a context around the request, and identifies it. Every `capture()` downstream is then attributed *automatically*. The SDK's Django middleware does this automatically and you can replicate it when using the plain Python SDK.
 
 ## Django contexts middleware
 
@@ -128,7 +136,28 @@ The session and distinct ID headers are sanitized before use. Empty values are i
 
 All events captured during the request (including exceptions) include these properties and are associated with the extracted session and distinct ID.
 
-If you're using [PostHog JS](/docs/libraries/js.md) on the frontend, configure [`tracing_headers`](/docs/libraries/js/config.md#tracing-headers) for your Django backend hostname so browser requests include the session and distinct ID headers.
+### Login and signup views
+
+The middleware reads `request.user` once, before your view runs. On a login or signup request the visitor is still anonymous at that point, so the request's context has no distinct ID. Calling `login()` inside the view doesn't change that. Everything captured during that request stays anonymous, including the login event itself.
+
+Identify the context from inside the request once you know who the user is. Django's auth signals are the natural place:
+
+Python
+
+PostHog AI
+
+```python
+from django.contrib.auth.signals import user_logged_in
+from django.dispatch import receiver
+from posthog import identify_context
+@receiver(user_logged_in)
+def identify_posthog_user(sender, request, user, **kwargs):
+    identify_context(str(user.pk))
+```
+
+Every capture later in that request is then attributed to the user who just logged in. Requests made after login don't need this. The middleware sees the authenticated user from the start.
+
+If you're using [PostHog JavaScript Web](/docs/libraries/js.md) on the frontend, configure [`tracing_headers`](/docs/libraries/js/config.md#tracing-headers) for your Django backend hostname so browser requests include the session and distinct ID headers.
 
 ### Exception capture
 
@@ -254,9 +283,13 @@ Alternatively, the following tutorials can help you get started:
 -   [Setting up Django analytics, feature flags, and more](/tutorials/django-analytics.md)
 -   [How to set up A/B tests in Django](/tutorials/django-ab-tests.md)
 
-### Community questions
+## Supported versions
+
+These docs cover version `7.x` of the PostHog Python SDK, which requires Python 3.10 or higher. Python 3.9 is no longer supported on `7.x.x` and higher — pin to the 6.x line with `pip install 'posthog<7'`, where `6.9.3` is the final release.
+
+Everything on this page works the same way on `6.9.3`. Event capture, the context API (`new_context`, `identify_context`, `set_context_session`), and `PosthogContextMiddleware` are identical on `6.9.3` and `7.0.0` — `7.0.0` only dropped Python 3.9 and bumped the optional LLM provider SDKs. That includes the middleware identifying the request context from the `X-POSTHOG-DISTINCT-ID` header and falling back to the authenticated user, which behaves the same across both lines.
 
-Ask a question
+Later `7.x` releases add what the 6.x line does not receive, such as the Celery integration, tracing header sanitization, and `set_context_device_id`. They also changed the middleware's own captured properties: `7.x` sends the request IP as `$ip`, where `6.9.3` sends it as `$ip_address`, and `7.x` additionally captures `$request_path`, `$raw_user_agent`, and the authenticated user's `email`.
 
 ### Was this page useful?
 

package/dist/global-skills/instrument-feature-flags/references/dotnet.md

@@ -1,3 +1,9 @@
+> AI agents: this is one page from PostHog's docs. Full index of Markdown docs for LLMs: https://posthog.com/llms.txt
+
+# .NET - Docs
+
+Copy page
+
 # .NET - Docs
 
 This is an optional library you can install if you're working with .NET Core. It uses an internal queue to make calls fast and non-blocking. It also batches requests and flushes asynchronously, making it perfect to use in any part of your web app or other server side application that needs performance.
@@ -366,6 +372,10 @@ For the full setup guide, see the [.NET error tracking installation docs](/docs/
 
 Automatic exception capture is not available in the .NET SDK yet.
 
+## Logs
+
+[PostHog Logs](/docs/logs.md) doesn't use this SDK. Logs are ingested over OpenTelemetry, so you attach an OTLP exporter to the standard `ILogger` pipeline instead — see the [.NET logs installation guide](/docs/logs/installation/dotnet.md).
+
 ## Person profiles and properties
 
 The .NET 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:
@@ -754,10 +764,6 @@ By default, the library buffers events before sending them to the `/batch` endpo
 
 To avoid this, call `await posthog.FlushAsync()` after processing every request by adding it as a middleware to your server. This allows `posthog.Capture()` to remain asynchronous for better performance.
 
-### Community questions
-
-Ask a question
-
 ### Was this page useful?
 
 HelpfulCould be better

package/dist/global-skills/instrument-feature-flags/references/elixir.md

@@ -1,3 +1,9 @@
+> AI agents: this is one page from PostHog's docs. Full index of Markdown docs for LLMs: https://posthog.com/llms.txt
+
+# Elixir Feature Flags installation - Docs
+
+Copy page
+
 # Elixir Feature Flags installation - Docs
 
 > This library was built by the community but it's being maintained by the PostHog core team since v1.0.0. Thank you to [Nick Kezhaya](https://github.com/nkezhaya) for building it originally. Thank you to [Alex Martsinovich](https://github.com/martosaur) for contributing v2.0.0.
@@ -38,10 +44,6 @@ Optionally, you might want to enable the [Plug integration](https://hexdocs.pm/p
 
 For a test environment, you can pass in `test_mode: true` value to the config. This causes events to be dropped instead of sent to PostHog.
 
-### Community questions
-
-Ask a question
-
 ### Was this page useful?
 
 HelpfulCould be better

package/dist/global-skills/instrument-feature-flags/references/flask.md

@@ -1,15 +1,21 @@
+> AI agents: this is one page from PostHog's docs. Full index of Markdown docs for LLMs: https://posthog.com/llms.txt
+
+# Flask - Docs
+
+Copy page
+
 # Flask - Docs
 
 PostHog makes it easy to get data about traffic and usage of your Flask app. Integrating PostHog enables analytics, custom events capture, feature flags, error tracking, and more.
 
 This guide walks you through integrating PostHog into your Flask app using the [Python SDK](/docs/libraries/python.md).
 
+> These docs cover version `7.x` of the Python SDK, which requires Python 3.10 or higher. On Python 3.9? See [supported versions](#supported-versions).
+
 ## Installation
 
 To start, run `pip install posthog` to install PostHog’s Python SDK.
 
-> **Note:** Version `7.x` of the PostHog Python SDK requires Python 3.10 or higher.
-
 Then, initialize PostHog where you'd like to use it. For example, here's how to capture an event in a simple route:
 
 app.py
@@ -54,12 +60,14 @@ You can find your project token and instance address in [your project settings](
 >         capture("foo_viewed")
 >     return {"status": "ok"}
 > ```
+>
+> When possible, write a small piece of **middleware** that resolves your authenticated user, wrap a context around the request, and identifies it. Every `capture()` downstream is then attributed *automatically*. The SDK's Django middleware does this automatically and you can replicate it when using the plain Python SDK.
 
 ## Request contexts
 
 Use [contexts](/docs/libraries/python.md#contexts) to share identity, session IDs, and tags across multiple captures during a request.
 
-If you're using [PostHog JS](/docs/libraries/js.md) on the frontend, configure [`tracing_headers`](/docs/libraries/js/config.md#tracing-headers) for your Flask backend hostname so browser requests include the session and distinct ID headers.
+If you're using [PostHog JavaScript Web](/docs/libraries/js.md) on the frontend, configure [`tracing_headers`](/docs/libraries/js/config.md#tracing-headers) for your Flask backend hostname so browser requests include the session and distinct ID headers.
 
 Then read the incoming headers in your Flask request handler. Tracing headers are client-controlled analytics context, not authentication or authorization, so prefer your authenticated user ID when one is available:
 
@@ -122,9 +130,13 @@ Alternatively, the following tutorials can help you get started:
 -   [How to set up feature flags in Python and Flask](/tutorials/python-feature-flags.md)
 -   [How to set up A/B tests in Python and Flask](/tutorials/python-ab-testing.md)
 
-### Community questions
+## Supported versions
+
+These docs cover version `7.x` of the PostHog Python SDK, which requires Python 3.10 or higher. Python 3.9 is no longer supported on `7.x.x` and higher — pin to the 6.x line with `pip install 'posthog<7'`, where `6.9.3` is the final release.
+
+Everything on this page works the same way on `6.9.3`. Event capture, the context API (`new_context`, `identify_context`, `set_context_session`), and `PosthogContextMiddleware` are identical on `6.9.3` and `7.0.0` — `7.0.0` only dropped Python 3.9 and bumped the optional LLM provider SDKs. That includes the middleware identifying the request context from the `X-POSTHOG-DISTINCT-ID` header and falling back to the authenticated user, which behaves the same across both lines.
 
-Ask a question
+Later `7.x` releases add what the 6.x line does not receive, such as the Celery integration, tracing header sanitization, and `set_context_device_id`. They also changed the middleware's own captured properties: `7.x` sends the request IP as `$ip`, where `6.9.3` sends it as `$ip_address`, and `7.x` additionally captures `$request_path`, `$raw_user_agent`, and the authenticated user's `email`.
 
 ### Was this page useful?
 

package/dist/global-skills/instrument-feature-flags/references/flutter.md

@@ -1,3 +1,9 @@
+> AI agents: this is one page from PostHog's docs. Full index of Markdown docs for LLMs: https://posthog.com/llms.txt
+
+# Flutter Feature Flags installation - Docs
+
+Copy page
+
 # Flutter Feature Flags installation - Docs
 
 1.  1
@@ -102,7 +108,7 @@
       <head>
         ...
         <script>
-          !function(t,e){var o,n,p,r;e.__SV||(window.posthog=e,e._i=[],e.init=function(i,s,a){function g(t,e){var o=e.split(".");2==o.length&&(t=t[o[0]],e=o[1]),t[e]=function(){t.push([e].concat(Array.prototype.slice.call(arguments,0)))}}(p=t.createElement("script")).type="text/javascript",p.async=!0,p.src=s.api_host.replace(".i.posthog.com","-assets.i.posthog.com")+"/static/array.js",(r=t.getElementsByTagName("script")[0]).parentNode.insertBefore(p,r);var u=e;for(void 0!==a?u=e[a]=[]:a="posthog",u.people=u.people||[],u.toString=function(t){var e="posthog";return"posthog"!==a&&(e+="."+a),t||(e+=" (stub)"),e},u.people.toString=function(){return u.toString(1)+".people (stub)"},o="init capture register register_once register_for_session unregister opt_out_capturing has_opted_out_capturing opt_in_capturing reset isFeatureEnabled getFeatureFlag getFeatureFlagPayload reloadFeatureFlags group identify setPersonProperties setPersonPropertiesForFlags resetPersonPropertiesForFlags setGroupPropertiesForFlags resetGroupPropertiesForFlags resetGroups onFeatureFlags addFeatureFlagsHandler onSessionId getSurveys getActiveMatchingSurveys renderSurvey canRenderSurvey getNextSurveyStep".split(" "),n=0;n<o.length;n++)g(u,o[n]);e._i.push([i,s,a])},e.__SV=1)}(document,window.posthog||[]);
+          !function(t,e){var o,n,p,r;e.__SV||(window.posthog && window.posthog.__loaded)||(window.posthog=e,e._i=[],e.init=function(i,s,a){function g(t,e){var o=e.split(".");2==o.length&&(t=t[o[0]],e=o[1]),t[e]=function(){t.push([e].concat(Array.prototype.slice.call(arguments,0)))}}p||((p=t.createElement("script")).type="text/javascript",p.crossOrigin="anonymous",p.async=!0,p.src=s.api_host.replace(".i.posthog.com","-assets.i.posthog.com")+"/static/array.js",p.onerror=function(){p=null},(r=t.getElementsByTagName("script")[0]).parentNode.insertBefore(p,r));var u=e;for(void 0!==a?u=e[a]=[]:a="posthog",u.people=u.people||[],u.toString=function(t){var e="posthog";return"posthog"!==a&&(e+="."+a),t||(e+=" (stub)"),e},u.people.toString=function(){return u.toString(1)+".people (stub)"},o="init capture register register_once register_for_session unregister opt_out_capturing has_opted_out_capturing opt_in_capturing reset isFeatureEnabled getFeatureFlag getFeatureFlagPayload reloadFeatureFlags group identify setPersonProperties setPersonPropertiesForFlags resetPersonPropertiesForFlags setGroupPropertiesForFlags resetGroupPropertiesForFlags resetGroups onFeatureFlags addFeatureFlagsHandler onSessionId getSurveys getActiveMatchingSurveys renderSurvey canRenderSurvey getNextSurveyStep".split(" "),n=0;n<o.length;n++)g(u,o[n]);e._i.push([i,s,a])},e.__SV=1)}(document,window.posthog||[]);
           posthog.init('<ph_project_token>', {
               api_host: 'https://us.i.posthog.com',
               defaults: '2026-05-30',
@@ -203,10 +209,6 @@
     | [How to do a phased rollout](/tutorials/phased-rollout.md) | Gradually roll out features to minimize risk |
     | [More tutorials](/docs/feature-flags/tutorials.md) | Other real-world examples and use cases |
 
-### Community questions
-
-Ask a question
-
 ### Was this page useful?
 
 HelpfulCould be better

package/dist/global-skills/instrument-feature-flags/references/go.md

@@ -1,3 +1,9 @@
+> AI agents: this is one page from PostHog's docs. Full index of Markdown docs for LLMs: https://posthog.com/llms.txt
+
+# Go Feature Flags installation - Docs
+
+Copy page
+
 # Go Feature Flags installation - Docs
 
 1.  1
@@ -199,10 +205,6 @@
     | [How to do a phased rollout](/tutorials/phased-rollout.md) | Gradually roll out features to minimize risk |
     | [More tutorials](/docs/feature-flags/tutorials.md) | Other real-world examples and use cases |
 
-### Community questions
-
-Ask a question
-
 ### Was this page useful?
 
 HelpfulCould be better

package/dist/global-skills/instrument-feature-flags/references/ios.md

@@ -1,3 +1,9 @@
+> AI agents: this is one page from PostHog's docs. Full index of Markdown docs for LLMs: https://posthog.com/llms.txt
+
+# iOS Feature Flags installation - Docs
+
+Copy page
+
 # iOS Feature Flags installation - Docs
 
 1.  1
@@ -137,10 +143,6 @@
     | [How to do a phased rollout](/tutorials/phased-rollout.md) | Gradually roll out features to minimize risk |
     | [More tutorials](/docs/feature-flags/tutorials.md) | Other real-world examples and use cases |
 
-### Community questions
-
-Ask a question
-
 ### Was this page useful?
 
 HelpfulCould be better

package/dist/global-skills/instrument-feature-flags/references/java.md

@@ -1,3 +1,9 @@
+> AI agents: this is one page from PostHog's docs. Full index of Markdown docs for LLMs: https://posthog.com/llms.txt
+
+# Java Feature Flags installation - Docs
+
+Copy page
+
 # Java Feature Flags installation - Docs
 
 The best way to install the PostHog Java SDK is with a build system like Gradle or Maven. This ensures you can easily upgrade to the latest versions.
@@ -85,10 +91,6 @@ PostHogConfig config = PostHogConfig
           .build();
 ```
 
-### Community questions
-
-Ask a question
-
 ### Was this page useful?
 
 HelpfulCould be better

package/dist/global-skills/instrument-feature-flags/references/laravel.md

@@ -1,3 +1,9 @@
+> AI agents: this is one page from PostHog's docs. Full index of Markdown docs for LLMs: https://posthog.com/llms.txt
+
+# Laravel - Docs
+
+Copy page
+
 # Laravel - Docs
 
 PostHog integrates with Laravel through the [PostHog PHP SDK](/docs/libraries/php.md). This page covers Laravel-specific setup. For SDK features such as event capture, identifying users, feature flags, group analytics, and configuration options, see the [PHP SDK docs](/docs/libraries/php.md).
@@ -161,10 +167,6 @@ PostHog::init(
 
 See the [PHP SDK docs](/docs/libraries/php.md) for usage examples and the full API reference.
 
-### Community questions
-
-Ask a question
-
 ### Was this page useful?
 
 HelpfulCould be better