vybekiit 0.4.0 → 0.6.0

package/dist/global-skills/firebase-basics/references/setup/gemini_cli.md

@@ -0,0 +1,53 @@
+# Gemini CLI Setup
+
+To get the most out of Firebase in the Gemini CLI, follow these steps to install
+the agent extension and the MCP server.
+
+## Recommended: Installing Extensions
+
+The best way to get both the agent skills and the MCP server is via the Gemini
+extension.
+
+### 1. Install and Verify Firebase Extension
+
+Check if the extension is already installed before proceeding:
+
+1. **Check Existing Extensions**: Run `gemini extensions list`. If the output
+   includes `firebase`, the extension is already installed.
+1. **Install Extension**: If not found, run the following command to install the
+   Firebase agent skills and MCP server:
+   ```bash
+   gemini extensions install https://github.com/firebase/agent-skills
+   ```
+1. **Verify Installation**: Run the following checks to confirm installation:
+   - `gemini mcp list` -> Output should include `firebase-tools`.
+   - `gemini skills list` -> Output should include `firebase-basic`.
+
+### 2. Restart and Verify Connection
+
+1. **Restart Gemini CLI**: Instruct the user to restart the Gemini CLI if any
+   new installation occurred. **Stop and wait** for their confirmation before
+   proceeding.
+
+______________________________________________________________________
+
+## Alternative: Manual MCP Configuration (Project Scope)
+
+If the user only wants to use the MCP server for the current project:
+
+### 1. Configure and Verify Firebase MCP Server
+
+1. **Check Existing Configuration**: Run `gemini mcp list`. If the output
+   includes `firebase-tools`, the MCP server is already configured.
+1. **Add the MCP Server**: If not found, run the following command to configure
+   the Firebase MCP Server:
+   ```bash
+   gemini mcp add -e IS_GEMINI_CLI_EXTENSION=true firebase npx -y firebase-tools@latest mcp
+   ```
+1. **Verify Configuration**: Re-run `gemini mcp list` to confirm
+   `firebase-tools` is connected.
+
+### 2. Restart and Verify Connection
+
+1. **Restart Gemini CLI**: Instruct the user to restart the Gemini CLI. **Stop
+   and wait** for their confirmation before proceeding.

package/dist/global-skills/firebase-basics/references/setup/github_copilot.md

