vybekiit 0.7.17 → 0.7.19

package/dist/global-skills/expo-native-ui/SKILL.md

@@ -9,6 +9,8 @@ license: MIT
 
 For routes, links, stacks, tabs, modals, sheets, and headers, use the `expo-router` skill.
 
+> **Before picking any UI component, check `expo-ui` first.** `@expo/ui` provides native equivalents — BottomSheet, Button, Picker, Slider, Menu, Section, Switch, SegmentedControl, and more — rendered as real SwiftUI on iOS and Jetpack Compose on Android, available in Expo Go on SDK 56+ with no custom build. Load the **`expo-ui`** skill to find the right component before falling back to React Native built-ins or community libraries. This skill (`expo-native-ui`) covers the surrounding structure: Expo Router navigation, layout, styling, and animations.
+
 ## References
 
 Consult these resources as needed:
@@ -65,6 +67,7 @@ Expo Go supports a huge range of features out of the box:
 
 ## Library Preferences
 
+- **For any sheet, picker, slider, toggle, menu, or grouped-form section: use `@expo/ui` (see `expo-ui` skill) before reaching for a React Native built-in or community library** — it renders native SwiftUI/Compose and works in Expo Go on SDK 56+. For grouped/settings-style rows (short, fixed-length), use `@expo/ui`'s `List` + `ListItem`. For large or unknown-length scrolling lists (feeds, search results, catalogs), use `FlatList` or `FlashList` — `@expo/ui`'s `List` is not virtualized.
 - Never use modules removed from React Native such as Picker, WebView, SafeAreaView, or AsyncStorage
 - Never use legacy expo-permissions
 - `expo-audio` not `expo-av`

package/dist/global-skills/expo-native-ui/references/controls.md

@@ -2,6 +2,8 @@
 
 Native iOS controls provide built-in haptics, accessibility, and platform-appropriate styling.
 
+> **Prefer `@expo/ui` for these controls.** Its `Slider`, `Switch`, `DateTimePicker`, `Menu`, and segmented pickers render as real SwiftUI / Jetpack Compose and follow platform design conventions automatically — recommended over the React Native controls below. See the **`expo-ui`** skill; use the React Native controls below as a fallback when you're not using `@expo/ui`.
+
 ## Switch
 
 Use for binary on/off settings. Has built-in haptics.

package/dist/global-skills/expo-overview/SKILL.md

