npm - vybekiit - Versions diffs - 0.4.0 → 0.6.0 - Mend

vybekiit 0.4.0 → 0.6.0

This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.

Files changed (665) hide show

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

@@ -0,0 +1,193 @@
+# Web Feature Flags installation - Docs
+1.  1
+    ## Choose an installation method
+    Required
+    You can either add the JavaScript snippet directly to your HTML or install the JavaScript SDK via your package manager.
+    ## HTML snippet
+    Add this snippet to your website within the `<head>` tag. This can also be used in services like Google Tag Manager:
+    HTML
+    PostHog AI
+    ```html
+    <script>
+        !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=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",(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 unregister_for_session getFeatureFlag getFeatureFlagResult isFeatureEnabled reloadFeatureFlags updateEarlyAccessFeatureEnrollment getEarlyAccessFeatures on onFeatureFlags onSessionId getSurveys getActiveMatchingSurveys renderSurvey canRenderSurvey getNextSurveyStep identify setPersonProperties group resetGroups setPersonPropertiesForFlags resetPersonPropertiesForFlags setGroupPropertiesForFlags resetGroupPropertiesForFlags reset get_distinct_id getGroups get_session_id get_session_replay_url alias set_config startSessionRecording stopSessionRecording sessionRecordingStarted captureException loadToolbar get_property getSessionProperty createPersonProfile opt_in_capturing opt_out_capturing has_opted_in_capturing has_opted_out_capturing clear_opt_in_out_capturing debug".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',
+        })
+    </script>
+    ```
+    ## JavaScript SDK
+    Install the PostHog JavaScript library using your package manager. Then, import and initialize the PostHog library with your project token and host:
+    PostHog AI
+    ### npm
+    ```bash
+    npm install posthog-js
+    ```
+    ### yarn
+    ```bash
+    yarn add posthog-js
+    ```
+    ### pnpm
+    ```bash
+    pnpm add posthog-js
+    ```
+    JavaScript
+    PostHog AI
+    ```javascript
+    import posthog from 'posthog-js'
+    posthog.init('<ph_project_token>', {
+        api_host: 'https://us.i.posthog.com',
+        defaults: '2026-05-30'
+    })
+    ```
+2.  2
+    ## Send events
+    Recommended
+    Once installed, PostHog will automatically start capturing events. You can also manually send events to test your integration:
+    Click around and view a couple pages to generate some events. PostHog automatically captures pageviews, clicks, and other interactions for you.
+    If you'd like, you can also manually capture custom events:
+    JavaScript
+    PostHog AI
+    ```javascript
+    posthog.capture('my_custom_event', { property: 'value' })
+    ```
+3.  3
+    ## Use boolean feature flags
+    Required
+    Check if a feature flag is enabled:
+    ```javascript
+    if (posthog.isFeatureEnabled('flag-key')) {
+        // Do something differently for this user
+        // Optional: fetch the payload
+        const matchedFlagPayload = posthog.getFeatureFlagResult('flag-key')?.payload
+    }
+    ```
+4.  4
+    ## Use multivariate feature flags
+    Optional
+    For multivariate flags, check which variant the user has been assigned:
+    ```javascript
+    const matchedFlag = posthog.getFeatureFlagResult('flag-key')
+    if (matchedFlag?.variant == 'variant-key') { // replace 'variant-key' with the key of your variant
+        // Do something differently for this user
+        // Optional: read the payload from the same result
+        const matchedFlagPayload = matchedFlag?.payload
+    }
+    ```
+5.  5
+    ## Use feature flag payloads
+    Optional
+    Feature flags can include payloads with additional data. Fetch the payload like this:
+    ```javascript
+    const matchedFlagPayload = posthog.getFeatureFlagResult('flag-key')?.payload
+    ```
+6.  6
+    ## Ensure flags are loaded
+    Optional
+    Every time a user loads a page, we send a request in the background to fetch the feature flags that apply to that user. We store those flags in your chosen persistence option (local storage by default).
+    This means that for most pages, the feature flags are available immediately — **except for the first time a user visits**.
+    To handle this, you can use the `onFeatureFlags` callback to wait for the feature flag request to finish:
+    ```javascript
+    posthog.onFeatureFlags(function (flags, flagVariants, { errorsLoading }) {
+        // feature flags are guaranteed to be available at this point
+        if (posthog.isFeatureEnabled('flag-key')) {
+            // do something
+        }
+    })
+    ```
+7.  7
+    ## Reload feature flags
+    Optional
+    Feature flag values are cached. If something has changed with your user and you'd like to refetch their flag values:
+    ```javascript
+    posthog.reloadFeatureFlags()
+    ```
+8.  8
+    ## Running experiments
+    Optional
+    Experiments run on top of our feature flags. Once you've implemented the flag in your code, you run an experiment by creating a new experiment in the PostHog dashboard.
+9.  9
+    ## Next steps
+    Recommended
+    Now that you're evaluating flags, continue with the resources below to learn what else Feature Flags enables within the PostHog platform.
+    | Resource | Description |
+    | --- | --- |
+    | [Creating a feature flag](/docs/feature-flags/creating-feature-flags.md) | How to create a feature flag in PostHog |
+    | [Adding feature flag code](/docs/feature-flags/adding-feature-flag-code.md) | How to check flags in your code for all platforms |
+    | [Framework-specific guides](/docs/feature-flags/tutorials.md#framework-guides) | Setup guides for React Native, Next.js, Flutter, and other frameworks |
+    | [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-product-analytics/SKILL.md ADDED Viewed

@@ -0,0 +1,139 @@
+---
+name: instrument-product-analytics
+description: >-
+  Add PostHog product analytics events to track user behavior. Use after
+  implementing new features or reviewing PRs to ensure meaningful user actions
+  are captured. Also handles initial PostHog SDK setup if not yet installed.
+metadata:
+  author: PostHog
+---
+# Add PostHog product analytics events
+Use this skill to add product analytics events (capture calls) that track meaningful user actions in new or changed code. Use it after implementing features or reviewing PRs to ensure key user behaviors are captured. If PostHog is not yet installed, this skill also covers initial SDK setup. Supports any framework or language.
+Supported frameworks and languages: Next.js, React Router, Nuxt, Vue, TanStack Start, SvelteKit, Astro, Angular, Django, Flask, FastAPI, Laravel, PHP, Ruby on Rails, Go, Elixir, Android, iOS, Flutter, React Native, Expo, and more.
+## Instructions
+Follow these steps IN ORDER:
+STEP 1: Analyze the codebase and detect the platform.
+  -
+ Look for dependency files (package.json, pubspec.yaml, Podfile, Package.swift, requirements.txt, Gemfile, composer.json, go.mod, mix.exs, etc.) to determine the framework and language.
+  -
+ Look for lockfiles (pnpm-lock.yaml, package-lock.json, yarn.lock, bun.lockb, go.sum, pubspec.lock, Podfile.lock, Package.resolved, mix.lock) to determine the package manager.
+  - Check for existing PostHog setup. If PostHog is already installed and initialized, skip to STEP 5.
+STEP 2: Research integration. (Skip if PostHog is already set up.)
+  2.1. Find the reference file below that matches the detected framework — it is the source of truth for SDK initialization, provider setup, and event capture patterns. Read it now.
+  2.2. If no reference matches, fall back to your general knowledge and web search. Use posthog.com/docs as the primary search source.
+STEP 3: Install the PostHog SDK. (Skip if PostHog is already set up.)
+  - Add the PostHog SDK package for the detected platform. Do not manually edit package.json — use the package manager's install command.
+STEP 4: Initialize PostHog. (Skip if PostHog is already set up.)
+  - Follow the framework reference for where and how to initialize. This varies significantly by framework (e.g., instrumentation-client.ts for Next.js 15.3+, AppConfig.ready() for Django, create_app() for Flask).
+STEP 5: Plan event tracking.
+  - From the project's file list, select between 10 and 15 files that might have interesting business value for event tracking, especially conversion and churn events.
+  - Also look for files related to login that could be used for identifying users, along with error handling.
+  - Find any existing `posthog.capture()` code. Make note of event name formatting. Don't duplicate existing events; supplement them.
+  - Track actions only, not pageviews (those can be captured automatically). Exceptions can be made for "viewed"-type events at the top of a conversion funnel.
+  - **Server-side events are REQUIRED** if the project includes any instrumentable server-side code (API routes, server actions, webhook handlers, payment/checkout completion, authentication endpoints).
+STEP 6: Implement event capture.
+  - For each planned event, add `posthog.capture()` calls with useful properties.
+  - If a file already has existing integration code for other tools or services, don't overwrite or remove that code. Place PostHog code below it.
+  - Do not alter the fundamental architecture of existing files. Make additions minimal and targeted.
+  - You must read a file immediately before attempting to write it.
+STEP 7: Identify users.
+  - Add PostHog `identify()` calls on the client side during login and signup events. Use the contents of login and signup forms to identify users on submit.
+  - If both frontend and backend exist, pass the client-side session and distinct ID using `X-POSTHOG-DISTINCT-ID` and `X-POSTHOG-SESSION-ID` headers to the server-side code. On the server side, make sure events have a matching distinct ID.
+STEP 8: Add error tracking.
+  - Add PostHog exception capture error tracking to relevant files, particularly around critical user flows and API boundaries.
+STEP 9: Set up environment variables.
+  - Check if the project already has PostHog environment variables configured (e.g. in `.env`, `.env.local`, or framework-specific env files). If valid values already exist, skip this step.
+  - If the PostHog project token is missing, use the PostHog MCP server's `projects-get` tool to retrieve the project's `api_token`. If multiple projects are returned, ask the user which project to use. If the MCP server is not connected or not authenticated, ask the user for their PostHog project token instead.
+  - For the PostHog host URL: check the `projects-get` MCP response for a `region` field — `US` maps to `https://us.i.posthog.com`, `EU` maps to `https://eu.i.posthog.com`. If the region is not available from the MCP response or from existing project configuration, ask the user: "Are you on PostHog US Cloud or EU Cloud?" Do not assume US Cloud.
+  - Write these values to the appropriate env file using the framework's naming convention.
+  - Reference these environment variables in code instead of hardcoding them.
+STEP 10: Verify and clean up.
+  - Check the project for errors. Look for type checking or build scripts in package.json.
+  - Ensure any components created were actually used.
+  - Run any linter or prettier-like scripts found in the package.json.
+## Reference files
+- `references/EXAMPLE-next-app-router.md` - next-app-router example project code
+- `references/EXAMPLE-next-pages-router.md` - next-pages-router example project code
+- `references/EXAMPLE-react-react-router-6.md` - react-react-router-6 example project code
+- `references/EXAMPLE-react-react-router-7-framework.md` - react-react-router-7-framework example project code
+- `references/EXAMPLE-react-react-router-7-data.md` - react-react-router-7-data example project code
+- `references/EXAMPLE-react-react-router-7-declarative.md` - react-react-router-7-declarative example project code
+- `references/EXAMPLE-nuxt-3-6.md` - nuxt-3-6 example project code
+- `references/EXAMPLE-nuxt-4.md` - nuxt-4 example project code
+- `references/EXAMPLE-vue-3.md` - vue-3 example project code
+- `references/EXAMPLE-react-tanstack-router-file-based.md` - react-tanstack-router-file-based example project code
+- `references/EXAMPLE-react-tanstack-router-code-based.md` - react-tanstack-router-code-based example project code
+- `references/EXAMPLE-tanstack-start.md` - tanstack-start example project code
+- `references/EXAMPLE-sveltekit.md` - sveltekit example project code
+- `references/EXAMPLE-astro-static.md` - astro-static example project code
+- `references/EXAMPLE-astro-view-transitions.md` - astro-view-transitions example project code
+- `references/EXAMPLE-astro-ssr.md` - astro-ssr example project code
+- `references/EXAMPLE-astro-hybrid.md` - astro-hybrid example project code
+- `references/EXAMPLE-angular.md` - angular example project code
+- `references/EXAMPLE-django.md` - django example project code
+- `references/EXAMPLE-flask.md` - flask example project code
+- `references/EXAMPLE-fastapi.md` - fastapi example project code
+- `references/EXAMPLE-python.md` - python example project code
+- `references/EXAMPLE-laravel.md` - laravel example project code
+- `references/EXAMPLE-php.md` - php example project code
+- `references/EXAMPLE-ruby-on-rails.md` - ruby-on-rails example project code
+- `references/EXAMPLE-ruby.md` - ruby example project code
+- `references/EXAMPLE-android.md` - android example project code
+- `references/EXAMPLE-swift.md` - swift example project code
+- `references/EXAMPLE-react-native.md` - react-native example project code
+- `references/EXAMPLE-expo.md` - expo example project code
+- `references/next-js.md` - Next.js - docs
+- `references/react-router-v6.md` - React router v6 - docs
+- `references/react-router-v7-framework-mode.md` - React router v7 framework mode (remix v3) - docs
+- `references/react-router-v7-data-mode.md` - React router v7 data mode - docs
+- `references/react-router-v7-declarative-mode.md` - React router v7 declarative mode - docs
+- `references/nuxt-js-3-6.md` - Nuxt.js (v3.0 to v3.6) - docs
+- `references/nuxt-js.md` - Nuxt.js - docs
+- `references/vue-js.md` - Vue.js - docs
+- `references/tanstack-start.md` - Tanstack start - docs
+- `references/svelte.md` - Svelte - docs
+- `references/astro.md` - Astro - docs
+- `references/angular.md` - Angular - docs
+- `references/django.md` - Django - docs
+- `references/flask.md` - Flask - docs
+- `references/python.md` - Python - docs
+- `references/posthog-python.md` - PostHog python SDK
+- `references/dotnet.md` - .net - docs
+- `references/elixir.md` - Elixir - docs
+- `references/go.md` - Go - docs
+- `references/laravel.md` - Laravel - docs
+- `references/php.md` - Php - docs
+- `references/ruby-on-rails.md` - Ruby on rails - docs
+- `references/ruby.md` - Ruby - docs
+- `references/android.md` - Android - docs
+- `references/ios.md` - Ios - docs
+- `references/usage.md` - Ios SDK usage - docs
+- `references/configuration.md` - Ios SDK configuration - docs
+- `references/flutter.md` - Flutter - docs
+- `references/react-native.md` - React native - docs
+- `references/identify-users.md` - Identify users - docs
+Each framework reference contains SDK-specific installation, initialization, and usage patterns. Find the one matching the user's stack.
+## Key principles
+- **Environment variables**: Always use environment variables for PostHog keys. Never hardcode them.
+- **Minimal changes**: Add PostHog code alongside existing integrations. Don't replace or restructure existing code.
+- **Match the docs**: Follow the framework reference's initialization and capture patterns exactly.