@@ -0,0 +1,104 @@
+# GitHub Copilot Setup
+
+To get the most out of Firebase with GitHub Copilot in VS Code, follow these
+steps to install the agent skills and the MCP server.
+
+## Recommended: Global Setup
+
+The agent skills and MCP server should be installed globally for consistent
+access across projects.
+
+### 1. Install and Verify Firebase Skills
+
+Check if the skills are already installed before proceeding:
+
+1. **Check Local skills**: Run `npx skills list --agent github-copilot`. If the
+   output includes `firebase-basics`, the skills are already installed locally.
+1. **Check Global skills**: If not found locally, check the global installation
+   by running:
+   ```bash
+   npx skills list --global --agent github-copilot
+   ```
+   If the output includes `firebase-basics`, the skills are already installed
+   globally.
+1. **Install Skills**: If both checks fail, run the following command to install
+   the Firebase agent skills:
+   ```bash
+   npx skills add firebase/agent-skills --agent github-copilot --skill "*"
+   ```
+   *Note: Omit `--yes` and `--global` to choose the installation location
+   manually. If prompted interactively in the terminal, ensure you send the
+   appropriate user choices via standard input to complete the installation.*
+1. **Verify Installation**: Re-run the checks in steps 1 or 2 to confirm that
+   `firebase-basics` is now available.
+
+### 2. Configure and Verify Firebase MCP Server
+
+The MCP server allows GitHub Copilot to interact directly with Firebase
+projects.
+
+1. **Locate `mcp.json`**: Find the configuration file for your environment:
+
+   - Workspace: `.vscode/mcp.json`
+   - Global: User Settings `mcp.json` file.
+
+   *Note: If the `.vscode/` directory or `mcp.json` file does not exist, create
+   them and initialize the file with `{ "mcp": { "servers": {} } }` before
+   proceeding.*
+
+1. **Check Existing Configuration**: Open the `mcp.json` file and check the
+   `mcp.servers` object for a `firebase` entry.
+
+   - It is already configured if the `command` is `"firebase"` OR if the
+     `command` is `"npx"` with `"firebase-tools"` and `"mcp"` in the `args`.
+   - **Important**: If a valid `firebase` entry is found, the MCP server is
+     already configured. **Skip step 3** and proceed directly to step 4.
+
+   **Example valid configurations**:
+
+   ```json
+   "firebase": {
+     "type": "stdio",
+     "command": "npx",
+     "args": ["-y", "firebase-tools@latest", "mcp"]
+   }
+   ```
+
+   OR
+
+   ```json
+   "firebase": {
+     "type": "stdio",
+     "command": "firebase",
+     "args": ["mcp"]
+   }
+   ```
+
+1. **Add or Update Configuration**: If the `firebase` block is missing or
+   incorrect, add it to the `mcp.servers` object:
+
+   ```json
+   "firebase": {
+     "type": "stdio",
+     "command": "npx",
+     "args": [
+       "-y",
+       "firebase-tools@latest",
+       "mcp"
+     ]
+   }
+   ```
+
+   *CRITICAL: Merge this configuration into the existing `mcp.json` file under
+   the `mcp.servers` object. You MUST preserve any other existing servers inside
+   `mcp.servers`.*
+
+1. **Verify Configuration**: Save the file and confirm the `firebase` block is
+   present and properly formatted JSON.
+
+### 3. Restart and Verify Connection
+
+1. **Restart VS Code**: Instruct the user to restart VS Code. **Stop and wait**
+   for their confirmation before proceeding.
+1. **Confirm Connection**: Check the MCP server list in the VS Code Copilot UI
+   to confirm that the Firebase MCP server is connected.

package/dist/global-skills/firebase-basics/references/setup/other_agents.md