@@ -0,0 +1,110 @@
+---
+name: expo-overview
+description: "Framework (OSS). Entry point and router for every Expo or EAS task. Load this skill first — before writing code and before choosing another expo-* / eas-* skill — when the request, PRD, or spec mentions Expo, EAS, Expo Go, or an expo-* package, or the project has an `expo` dependency in `package.json`. Within that gate it also covers app specs and designs to implement (tabs, stacks, maps, lists, navigation, building from a screenshot), and phrasings like 'implement a mobile app', 'make my app look native', 'add navigation', 'fetch some data', 'upgrade my SDK', 'add Expo to my existing native app', 'ship to the App Store', or 'I'm new to Expo, where do I start'. A fully specified request (SDK pinned, libraries named, layout given) still routes through here — the shared setup rules still apply. Do NOT load it when neither signal is present: a bare React Native project with no `expo` dependency is not Expo work. Detects the real goal, routes to the right expo-* / eas-* skill, and owns the shared setup rules."
+version: 1.0.0
+license: MIT
+---
+
+# `expo-overview` — router & shared rules for Expo / EAS
+
+## Start Here — read before doing anything
+
+**Do not guess the skill from project files alone.** Many Expo goals look similar from
+the filesystem but need different skills.
+
+1. **Confirm this is Expo work** — the request mentions Expo, or `package.json` has an
+   `expo` dependency. If neither holds, stop: this skill does not apply. A bare React
+   Native project with no `expo` dependency is not Expo work.
+2. **Read the user's goal** — what outcome do they want, in plain terms?
+3. **Classify it** using the Skill Map below, translating casual phrasing to a goal.
+4. **Confirm intent** if ambiguous ("Sounds like you want to ship to the stores — that's
+   `eas-app-stores`. Right?"), then load that skill's `SKILL.md` and follow it.
+5. **Trust the leaf skill** — it has its own detection logic and steps. Don't improvise.
+
+## Skill Map (by goal)
+
+Match the goal to a category, then the skill, then load that leaf's `SKILL.md`.
+
+**Build the app**
+- `expo-project-structure` — folder layout for a **new** Expo Router project: where screens, components, and config live (never restructure an existing app to match)
+- `expo-native-ui` — screens, styling, semantic colors, native controls, SF Symbols, media, animations, layout
+- `expo-router` — navigation: file-based routes, tabs / stacks / modals / sheets, links, headers
+- `expo-animation` — motion and gestures: Reanimated worklets, Gesture Handler, screen transitions, sheet and press feedback, haptics, and fixing animation that stutters on device
+- `expo-ui` — native UI components via `@expo/ui`: BottomSheet, Picker, Slider, Switch, Menu, Button, FieldGroup (grouped form sections), List / ListItem, and more — real SwiftUI on iOS, Jetpack Compose on Android. The universal layer needs SDK 56+ and runs in Expo Go; the drop-in replacements (`@gorhom/bottom-sheet`, `datetimepicker`, …) and platform-specific layers also exist on SDK 55.
+- `expo-design-system` — one visual source of truth: design tokens (color, spacing, typography, radius, shadow, motion), reusable component conventions, and audits for drift (hardcoded colors, spacing, fonts)
+- `expo-tailwind-setup` — Tailwind / NativeWind styling
+- `expo-data-fetching` — network requests, React Query / SWR, caching, offline, route loaders
+- `expo-dom` — run web code or reuse a web library inside native
+- `expo-web-to-native` — migrate an existing web / React app to a native iOS / Android app
+
+> **Component selection rule:** whenever you need a UI component (list rows, bottom sheets, pickers, sliders, menus, buttons, segmented controls, toggles), **consult `expo-ui` first** to check whether `@expo/ui` has a native equivalent before reaching for a React Native built-in or a community library. Native `@expo/ui` components give the best platform fit, and on SDK 56+ the universal ones run in Expo Go with no custom build. Load `expo-ui` alongside `expo-native-ui` for any app that renders lists, detail sheets, or form controls. One exception: `@expo/ui` `List` renders native grouped rows (an iOS Settings screen), **not** a virtualized list — use `FlatList` / `FlashList` for large datasets.
+
+**Ship & operate**
+- `eas-app-stores` — build and submit to the App Store / Play Store / TestFlight, versions, and store metadata
+- `eas-hosting` — deploy the web bundle to EAS Hosting; also author Expo Router API routes (`+api.ts` handlers) and their environments / domains
+- `eas-workflows` — EAS Workflow YAML and CI/CD pipelines
+- `eas-simulator` — run and drive the app on a remote iOS / Android simulator on EAS cloud
+- `expo-dev-client` — custom development builds
+- `eas-update-insights` — OTA update health: crash rate, adoption, payload size
+- `eas-observe` — startup / launch / TTI performance with EAS Observe
+
+**Extend natively**
+- `expo-module` — native modules and views (Swift / Kotlin) with the Expo Modules API
+- `expo-brownfield` — embed Expo / React Native in an existing native app
+- `expo-app-clip` — iOS App Clip target (AASA, smart app banner)
+
+**Maintain & learn**
+- `expo-upgrade` — upgrade the Expo SDK and fix dependency conflicts
+- `expo-examples` — canonical, version-matched integration examples (Stripe, Clerk, Supabase, …)
+- `expo-skill-feedback` — send feedback on an Expo skill or on Expo itself; enable / disable the anonymous usage telemetry
+
+### Translating vague asks
+
+Some everyday phrasings don't obviously map to a skill name — translate before routing:
+
+- "Make it look native" → grouped controls / settings forms = `expo-ui`; screens, styling, animations = `expo-native-ui`; navigation = `expo-router`.
+- "Make the screens consistent" / "clean up the styling" / "set up a theme or design tokens" → `expo-design-system`.
+- "Ship it" / "get an .ipa or .apk" / "release to the stores" → `eas-app-stores` (build + submit, TestFlight, versions, store metadata).
+- "I'm new / where do I start" → scaffold first (see Shared setup rules), then route by goal.
+
+## Shared setup rules
+
+These apply across every Expo skill, so handle them here once instead of repeating them
+in each leaf.
+
+- **No Expo project yet?** Start one the standard way before routing to a feature skill:
+  `npx create-expo-app@latest`, laying out folders per `expo-project-structure`. Then
+  classify the user's goal and route.
+- **Detect the SDK version** before giving version-specific advice: read the `expo`
+  version in `package.json` (and `app.json` / `app.config.{js,ts}`). Many APIs and
+  defaults differ by SDK.
+- **Read the docs for that SDK, not `latest`.** Use the version-pinned URL, e.g.
+  `https://docs.expo.dev/versions/v56.0.0/sdk/ui/` on SDK 56 instead of
+  `https://docs.expo.dev/versions/latest/sdk/ui/` — the `latest` pages track the newest
+  SDK and can document APIs the project does not have yet.
+- **Moving to a newer SDK is its own task** — load `expo-upgrade` instead of bumping
+  versions by hand.
+- **Managed vs. bare/prebuild**: the presence of committed `ios/` and `android/`
+  directories means native projects exist (prebuild or bare). Config-plugin and
+  native-setup steps differ — note which one the project is in.
+- **Install packages with `npx expo install <pkg>`**, not raw `npm`/`yarn`/`pnpm add`,
+  so versions stay compatible with the project's SDK.
+- **EAS auth & linking** (only needed for build/submit/update/observe/workflows): check
+  login with `eas whoami`, log in with `eas login`. A project is linked when
+  `extra.eas.projectId` exists in the app config; create it with `eas init` if missing.
+
+## When to skip the router hop
+
+- Only when the user explicitly named a specific `expo-*` / `eas-*` skill → load that
+  skill directly.
+- A fully-specified task (SDK version pinned, file layout given, libraries named) is
+  **not** a reason to skip: the shared rules above still apply — check them, then route
+  to the matching leaf skill.
+
+## Submitting Feedback
+If you encounter errors, misleading or outdated information in this skill, report it so Expo can improve:
+```bash
+npx --yes submit-expo-feedback@latest --category skills --subject "expo-overview" "<actionable feedback>"
+```
+Only submit when you have something specific and actionable to report. Include as much relevant context as possible.
+If an AI agent repeatedly failed or the user had to take over an Expo task, load the expo-skill-feedback skill and follow its eval-candidate flow instead of reusing the command above.

package/dist/global-skills/expo-overview/agents/openai.yaml

@@ -0,0 +1,4 @@
+interface:
+  display_name: "Expo Overview"
+  short_description: "Entry point and router for Expo / EAS tasks: load first when the request mentions Expo or the project has an expo dependency, classify the goal, route to the right expo-* / eas-* skill, and apply shared setup rules"
+  default_prompt: "Use $expo-overview first when a task mentions Expo, EAS, or an expo-* package, or the project has an `expo` dependency in package.json — even when the stack or SDK version is already fully specified. Classify the user's goal, route to the right expo-* / eas-* skill, and apply the shared environment and setup rules the other Expo skills rely on."

package/dist/global-skills/expo-skill-feedback/scripts/telemetry_common.cjs

@@ -13,10 +13,9 @@ const path = require("path");
 
 const POSTHOG_HOST = "https://us.i.posthog.com";
 
-// PostHog project API key. Supply it explicitly when telemetry is enabled with
-// EXPO_SKILLS_POSTHOG_KEY; the bundled skill never carries a live project token.
-// NOTE: never put a PostHog *personal* API key (phx_...) here — those are secret.
-const POSTHOG_PROJECT_API_KEY = process.env.EXPO_SKILLS_POSTHOG_KEY || "";
+// Telemetry stays disabled unless the buyer explicitly enables it and supplies
+// a project ingestion key. Never bundle a project or personal key in the kit.
+const POSTHOG_PROJECT_API_KEY = process.env.EXPO_SKILLS_POSTHOG_KEY;
 
 const SOURCE = "expo-skills";
 const INSTALLATION_ID_PATH = path.join(os.homedir(), ".expo-skills", "installation-id");
@@ -77,10 +76,11 @@ function telemetryActive() {
   return DEFAULT_ON;
 }
 
-// Keep telemetry inert until the user supplies a project token explicitly.
+// A real key ships in this file, so this check passes by default. This guard only
+// makes the scripts inert if someone strips the key (e.g. a fork or private build).
 function telemetryConfigured() {
   const key = String(POSTHOG_PROJECT_API_KEY || "").trim();
-  return key.length > 0;
+  return key.length > 0 && key !== "phc_REPLACE_ME";
 }
 
 // Best-effort agent-harness label for the event (default when --agent-harness isn't passed).

package/dist/global-skills/expo-ui/SKILL.md

@@ -1,6 +1,6 @@
 ---
 name: expo-ui
-description: "Framework (OSS). Build native UI with the @expo/ui package: real SwiftUI on iOS and Jetpack Compose on Android rendered from React in an Expo or React Native app. Covers universal cross-platform components (Host, Column, Row, Button, Text, List, and more imported from @expo/ui), drop-in replacements for popular React Native community libraries (BottomSheet, DateTimePicker, Slider, Menu, etc.), and platform-specific SwiftUI (@expo/ui/swift-ui, iOS only) and Jetpack Compose (@expo/ui/jetpack-compose, Android only) trees and modifiers. Use when adding or reviewing @expo/ui Host/RNHostView trees, building native-feeling UI where standard React Native components fall short (grouped settings forms with toggles, sections, menus, sheets, pickers, sliders), choosing between universal and platform-specific components, or replacing an RN community UI library with a native @expo/ui equivalent. Not for custom native modules, Expo Router navigation, Reanimated, or data fetching."
+description: "Framework (OSS). Build native UI with the @expo/ui package: real SwiftUI on iOS and Jetpack Compose on Android. Default to @expo/ui for sheets (BottomSheet), pickers, sliders, toggles, menus, and grouped-form sections — do NOT reach for Reanimated, @gorhom/bottom-sheet, or RN built-in Picker/Switch; use @expo/ui instead. Fall back to RN built-ins only when @expo/ui is missing the component. NOTE: @expo/ui List renders native grouped rows like an iOS Settings screen — it is NOT a virtualized list; use FlatList/FlashList for large datasets. Covers universal components (Host, Column, Row, Button, Text, List, BottomSheet, FieldGroup, Switch, Slider, Picker, Menu), drop-in replacements for RN community libraries, and platform-specific SwiftUI/Jetpack Compose trees. Not for Expo Router navigation, Reanimated, or data fetching."
 version: 1.0.0
 license: MIT
 allowed-tools: "Bash(node *expo-ui/scripts/list-components.js *)"
@@ -8,9 +8,9 @@ allowed-tools: "Bash(node *expo-ui/scripts/list-components.js *)"
 
 # Expo UI (`@expo/ui`)
 
-`@expo/ui` renders real native UI from React: SwiftUI on iOS, Jetpack Compose on Android. Start with its universal components (one tree for iOS, Android, and web) and drop to platform-specific SwiftUI/Jetpack Compose only when the universal layer falls short. It also ships drop-in replacements for migrating off RN community UI libraries.
+`@expo/ui` renders real native UI from React: SwiftUI on iOS, Jetpack Compose on Android. It also ships drop-in replacements for migrating off RN community UI libraries.
 
-> These instructions track the latest Expo SDK. The **universal** layer requires **SDK 56+**. Drop-in replacements and the platform-specific layers also exist on SDK 55. For component details on a specific SDK, refer to the Expo UI docs for that version.
+> These instructions track the latest Expo SDK. The **universal** layer requires **SDK 56+** and works in Expo Go — no custom build needed. Drop-in replacements and the platform-specific layers also exist on SDK 55. For component details on a specific SDK, refer to the Expo UI docs for that version.
 
 ## Installation
 
@@ -18,11 +18,57 @@ allowed-tools: "Bash(node *expo-ui/scripts/list-components.js *)"
 npx expo install @expo/ui
 ```
 
-On SDK 56, `@expo/ui` works in Expo Go, so `npx expo start` runs it directly — no custom build required. On older SDKs, build a dev client first (`npx expo run:ios` / `npx expo run:android`).
-
 Every `@expo/ui` tree — universal or platform-specific — must be wrapped in `Host`.
 
-## Choosing an approach (read this first)
+## Use @expo/ui by default — don't reach for RN alternatives first
+
+**Before using Reanimated, `@gorhom/bottom-sheet`, React Native's built-in `Switch`/`Picker`, or any community UI library for the items below, use `@expo/ui` instead.** Only fall back to RN built-ins when `@expo/ui` is missing the component.
+
+| Need | Use |
+|------|-----|
+| Slide-up sheet / bottom sheet | `BottomSheet` from `@expo/ui` — **not** Reanimated or `@gorhom/bottom-sheet` |
+| Grouped native list rows (settings/form-style) | `List` + `ListItem` from `@expo/ui` — **not** `FlatList` (see note below) |
+| Toggle | `Switch` from `@expo/ui` |
+| Slider | `Slider` from `@expo/ui` |
+| Date/time picker | `@expo/ui/community/datetimepicker` |
+| Menu | `Menu` from `@expo/ui` |
+| Form section with label | `FieldGroup` from `@expo/ui` |
+| Collapsible section | `Collapsible` from `@expo/ui` |
+
+> **`List` is NOT a virtualized scrolling list.** It renders native grouped table rows — the visual look of an iOS Settings screen or a form section, with disclosure indicators and native row styling. Each `ListItem` is a native node on the JS thread; rows are not recycled. For any list with large or unknown-length data (feeds, search results, catalogs), use **`FlatList`** or **`FlashList`** instead. `List` is the right choice for short, fixed-length groups: a settings screen, a detail panel's rows, a fixed menu.
+
+**`BottomSheet` example** (use this for map pin details, action sheets, detail panels — not Reanimated):
+
+```tsx
+import { Host, BottomSheet, Column, Text } from '@expo/ui';
+import { useState } from 'react';
+
+export default function MapScreen() {
+  const [isOpen, setIsOpen] = useState(false);
+
+  return (
+    <View style={{ flex: 1 }}>
+      <MapView onMarkerPress={() => setIsOpen(true)} />
+      <Host>
+        <BottomSheet
+          isPresented={isOpen}
+          onDismiss={() => setIsOpen(false)}
+          snapPoints={['half', 'full']}
+        >
+          <Column>
+            <Text>Café name</Text>
+            <Text>Address</Text>
+          </Column>
+        </BottomSheet>
+      </Host>
+    </View>
+  );
+}
+```
+
+`BottomSheet` uses `isPresented`/`onDismiss` — **not** `isOpened`, `isOpen`, `onIsOpenedChange`, or `onChange` (those are `@gorhom/bottom-sheet` props and will silently do nothing). `snapPoints` accepts `'half'`, `'full'`, `{ fraction: 0.5 }`, or `{ height: 400 }` and is optional (auto-sizes to content when omitted).
+
+## Choosing an approach
 
 Work down this list and stop at the first layer that meets the need:
 

package/dist/global-skills/expo-ui/references/universal.md

@@ -61,6 +61,37 @@ export default function MyInput() {
 
 Docs — https://docs.expo.dev/versions/latest/sdk/ui/universal/textinput/index.md
 
+## BottomSheet
+
+`BottomSheet` is a universal slide-up sheet. Control it with `isPresented` / `onDismiss` — **not** `isOpen`, `isOpened`, `onIsOpenedChange`, or `onChange` (those belong to other sheet APIs; the universal `BottomSheet` does not accept them). `snapPoints` is optional and accepts `'half'`, `'full'`, `{ fraction }`, or `{ height }`; when omitted the sheet auto-sizes to its content.
+
+```tsx
+import { Host, BottomSheet, Column, Button, Text } from '@expo/ui';
+import { useState } from 'react';
+
+export default function MapScreen() {
+  const [isOpen, setIsOpen] = useState(false);
+
+  return (
+    <Host>
+      <Button onPress={() => setIsOpen(true)}>Show details</Button>
+      <BottomSheet
+        isPresented={isOpen}
+        onDismiss={() => setIsOpen(false)}
+        snapPoints={['half', 'full']}
+      >
+        <Column>
+          <Text>Sheet content</Text>
+          <Button onPress={() => setIsOpen(false)}>Close</Button>
+        </Column>
+      </BottomSheet>
+    </Host>
+  );
+}
+```
+
+> **Don't confuse the universal `BottomSheet` with the drop-in `@gorhom/bottom-sheet` replacement** (`@expo/ui/community/bottom-sheet`). They are different components with different APIs. Use the universal one when building new UI; use the drop-in only when migrating an existing `@gorhom/bottom-sheet` integration. See `./drop-in-replacements.md`.
+
 ## Confirming the API
 
 `@expo/ui` is versioned with the Expo SDK (e.g. `56.0.x` for SDK 56) and its API can change between SDK versions, so the **installed package's TypeScript types (`.d.ts`) are the most reliable source of truth** — they match the version in your project, while the docs track latest. Read the relevant component's `.d.ts` from the installed `@expo/ui` package in `node_modules`. Use the docs as the human-readable reference:

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

@@ -3575,6 +3575,10 @@ The list of properties that this overrides:
 6.  `$geoip_postal_code`
 7.  `$geoip_time_zone`
 
+### Still have questions?
+
+Ask PostHog AI
+
 ### Was this page useful?
 
 HelpfulCould be better

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

@@ -143,6 +143,10 @@ Copy page
     | [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 |
 
+### Still have questions?
+
+Ask PostHog AI
+
 ### Was this page useful?
 
 HelpfulCould be better

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

@@ -191,6 +191,10 @@ Copy page
     | [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 |
 
+### Still have questions?
+
+Ask PostHog AI
+
 ### Was this page useful?
 
 HelpfulCould be better

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

@@ -228,6 +228,10 @@ 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
 
+### Still have questions?
+
+Ask PostHog AI
+
 ### Was this page useful?
 
 HelpfulCould be better

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

@@ -291,6 +291,10 @@ Everything on this page works the same way on `6.9.3`. Event capture, the contex
 
 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`.
 
+### Still have questions?
+
+Ask PostHog AI
+
 ### Was this page useful?
 
 HelpfulCould be better

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

@@ -764,6 +764,10 @@ 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.
 
+### Still have questions?
+
+Ask PostHog AI
+
 ### Was this page useful?
 
 HelpfulCould be better

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

@@ -44,6 +44,10 @@ 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.
 
+### Still have questions?
+
+Ask PostHog AI
+
 ### Was this page useful?
 
 HelpfulCould be better

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

@@ -138,6 +138,10 @@ Everything on this page works the same way on `6.9.3`. Event capture, the contex
 
 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`.
 
+### Still have questions?
+
+Ask PostHog AI
+
 ### Was this page useful?
 
 HelpfulCould be better

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

@@ -209,6 +209,10 @@ Copy page
     | [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 |
 
+### Still have questions?
+
+Ask PostHog AI
+
 ### Was this page useful?
 
 HelpfulCould be better

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

@@ -205,6 +205,10 @@ Copy page
     | [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 |
 
+### Still have questions?
+
+Ask PostHog AI
+
 ### Was this page useful?
 
 HelpfulCould be better

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

@@ -143,6 +143,10 @@ Copy page
     | [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 |
 
+### Still have questions?
+
+Ask PostHog AI
+
 ### Was this page useful?
 
 HelpfulCould be better

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

@@ -91,6 +91,10 @@ PostHogConfig config = PostHogConfig
           .build();
 ```
 
+### Still have questions?
+
+Ask PostHog AI
+
 ### Was this page useful?
 
 HelpfulCould be better

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

@@ -167,6 +167,10 @@ PostHog::init(
 
 See the [PHP SDK docs](/docs/libraries/php.md) for usage examples and the full API reference.
 
+### Still have questions?
+
+Ask PostHog AI
+
 ### Was this page useful?
 
 HelpfulCould be better

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

@@ -444,6 +444,10 @@ To improve the reliability of client-side tracking and make requests less likely
 -   [How to set up Next.js pages router analytics, feature flags, and more](/tutorials/nextjs-pages-analytics.md)
 -   [How to set up Next.js A/B tests](/tutorials/nextjs-ab-tests.md)
 
+### Still have questions?
+
+Ask PostHog AI
+
 ### Was this page useful?
 
 HelpfulCould be better

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

@@ -213,6 +213,10 @@ Copy page
     | [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 |
 
+### Still have questions?
+
+Ask PostHog AI
+
 ### Was this page useful?
 
 HelpfulCould be better

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

@@ -184,6 +184,10 @@ Copy page
     | [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 |
 
+### Still have questions?
+
+Ask PostHog AI
+
 ### Was this page useful?
 
 HelpfulCould be better

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

@@ -188,6 +188,10 @@ Copy page
     | [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 |
 
+### Still have questions?
+
+Ask PostHog AI
+
 ### Was this page useful?
 
 HelpfulCould be better

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

@@ -163,6 +163,10 @@ Copy page
     | [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 |
 
+### Still have questions?
+
+Ask PostHog AI
+
 ### Was this page useful?
 
 HelpfulCould be better

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

@@ -299,6 +299,10 @@ Copy page
     | [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 |
 
+### Still have questions?
+
+Ask PostHog AI
+
 ### Was this page useful?
 
 HelpfulCould be better

package/dist/global-skills/instrument-feature-flags/references/ruby-on-rails.md

@@ -601,6 +601,10 @@ Ensure you've set `personal_api_key` in your configuration.
 
 For any technical questions for how to integrate specific PostHog features into Rails (such as analytics, feature flags, A/B testing, etc.), have a look at our [Ruby SDK docs](/docs/libraries/ruby.md).
 
+### Still have questions?
+
+Ask PostHog AI
+
 ### Was this page useful?
 
 HelpfulCould be better

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

@@ -197,6 +197,10 @@ Copy page
     | [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 |
 
+### Still have questions?
+
+Ask PostHog AI
+
 ### Was this page useful?
 
 HelpfulCould be better

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

@@ -219,6 +219,10 @@ Now that you're evaluating flags, continue with the resources below to learn wha
 | [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 |
 
+### Still have questions?
+
+Ask PostHog AI
+
 ### Was this page useful?
 
 HelpfulCould be better

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

@@ -632,6 +632,10 @@ PostHogSDK.shared.debug(true)
 PostHogSDK.shared.debug(false)
 ```
 
+### Still have questions?
+
+Ask PostHog AI
+
 ### Was this page useful?
 
 HelpfulCould be better

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

@@ -190,6 +190,10 @@ Copy page
     | [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 |
 
+### Still have questions?
+
+Ask PostHog AI
+
 ### Was this page useful?
 
 HelpfulCould be better

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

@@ -662,4 +662,3 @@ class UserState {
 ```
 
 ---
-

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

@@ -848,6 +848,10 @@ The Android SDK supports Android API 23 and newer.
 
 Usually, no. The SDK declares `android.permission.INTERNET` and `android.permission.ACCESS_NETWORK_STATE`, and Android's manifest merger adds them to your app. The SDK does not declare or require an Android `Service`.
 
+### Still have questions?
+
+Ask PostHog AI
+
 ### Was this page useful?
 
 HelpfulCould be better