vybekiit 0.7.33 → 0.7.35

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

@@ -2,11 +2,23 @@
 
 # Vue.js
 
+Canonical URL: https://posthog.com/docs/libraries/vue-js
+
+> **Cloud region:** This page uses US Cloud hosts. For an EU Cloud project, use `https://eu.i.posthog.com` instead of `https://us.i.posthog.com` (ingestion host), and use `https://eu.posthog.com` instead of `https://us.posthog.com` or `https://app.posthog.com` (app host for links).
+
+## On this page
+
+- [Prerequisites](#prerequisites)
+- [Setting up PostHog](#setting-up-posthog)
+- [Identifying users](#identifying-users)
+- [Capturing custom events, using feature flags, and more](#capturing-custom-events-using-feature-flags-and-more)
+- [Next steps](#next-steps)
+
 PostHog makes it easy to get data about usage of your [Vue.js](https://vuejs.org/) app. Integrating PostHog into your app enables analytics about user behavior, custom events capture, session replays, feature flags, and more.
 
-This guide walks you through integrating PostHog into your app for both Vue 2 and Vue 3. We'll use the [JavaScript Web SDK](/docs/libraries/js.md) for this.
+This guide walks you through integrating PostHog into your app for both Vue 2 and Vue 3. We'll use the [JavaScript Web SDK](https://posthog.com/docs/libraries/js.md) for this.
 
-For integrating PostHog into a [Nuxt.js](https://nuxt.com/) app, see our [Nuxt guide](/docs/libraries/nuxt-js.md).
+For integrating PostHog into a [Nuxt.js](https://nuxt.com/) app, see our [Nuxt guide](https://posthog.com/docs/libraries/nuxt-js.md).
 
 ## Prerequisites
 
@@ -51,7 +63,7 @@ bun add posthog-js
 > worker-src 'self' blob: data:;
 > ```
 >
-> `script-src` covers the snippet and the lazy-loaded bundles, `connect-src` covers event ingestion and feature flags, and `worker-src` covers session replay. The [toolbar needs a few more](/docs/advanced/content-security-policy.md), or use a [reverse proxy](/docs/advanced/proxy.md) so everything is first-party. Failing to do so causes silent failures where `capture` and `identify` calls never send, so the integration looks complete while zero events arrive. Remember `connect-src` falls back to `default-src`, so `default-src 'self'` blocks event delivery even when the script itself is bundled.
+> `script-src` covers the snippet and the lazy-loaded bundles, `connect-src` covers event ingestion and feature flags, and `worker-src` covers session replay. The [toolbar needs a few more](https://posthog.com/docs/advanced/content-security-policy.md), or use a [reverse proxy](https://posthog.com/docs/advanced/proxy.md) so everything is first-party. Failing to do so causes silent failures where `capture` and `identify` calls never send, so the integration looks complete while zero events arrive. Remember `connect-src` falls back to `default-src`, so `default-src 'self'` blocks event delivery even when the script itself is bundled.
 
 Next, depending on your Vue version, we recommend initializing PostHog using the composition API or as a plugin.
 
@@ -91,8 +103,6 @@ app.mount('#app')
 
 Then, you can access PostHog throughout your app just by importing it from `posthog-js`.
 
-TypeScript
-
 ```typescript
 // src/App.vue
 <script setup>
@@ -104,14 +114,12 @@ const handleClick = () => {
 </script>
 ```
 
-Once done, PostHog will begin [autocapturing](/docs/product-analytics/autocapture.md) events and pageviews (if enabled) and is ready to use throughout your app.
+Once done, PostHog will begin [autocapturing](https://posthog.com/docs/product-analytics/autocapture.md) events and pageviews (if enabled) and is ready to use throughout your app.
 
 ## Vue 2: Plugins
 
 Start by creating a `plugins` folder and adding a `posthog.js` file to that folder. In `posthog.js`, initialize PostHog using the `install` method with your project token and host. You can find these in your [project settings](https://us.posthog.com/project/settings).
 
-JavaScript
-
 ```javascript
 // src/plugins/posthog.js
 import posthog from 'posthog-js'
@@ -130,8 +138,6 @@ export default {
 
 Next, in `main.js`, import and use the plugin.
 
-JavaScript
-
 ```javascript
 // src/main.js
 import Vue from 'vue'
@@ -150,18 +156,16 @@ This makes PostHog available as `this.$posthog` in any Vue component.
 
 ## Identifying users
 
-> **Identifying users is required.** Call `posthog.identify('your-user-id')` after login to link events to a known user. This is what connects frontend event captures, [session replays](/docs/session-replay.md), [LLM traces](/docs/ai-engineering.md), and [error tracking](/docs/error-tracking.md) to the same person — and lets backend events link back too.
+> **Identifying users is required.** Call `posthog.identify('your-user-id')` after login to link events to a known user. This is what connects frontend event captures, [session replays](https://posthog.com/docs/session-replay.md), [LLM traces](https://posthog.com/docs/ai-engineering.md), and [error tracking](https://posthog.com/docs/error-tracking.md) to the same person — and lets backend events link back too.
 >
 > Use a stable ID from your auth system when possible, not an email or display name. Send those as person properties instead. If your app has no other stable key, email works as a fallback if they are unique. Never a shared literal like `"anonymous"` or `"user"`, which pools many people onto one person and corrupts their data. When no ID is available at all, skip the identify and retain the anonymous distinct ID that's automatically assigned.
 >
 > Call `posthog.reset()` on logout, so the next person to use the browser doesn't inherit the last one's identity.
 >
-> See our guide on [identifying users](/docs/getting-started/identify-users.md) for how to set this up.
+> See our guide on [identifying users](https://posthog.com/docs/getting-started/identify-users.md) for how to set this up.
 
 If your app calls your own backend, `tracing_headers` adds `X-POSTHOG-DISTINCT-ID` and `X-POSTHOG-SESSION-ID` to matching `fetch` and `XMLHttpRequest` requests. This lets server-side SDKs link backend events, errors, and LLM traces back to frontend sessions and replays. Use hostnames only, without protocols or paths.
 
-JavaScript
-
 ```javascript
 posthog.init('<ph_project_token>', {
   api_host: 'https://us.i.posthog.com',
@@ -176,14 +180,12 @@ Tracing headers help you attribute events across front and backend consistently.
 
 ## Capturing custom events, using feature flags, and more
 
-Once you have PostHog initialized, there is a lot more you can do with it beyond autocapture, pageviews, and pageleaves. You can find the full details in our [JavaScript SDK docs](/docs/libraries/js/usage.md), but we'll cover a few examples here.
+Once you have PostHog initialized, there is a lot more you can do with it beyond autocapture, pageviews, and pageleaves. You can find the full details in our [JavaScript SDK docs](https://posthog.com/docs/libraries/js/usage.md), but we'll cover a few examples here.
 
 ## Vue 3: Composition API
 
 To capture custom events, evaluate feature flags, and use any of the other PostHog features, you can use the `posthog` object returned from the `usePostHog` composable like this:
 
-JavaScript
-
 ```javascript
 // src/App.vue
 <script setup>
@@ -210,8 +212,6 @@ const handleClick = () => {
 
 When using feature flags on pages that users navigate to directly, the flags may not be loaded when the component first renders. To ensure your UI updates reactively when flags load, create a composable that returns a reactive ref:
 
-JavaScript
-
 ```javascript
 // src/composables/usePostHogFeatureFlag.ts
 import { ref, type Ref } from 'vue'
@@ -233,8 +233,6 @@ export function usePostHogFeatureFlag(
 
 Then use it in your components:
 
-JavaScript
-
 ```javascript
 // src/App.vue
 <script setup>
@@ -266,8 +264,6 @@ This ensures your component will automatically update when feature flags load, e
 
 To capture custom events, evaluate feature flags, and use any of the other PostHog features, you can use the `$posthog` object returned from the plugin like this:
 
-JavaScript
-
 ```javascript
 // src/components/AboutPage.vue
 <template>
@@ -299,23 +295,23 @@ export default {
 </script>
 ```
 
-Set up a reverse proxy (recommended)
+**Set up a reverse proxy (recommended)**
 
-We recommend [setting up a reverse proxy](/docs/advanced/proxy.md), so that events are less likely to be intercepted by tracking blockers.
+We recommend [setting up a reverse proxy](https://posthog.com/docs/advanced/proxy.md), so that events are less likely to be intercepted by tracking blockers.
 
-We have our [own managed reverse proxy service](/docs/advanced/proxy/managed-reverse-proxy.md), which is free for all PostHog Cloud users, routes through our infrastructure, and makes setting up your proxy easy.
+We have our [own managed reverse proxy service](https://posthog.com/docs/advanced/proxy/managed-reverse-proxy.md), which is free for all PostHog Cloud users, routes through our infrastructure, and makes setting up your proxy easy.
 
-If you don't want to use our managed service then there are several other options for creating a reverse proxy, including using [Cloudflare](/docs/advanced/proxy/cloudflare.md), [AWS Cloudfront](/docs/advanced/proxy/cloudfront.md), and [Vercel](/docs/advanced/proxy/vercel.md).
+If you don't want to use our managed service then there are several other options for creating a reverse proxy, including using [Cloudflare](https://posthog.com/docs/advanced/proxy/cloudflare.md), [AWS Cloudfront](https://posthog.com/docs/advanced/proxy/cloudfront.md), and [Vercel](https://posthog.com/docs/advanced/proxy/vercel.md).
 
-Grouping products in one project (recommended)
+**Grouping products in one project (recommended)**
 
-If you have multiple customer-facing products (e.g. a marketing website + mobile app + web app), it's best to install PostHog on them all and [group them in one project](/docs/settings/projects.md).
+If you have multiple customer-facing products (e.g. a marketing website + mobile app + web app), it's best to install PostHog on them all and [group them in one project](https://posthog.com/docs/settings/projects.md).
 
 This makes it possible to track users across their entire journey (e.g. from visiting your marketing website to signing up for your product), or how they use your product across multiple platforms.
 
-Add IPs to Firewall/WAF allowlists (recommended)
+**Add IPs to Firewall/WAF allowlists (recommended)**
 
-For certain features like [heatmaps](/docs/toolbar/heatmaps.md), your Web Application Firewall (WAF) may be blocking PostHog's requests to your site. Add these IP addresses to your WAF allowlist or rules to let PostHog access your site.
+For certain features like [heatmaps](https://posthog.com/docs/toolbar/heatmaps.md), your Web Application Firewall (WAF) may be blocking PostHog's requests to your site. Add these IP addresses to your WAF allowlist or rules to let PostHog access your site.
 
 **EU**: `3.75.65.221`, `18.197.246.42`, `3.120.223.253`
 
@@ -325,23 +321,15 @@ 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).
+An allowlist does not help when your app has a private address. For apps on an internal network, see [internal and intranet applications](https://posthog.com/docs/session-replay/troubleshooting.md#internal-and-intranet-applications).
 
 ## Next steps
 
-For any technical questions for how to integrate specific PostHog features into Vue (such as analytics, feature flags, A/B testing, or surveys), have a look at our [JavaScript Web](/docs/libraries/js/usage.md) SDK docs.
+For any technical questions for how to integrate specific PostHog features into Vue (such as analytics, feature flags, A/B testing, or surveys), have a look at our [JavaScript Web](https://posthog.com/docs/libraries/js/usage.md) SDK docs.
 
 Alternatively, the following tutorials can help you get started:
 
--   [How to set up analytics in Vue](/tutorials/vue-analytics.md)
--   [How to set up feature flags in Vue](/tutorials/vue-feature-flags.md)
--   [How to set up A/B tests in Vue](/tutorials/vue-ab-tests.md)
--   [How to set up surveys in Vue](/tutorials/vue-surveys.md)
-
-### Still have questions?
-
-Ask PostHog AI
-
-### Was this page useful?
-
-HelpfulCould be better
+-   [How to set up analytics in Vue](https://posthog.com/tutorials/vue-analytics.md)
+-   [How to set up feature flags in Vue](https://posthog.com/tutorials/vue-feature-flags.md)
+-   [How to set up A/B tests in Vue](https://posthog.com/tutorials/vue-ab-tests.md)
+-   [How to set up surveys in Vue](https://posthog.com/tutorials/vue-surveys.md)

package/dist/global-skills/manifest.json

@@ -111,6 +111,7 @@
     "neon-postgres",
     "neon-postgres-branches",
     "neon-postgres-egress-optimizer",
+    "neon-realtime",
     "onboarding",
     "plan-my-idea",
     "publish-app",
@@ -152,5 +153,5 @@
   "resources": [
     "vybekiitReferences"
   ],
-  "count": 148
+  "count": 149
 }

package/dist/global-skills/mongodb-search-and-ai/SKILL.md

@@ -1,7 +1,7 @@
 ---
 name: mongodb-search-and-ai
 description: |
-  Guides MongoDB users through implementing and optimizing Atlas Search (full-text), Vector Search (semantic), and Hybrid Search solutions. Use this skill when users need to build search functionality for text-based queries (autocomplete, fuzzy matching, faceted search), semantic similarity (embeddings, RAG applications), or combined approaches. Also use when users need text containment, substring matching ('contains', 'includes', 'appears in'), case-insensitive or multi-field text search, or filtering across many fields with variable combinations. Provides workflows for selecting the right search type, creating indexes, constructing queries, and optimizing performance using the MongoDB MCP server.
+  Covers everything about search in MongoDB: Atlas Search (full-text), Vector Search (semantic), and Hybrid Search. Use this skill for ANY question about MongoDB search, including open-ended and explanatory ones asked before the user has any data or use case — 'how does search work in MongoDB?', 'I'm new to MongoDB search, where do I start?', 'what's the difference between Atlas Search and Vector Search?', 'which search type should I use?', 'what is vector search?', 'how does automated embedding work?', 'can you explain hybrid search?'. Do not answer these from general knowledge; use this skill. Also use to build search features: full-text queries, autocomplete, fuzzy matching, faceted search, semantic similarity, embeddings, RAG, text containment or substring matching ('contains', 'includes'), case-insensitive or multi-field text search, and filtering across many fields. Provides workflows for choosing a search type, creating indexes, writing queries, and optimizing performance via the MongoDB MCP server.
 license: Apache-2.0
 metadata:
   version: "1.0.0"
@@ -10,19 +10,47 @@ disable-model-invocation: true
 
 # MongoDB Search and AI Recommendations Skill
 
-You are helping MongoDB users implement, optimize, and troubleshoot Atlas Search (lexical), Vector Search (semantic), and Hybrid Search (combined) solutions. Your goal is to understand their use case, recommend the appropriate search approach, and help them build effective indexes and queries.
+You are helping MongoDB users implement, optimize, and troubleshoot Atlas Search (lexical), Vector Search (semantic), and Hybrid Search (combined) solutions.
 
 ## Core Principles
 
 1. **Understand before building** - Validate the use case to ensure you recommend the right solution
 2. **Always inspect first** - Check existing indexes and schema before making recommendations
 3. **Explain before executing** - Describe what indexes will be created and require explicit approval
-4. **Optimize for the use case** - Different use cases require different index configurations and query patterns
-5. **Handle read-only scenarios** - If you do not have access to `create`, `update`, or `delete` operation tools, you are in read-only mode. Provide the complete index configuration JSON so the user can create it themselves, including via the Atlas UI.
-6. **Explain in accessible language** - Describe technical concepts and map business requirements to technical implementations in terms the user can follow.
+4. **Handle read-only scenarios** - Without `create`, `update`, or `delete` operation tools you are in read-only mode; hand the user index JSON to create themselves
+5. **Explain in accessible language** - Describe technical concepts and map business requirements to technical implementations in terms the user can follow
 
 ## Workflow
 
+### 0. Check for a Quickstart Request
+
+`references/quick-start.md` is a guided walkthrough that builds semantic, keyword, and hybrid search against the `sample_mflix` sample dataset. It is a teaching tour, not a way to build search for the user's own data.
+
+**Do not read `references/quick-start.md` until the user has chosen the tour.** A general request like "I'm new to search, help me get started" can just as easily mean "help me add search to my app." Use AskUserQuestion:
+
+> "Two ways I can take this — which fits better?"
+
+- **Guided tour on sample data** — we load Atlas's sample movie dataset and build semantic, keyword, and hybrid search on it step by step. Best for learning how each type works.
+- **Build search for my own data** — tell me what you're searching and I'll design the indexes and queries for your collections.
+
+Prompts that should trigger this offer, rather than being answered directly as a question:
+
+- "I'm new to MongoDB, how does search work?", "help me get started with search"
+- "what's the difference between Atlas Search and Vector Search?", "which search type should I use?"
+- "I want to try vector search", "show me semantic search", "how does automated embedding work?"
+- "I want to try keyword search", "show me full-text search", "I want to try hybrid search"
+
+Skip the offer only when the intent is already unambiguous:
+
+- **Explicit tour request** ("give me a guided tour", "walk me through search using sample data") — load `references/quick-start.md` and start at its Step 0.
+- **The user has their own collection, data, or concrete use case** — use the Discovery Phase below, even when they name a single search type.
+
+If the user named a specific search type, carry that into the walkthrough: it skips its own path question and routes straight to that path, after its prerequisite steps.
+
+The walkthrough requires an Atlas cloud cluster — the sample dataset loads from the Atlas UI, and Automated Embedding works on every Atlas tier with no key management. Atlas Local and self-managed MongoDB are out of scope; the walkthrough routes them back here when a step gives evidence of one.
+
+Otherwise, continue with the Discovery Phase.
+
 ### 1. Discovery Phase
 
 **Check the environment:**
@@ -48,7 +76,7 @@ Common questions to ask:
 
 ### 2. Determine Search Type and Consult the Reference File
 
-Match the use case to a search type below, then consult the linked reference file **before** recommending indexes or queries. Each reference file also documents the prerequisites you must verify first (cluster tier, MongoDB version, deployment requirements).
+Match the use case to a search type below, then consult the linked reference file **before** recommending indexes or queries. Each reference file also documents the prerequisites you must verify first (cluster tier, MongoDB version, deployment type, auto-scaling).
 
 **Atlas Search (Lexical/Full-Text):**
 Use when users need:
@@ -70,7 +98,7 @@ Use when users need:
 - Text data already stored in Atlas that they want to search by meaning
 - RAG or AI agent memory with minimal setup
 
-→ Consult `references/automated-embedding.md` and verify its cluster prerequisites (tier, deployment, auto-scaling) before creating the index or query.
+→ Consult `references/automated-embedding.md`.
 
 **Vector Search (Semantic, bring your own embeddings):**
 Use when users need:
@@ -89,7 +117,7 @@ Use when users need:
 - Results that factor in multiple relevance criteria
 - Uses `$rankFusion` (rank-based) or `$scoreFusion` (score-based) to merge pipelines
 
-→ Consult `references/hybrid-search.md` and verify its version requirements before building (also consult the lexical/vector files for the individual pipeline stages).
+→ Consult `references/hybrid-search.md`, plus the lexical/vector files for the individual pipeline stages.
 
 ### 3. Execution and Validation
 
@@ -118,17 +146,7 @@ Use when users need:
 
 ## Handling Edge Cases
 
-**User mentions fields you can't find:**
-- Use `collection-schema` to inspect available fields
-- Suggest alternatives or ask for clarification
-
-**Required field doesn't exist:**
-- Explain what needs to be added and how (e.g., embedding field for vector search)
-
-**Query fails or index missing:**
-- Use `collection-indexes` to verify index exists
-- If missing, explain index needs to be created first
-
-**Multiple collections are relevant:**
-- List options and ask which one they mean
-- If context makes it obvious, confirm your assumption
+- **Fields you can't find** — inspect available fields with `collection-schema`, then confirm the intended field with the user
+- **A required field doesn't exist** — explain what to add and how (e.g., an embedding field for vector search)
+- **Query fails or index missing** — verify with `collection-indexes`; if absent, the index must be created first
+- **Multiple collections are relevant** — ask which one they mean, unless context makes it obvious

package/dist/global-skills/mongodb-search-and-ai/references/automated-embedding.md

@@ -44,13 +44,16 @@ All models use Voyage AI, hosted and managed by MongoDB (multi-tenant, US region
 | `voyage-4-lite` | High-volume, cost-sensitive applications | $0.00002 | $0.02 |
 | `voyage-4` | **(Recommended)** General text search, balanced performance | $0.00006 | $0.06 |
 | `voyage-4-large` | Maximum accuracy, complex semantic relationships | $0.00012 | $0.12 |
-| `voyage-code-3` | Code search, technical documentation | $0.00018 | $0.18 |
+| `voyage-code-4` | **(Recommended for code)** Code search, technical documentation | $0.00012 | $0.12 |
+| `voyage-code-3` | Legacy code model — use `voyage-code-4` instead | $0.00018 | $0.18 |
 
 **Decision guide:**
 - Default / unknown use case → `voyage-4`
 - Large collection, cost is a concern → `voyage-4-lite`
 - High-stakes retrieval where accuracy matters most → `voyage-4-large`
-- Codebase or technical docs search → `voyage-code-3`
+- Codebase or technical docs search → `voyage-code-4`
+
+**`voyage-code-4` requires an Atlas deployment.** On self-managed deployments, use `voyage-code-3` for code and technical documentation.
 
 **Free tokens:** 200 million tokens per model, one-time, shared across the entire Atlas organization. Does not refresh. See [Billing and Free Tokens](#billing-and-free-tokens) below for how consumption and invoicing work.
 
@@ -327,6 +330,7 @@ No standard rate limits — uses a separate inference tier optimized for through
 | `voyage-4-large` | 2,000 | 3,000,000 |
 | `voyage-4` | 2,000 | 8,000,000 |
 | `voyage-4-lite` | 2,000 | 16,000,000 |
+| `voyage-code-4` | 2,000 | 3,000,000 |
 | `voyage-code-3` | 2,000 | 3,000,000 |
 
 **Best practice:** space out bulk insert/update operations rather than sending them all at once — batching avoids hitting these per-minute limits.
@@ -340,6 +344,7 @@ No standard rate limits — uses a separate inference tier optimized for through
 | `voyage-4-large` | 3 | 2,000 |
 | `voyage-4` | 3 | 2,000 |
 | `voyage-4-lite` | 3 | 2,000 |
+| `voyage-code-4` | 3 | 2,000 |
 | `voyage-code-3` | 3 | 2,000 |
 
 **Paid cluster (M0 with a payment method, Flex, or M10+ dedicated):**
@@ -349,6 +354,7 @@ No standard rate limits — uses a separate inference tier optimized for through
 | `voyage-4-large` | 2,000 | 3,000,000 |
 | `voyage-4` | 2,000 | 8,000,000 |
 | `voyage-4-lite` | 2,000 | 16,000,000 |
+| `voyage-code-4` | 2,000 | 3,000,000 |
 | `voyage-code-3` | 2,000 | 3,000,000 |
 
 Paid-tier limits increase automatically as usage grows over time — no action needed to benefit from that growth.