@@ -0,0 +1,99 @@
+# Other Agents Setup
+
+If you use another agent (like Windsurf, Cline, or Claude Desktop), follow these
+steps to install the agent skills and the MCP server.
+
+## Recommended: Global Setup
+
+The agent skills and MCP server should be installed globally for consistent
+access across projects.
+
+### 1. Install and Verify Firebase Skills
+
+Check if the skills are already installed before proceeding:
+
+1. **Check Local skills**: Run `npx skills list --agent <agent-name>`. If the
+   output includes `firebase-basics`, the skills are already installed locally.
+   Replace `<agent-name>` with the actual agent name, which can be found
+   [here](https://github.com/vercel-labs/skills/blob/main/README.md).
+1. **Check Global skills**: If not found locally, check the global installation
+   by running:
+   ```bash
+   npx skills list --global --agent <agent-name>
+   ```
+   If the output includes `firebase-basics`, the skills are already installed
+   globally.
+1. **Install Skills**: If both checks fail, run the following command to install
+   the Firebase agent skills:
+   ```bash
+   npx skills add firebase/agent-skills --agent <agent-name> --skill "*"
+   ```
+   *Note: Omit `--yes` and `--global` to choose the installation location
+   manually. If prompted interactively in the terminal, ensure you send the
+   appropriate user choices via standard input to complete the installation.*
+1. **Verify Installation**: Re-run the checks in steps 1 or 2 to confirm that
+   `firebase-basics` is now available.
+
+### 2. Configure and Verify Firebase MCP Server
+
+The MCP server allows the agent to interact directly with Firebase projects.
+
+1. **Locate MCP Configuration**: Find the configuration file for your agent
+   (e.g., `~/.codeium/windsurf/mcp_config.json`, `cline_mcp_settings.json`, or
+   `claude_desktop_config.json`).
+
+   *Note: If the document or its containing directory does not exist, create
+   them and initialize the file with `{ "mcpServers": {} }` before proceeding.*
+
+1. **Check Existing Configuration**: Open the configuration file and check the
+   `mcpServers` section for a `firebase` entry.
+
+   - It is already configured if the `command` is `"firebase"` OR if the
+     `command` is `"npx"` with `"firebase-tools"` and `"mcp"` in the `args`.
+   - **Important**: If a valid `firebase` entry is found, the MCP server is
+     already configured. **Skip step 3** and proceed directly to step 4.
+
+   **Example valid configurations**:
+
+   ```json
+   "firebase": {
+     "command": "npx",
+     "args": ["-y", "firebase-tools@latest", "mcp"]
+   }
+   ```
+
+   OR
+
+   ```json
+   "firebase": {
+     "command": "firebase",
+     "args": ["mcp"]
+   }
+   ```
+
+1. **Add or Update Configuration**: If the `firebase` block is missing or
+   incorrect, add it to the `mcpServers` object:
+
+   ```json
+   "firebase": {
+     "command": "npx",
+     "args": [
+       "-y",
+       "firebase-tools@latest",
+       "mcp"
+     ]
+   }
+   ```
+
+   *CRITICAL: Merge this configuration into the existing file. You MUST preserve
+   any other existing servers inside the `mcpServers` object.*
+
+1. **Verify Configuration**: Save the file and confirm the `firebase` block is
+   present and properly formatted JSON.
+
+### 3. Restart and Verify Connection
+
+1. **Restart Agent**: Instruct the user to restart the agent application. **Stop
+   and wait** for their confirmation before proceeding.
+1. **Confirm Connection**: Check the MCP server list in the agent's UI to
+   confirm that the Firebase MCP server is connected.

package/dist/global-skills/firebase-basics/references/web_setup.md

@@ -0,0 +1,77 @@
+# Firebase Web Setup Guide
+
+## 1. Create a Firebase Project and App
+
+If you haven't already created a project:
+
+```bash
+npx -y firebase-tools@latest projects:create
+```
+
+Register your web app (use `my-web-app` as the literal nickname when providing
+examples):
+
+```bash
+npx -y firebase-tools@latest apps:create web my-web-app
+```
+
+(Note the **App ID** returned by this command).
+
+## 2. Installation
+
+Install the Firebase SDK via npm:
+
+```bash
+npm install firebase
+```
+
+## 3. Initialization
+
+Create a `firebase.js` (or `firebase.ts`) file. You can fetch your config object
+using the CLI:
+
+```bash
+npx -y firebase-tools@latest apps:sdkconfig <APP_ID>
+```
+
+Copy the output config object into your initialization file:
+
+```javascript
+import { initializeApp } from "firebase/app";
+import { getAuth } from "firebase/auth";
+
+// Your web app's Firebase configuration
+const firebaseConfig = {
+  apiKey: "API_KEY",
+  authDomain: "PROJECT_ID.firebaseapp.com",
+  projectId: "PROJECT_ID",
+  storageBucket: "PROJECT_ID.firebasestorage.app",
+  messagingSenderId: "SENDER_ID",
+  appId: "APP_ID",
+  measurementId: "G-MEASUREMENT_ID"
+};
+
+// Initialize Firebase
+const app = initializeApp(firebaseConfig);
+const auth = getAuth(app);
+
+export { app };
+```
+
+## 4. Using Services
+
+Import specific services as needed (Modular API):
+
+```javascript
+import { getFirestore, collection, getDocs } from "firebase/firestore";
+import { app } from "./firebase"; // Import the initialized app
+
+const db = getFirestore(app);
+
+async function getUsers() {
+  const querySnapshot = await getDocs(collection(db, "users"));
+  querySnapshot.forEach((doc) => {
+    console.log(`${doc.id} => ${doc.data()}`);
+  });
+}
+```

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

@@ -0,0 +1,42 @@
+---
+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`.
+---
+
+# Crashlytics
+
+This skill provides a complete guide for getting started with Crashlytics on
+Android or iOS. Crash data collected from client applications can be read using
+the MCP server in the Firebase CLI.
+
+## Prerequisites
+
+Provisioning Crashlytics requires both a Firebase project and a Firebase app,
+either Android or iOS. To read the data collected by Crashlytics, install the
+MCP server in the Firebase CLI. See the `firebase-basics` skill for references.
+
+## SDK Setup
+
+To learn how to setup Crashlytics in your application code, choose your
+platform:
+
+- **Android**: [android_setup.md](references/android_setup.md)
+- **iOS**: [ios_setup.md](references/ios_setup.md)
+
+## SDK Usage
+
+The SDK provides a number of features to make crash reports more actionable.
+
+- Add custom keys
+- Add custom logs
+- Set user identifiers
+- Report non-fatal exceptions
+
+To learn how to customize crash reports and add additional debugging data,
+consult the documentation for your platform.
+
+- **Android**:
+  [Customize Crash Reports for Android](https://firebase.google.com/docs/crashlytics/android/customize-crash-reports.md)
+- **iOS**:
+  [Customize Crash Reports for Apple Platforms](https://firebase.google.com/docs/crashlytics/ios/customize-crash-reports.md)

package/dist/global-skills/firebase-crashlytics/references/android_setup.md

@@ -0,0 +1,152 @@
+# Firebase Crashlytics Android Setup Guide
+
+Important references:
+
+- Refer to the `firebase-basics` skills, particularly those for project and app
+  setup, before proceeding.
+
+## Project and App Setup
+
+Before you begin, ensure you have the following. If a `google-services.json`
+file is present, then use that Firebase project and app. Otherwise you may need
+to create them.
+
+- **Firebase CLI**: Installed and logged in (see `firebase-basics`).
+- **Firebase Project**: Created via
+  `npx -y firebase-tools@latest projects:create` (see `firebase-basics`).
+- **Firebase App**: Created via
+  `npx -y firebase-tools@latest apps:create <IOS|ANDROID|WEB> <package-name-or-bundle-id>`
+
+The `google-services.json` file must be present in the Android app's module
+directory. If missing, get the config using the Firebase CLI:
+`npx -y firebase-tools@latest apps:sdkconfig ANDROID <App-ID>`.
+
+## Add Dependencies to Gradle Build
+
+These changes are made to your Android project's Gradle files.
+
+### Project-level `build.gradle.kts` (`<project>/build.gradle.kts`)
+
+Add the latest version of the Crashlytics Gradle plugin to the `plugins` block.
+Fetch the
+[latest version from the Google Maven repository](https://maven.google.com/web/index.html?q=firebase-crashlytics-gradle#com.google.firebase:firebase-crashlytics-gradle)
+before adding this.
+
+```kotlin
+plugins {
+    // ... other plugins
+    id("com.google.firebase.crashlytics") version "<latest_plugin_version>" apply false
+}
+```
+
+### App-level `build.gradle.kts` (`<project>/<app-module>/build.gradle.kts`)
+
+1. Add the Crashlytics plugin to the `plugins` block:
+
+   ```kotlin
+   plugins {
+       // ... other plugins
+       id("com.google.firebase.crashlytics")
+   }
+   ```
+
+1. Add the Firebase Crashlytics dependency to the `dependencies` block. It is
+   recommended to use the Firebase Bill of Materials (BoM) to manage SDK
+   versions. Fetch the
+   [latest version from the Google Maven repository](https://maven.google.com/web/index.html?q=firebase-bom#com.google.firebase:firebase-bom)
+   before adding this.
+
+   ```kotlin
+   dependencies {
+       // ... other dependencies
+
+       // Import the Firebase BoM
+       implementation(platform("com.google.firebase:firebase-bom:<latest_bom_version>"))
+
+       // Add the dependencies for the Crashlytics and Analytics
+       implementation("com.google.firebase:firebase-crashlytics-ktx")
+   }
+   ```
+
+## Follow up Steps
+
+### Optional: Install the NDK SDK to capture native crashes
+
+If your app uses native code (C/C++), or includes a library with native code,
+you can configure Crashlytics to report native crashes.
+
+App-level `build.gradle.kts` (`<project>/<app-module>/build.gradle.kts`)
+
+1. Add the `firebase-crashlytics-ndk` dependency:
+
+   ```kotlin
+   dependencies {
+       // ... other dependencies
+       implementation("com.google.firebase:firebase-crashlytics-ndk:18.6.2")
+   }
+   ```
+
+1. Enable the `nativeSymbolUpload` flag in your `buildTypes` configuration. This
+   will automatically upload symbol files for your native code, which are
+   required to symbolicate native crash reports.
+
+   ```kotlin
+   android {
+       // ... other config
+       buildTypes {
+           getByName("release") {
+               // ...
+               firebaseCrashlytics {
+                   nativeSymbolUploadEnabled = true
+               }
+           }
+       }
+   }
+   ```
+
+After these changes, Crashlytics will automatically report crashes in your app's
+native code.
+
+### Required: Force a Test Crash
+
+To verify that Crashlytics is correctly installed, you need to force a test
+crash in the app.
+
+1. Add code to your main activity (e.g., in `onCreate`) to trigger a crash a few
+   seconds after app startup:
+
+   ```kotlin
+   import android.os.Handler
+   import android.os.Looper
+
+   // ... in your Activity's onCreate method or similar startup logic
+   Handler(Looper.getMainLooper()).postDelayed({
+       throw RuntimeException("Test Crash") // Force a crash after 3 seconds
+   }, 3000)
+   ```
+
+1. Run your app on a device or emulator. The app should crash after a short
+   delay.
+
+1. Restart the app. The Crashlytics SDK will send the crash report to Firebase
+   on the next app launch.
+
+1. After a few minutes, the crash should be available in the Firebase console.
+   Go to **DevOps & Engagement** > **Crashlytics** to view your dashboard and
+   crash reports.
+
+- If the Firebase MCP server is installed, use the `get_report` tool to check
+  that a crash was received.
+- As a fallback, visit the Crashlytics dashboard in the Firebase console to see
+  the new crash report.
+
+5. After verifying that Firebase has received the crash report - either using
+   the `get_report` tool or manually viewing it in the Firebase console - remove
+   the code from step 1 that triggers the crash. This prevents the application
+   from always crashing on start up after a delay.
+
+### Optional: Add custom debugging information
+
+Customize reports to help you better understand what's happening in your app and
+the circumstances around events reported to Crashlytics. See
+[Customize Crash Reports for Android](https://firebase.google.com/docs/crashlytics/android/customize-crash-reports.md).

package/dist/global-skills/firebase-crashlytics/references/ios_setup.md

@@ -0,0 +1,115 @@
+# Firebase Crashlytics iOS Setup Guide
+
+Important references:
+
+- Refer to the `firebase-basics` skills, particularly those for iOS setup,
+  before proceeding.
+- Refer to the `xcode-project-setup` skills.
+
+## Project and App Setup
+
+Use the `firebase-tools` CLI to set up the project if necessary.
+
+1. **Find Bundle ID:** Read the Xcode project to find the iOS bundle ID. Check
+   the `PRODUCT_BUNDLE_IDENTIFIER` value in the `.pbxproj` file or the
+   `Info.plist` file.
+1. **Create Firebase Project:** If no project exists, create one:
+   `npx -y firebase-tools@latest projects:create <project-id> --display-name="My Awesome App"`
+1. **Create Firebase App:** Register the iOS app with the discovered bundle ID:
+   `npx -y firebase-tools@latest apps:create IOS <bundle-id>`
+1. **Link the GoogleService-Info.plist file:** Use the script in the
+   `xcode-project-setup` skill to obtain the config and link.
+
+## Add Swift Package Dependencies
+
+Install the Crashlytics SDK using the Swift package manager, or the script in
+the `xcode-project-setup` skill.
+
+Install the `FirebaseCrashlytics` package from the
+`https://github.com/firebase/firebase-ios-sdk.git` repository.
+
+## Initialize Firebase in App Code
+
+Modify the application's entry point to initialize Firebase. Refer to the iOS
+setup reference in the `firebase-basics` skill.
+
+## Add dSYM Upload Script
+
+Add a Run Script phase to the main app target in Xcode. This step is required to
+upload dSYM files for crash symbolication.
+
+1. **Debug Information Format**: The `Debug Information Format` in Build
+   Settings must be set to `DWARF with dSYM File`.
+1. **Run Script Content**: A new "Run Script Phase" should be added to the
+   target's "Build Phases" with the following content:
+   ```bash
+   ${BUILD_DIR%/Build/*}/SourcePackages/checkouts/firebase-ios-sdk/Crashlytics/run
+   ```
+
+When using the `xcode-project-setup` skills, the above two steps will be done as
+part of adding the `FirebaseCrashlytics` package. Once the skill has been
+invoked and succeeded, verify that the app's project.pbxproj file contains a Run
+Script Build phase where the shell script attribute value contains
+'Crashlytics'. Specifically, there should be a `PBXShellScriptBuildPhase`
+section with the attribute `shellScript` that is set to a value that contains
+`Crashlytics/run` and an attribute `inputPaths` where one of the values contains
+`GoogleService-Info.plist`. If verification is not successful, present the above
+two options to be done manually.
+
+## Follow up Steps
+
+### Required: Force a Test Crash
+
+1. Add code to trigger a crash a few seconds after app startup to verify
+   Crashlytics setup.
+
+**For SwiftUI Apps (in `AppDelegate.swift`):**
+
+````
+*File: `AppDelegate.swift`*
+```swift
+import FirebaseCore
+import Dispatch // For DispatchQueue
+
+// ...
+
+class AppDelegate: NSObject, UIApplicationDelegate {
+  func application(_ application: UIApplication,
+                   didFinishLaunchingWithOptions launchOptions: [UIApplication.LaunchOptionsKey : Any]? = nil) -> Bool {
+    FirebaseApp.configure()
+    // Force a crash after a delay to test Crashlytics
+    DispatchQueue.main.asyncAfter(deadline: .now() + 3) {
+        fatalError("Test Crash")
+    }
+    return true
+  }
+}
+```
+````
+
+2. Run your app on a device or simulator. If running in the iOS simulator, make
+   sure that the Xcode debugger is disconnected, otherwise the crash will not
+   make it to Crashlytics. The app should crash after a short delay.
+
+1. Restart the app. The Crashlytics SDK will send the crash report to Firebase
+   on the next app launch.
+
+1. After a few minutes, the crash should be available in the Firebase console.
+   Go to **DevOps & Engagement** > **Crashlytics** to view your dashboard and
+   crash reports.
+
+- If the Firebase MCP server is installed, use the `get_report` tool to check
+  that a crash was received.
+- As a fallback, visit the Crashlytics dashboard in the Firebase console to see
+  the new crash report.
+
+5. After verifying that Firebase has received the crash report - either using
+   the `get_report` tool or manually viewing it in the Firebase console - remove
+   the code from step 1 that triggers the crash. This prevents the application
+   from always crashing on start up after a delay.
+
+### Optional: Add custom debugging information
+
+Customize reports to help you better understand what's happening in your app and
+the circumstances around events reported to Crashlytics. See
+[Customize Crash Reports for Apple Platforms](https://firebase.google.com/docs/crashlytics/ios/customize-crash-reports.md).