vybekiit 0.4.0 → 0.6.0

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

@@ -0,0 +1,113 @@
+# Firebase iOS Setup Guide
+
+# ⛔️ CRITICAL RULE: STATE MANAGEMENT (OBSERVATION VS COMBINE) ⛔️
+
+When writing or updating SwiftUI code, you **MUST** prioritize the modern Swift
+**Observation framework (`@Observable` macro and `@State`)** as your default
+approach.
+
+However, it is acceptable to use **Combine** (`ObservableObject`, `@Published`,
+`@StateObject`, `@EnvironmentObject`) under the following conditions:
+
+- The user explicitly asks you to use Combine.
+- There are strong signals in the existing codebase that the project is heavily
+  relying on Combine.
+
+If neither of those conditions are true, default to the Swift 5.9+ Observation
+framework.
+
+# ⛔️ CRITICAL RULE: INITIALIZATION ORDER ⛔️
+
+When using SwiftUI, you **MUST** ensure `FirebaseApp.configure()` is called
+**BEFORE** any Firebase-dependent state objects are initialized.
+
+- **UNSAFE (CRASH):** Declaring a `@State` (for `@Observable`) or `@StateObject`
+  (for Combine) property in the root `App` struct if its initializer touches
+  Firebase. Property initializers run *before* the `App.init()` body, meaning
+  the object's `init()` will fire before Firebase is configured.
+- **SAFE:** Initialize Firebase in `App.init()` and pass your state objects into
+  the sub-views (like `ContentView`), or use `onAppear` for delayed setup.
+
+Failing to follow this will result in a fatal crash:
+`Default FirebaseApp is not configured`.
+
+## 1. Create a Firebase Project and App (Automated)
+
+Do not use the Firebase Console. Use the CLI to automate setup:
+
+1. Create the project: `npx -y firebase-tools@latest projects:create`
+1. Action: Read the Xcode project (`.pbxproj` or `Info.plist`) to determine the
+   iOS bundle ID.
+1. Register the iOS app:
+   `npx -y firebase-tools@latest apps:create IOS <bundle-id>`
+1. Fetch the config: `npx -y firebase-tools@latest apps:sdkconfig IOS <App-ID>`
+1. Save the output as `GoogleService-Info.plist` in your Xcode project folder.
+   Ensure you remove any non-XML CLI output headers, and ensure the file is
+   linked to the main application target.
+
+## 2. Installation (Automated via Swift Package Manager CLI)
+
+Do not use raw text parsing, sed, or Ruby scripts (like `xcodeproj` gem) to
+modify `.pbxproj` files directly.
+
+Instead, use the **`xcode-project-setup`** skill. Load that skill using your
+tools to securely execute its native Swift package setup script. That skill
+handles installing the required SPM packages and safely linking the
+`GoogleService-Info.plist` file.
+
+> **💡 TIP: ALWAYS USE THE LATEST SDK VERSION** To ensure access to the latest
+> features and security fixes, always check for the most recent version of the
+> Firebase iOS SDK at
+> [https://github.com/firebase/firebase-ios-sdk/releases](https://github.com/firebase/firebase-ios-sdk/releases)
+> and use that version when adding the SPM dependency.
+
+## 3. Initialization
+
+Configure the shared `FirebaseApp` instance. You can do this either in a modern
+SwiftUI `App` structure or a traditional `AppDelegate`.
+
+### SwiftUI (Modern - SAFE PATTERN)
+
+```swift
+import SwiftUI
+import FirebaseCore
+
+@main
+struct YourApp: App {
+  // ⛔️ FATAL CRASH: @State private var auth = AuthManager()
+  // property initializers run before init(), causing FirebaseApp not configured error
+  @State private var authManager: AuthManager
+
+  init() {
+    // ✅ SAFE: This runs FIRST
+    FirebaseApp.configure()
+    
+    // ✅ SAFE: Initialize state ONLY AFTER Firebase is configured
+    _authManager = State(initialValue: AuthManager())
+  }
+
+  var body: some Scene {
+    WindowGroup {
+      ContentView()
+        .environment(authManager)
+    }
+  }
+}
+```
+
+### AppDelegate (Traditional / UIKit)
+
+```swift
+import UIKit
+import FirebaseCore
+
+@main
+class AppDelegate: UIResponder, UIApplicationDelegate {
+  func application(_ application: UIApplication,
+                   didFinishLaunchingWithOptions launchOptions: [UIApplication.LaunchOptionsKey : Any]? = nil) -> Bool {
+    // ✅ SAFE: Always the first line in didFinishLaunching
+    FirebaseApp.configure()
+    return true
+  }
+}
+```

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

@@ -0,0 +1,80 @@
+# Firebase Local Environment Setup
+
+This skill documents the bare minimum setup required for a full Firebase
+experience for the agent. Before starting to use any Firebase features, you MUST
+verify that each of the following steps has been completed.
+
+## 1. Verify Node.js
+
+- **Action**: Run `node --version`.
+
+- **Handling**: Ensure Node.js is installed and the version is `>= 20`. If
+  Node.js is missing or `< v20`, install it based on the operating system:
+
+  **Recommended: Use a Node Version Manager** This avoids permission issues when
+  installing global packages.
+
+  **For macOS or Linux:**
+
+  1. Guide the user to the
+     [official nvm repository](https://github.com/nvm-sh/nvm#installing-and-updating).
+  1. Request the user to manually install `nvm` and reply when finished. **Stop
+     and wait** for the user's confirmation.
+  1. Make `nvm` available in the current terminal session by sourcing the
+     appropriate profile:
+     ```bash
+     # For Bash
+     source ~/.bash_profile
+     source ~/.bashrc
+
+     # For Zsh
+     source ~/.zprofile
+     source ~/.zshrc
+     ```
+  1. Install Node.js:
+     ```bash
+     nvm install 24
+     nvm use 24
+     ```
+
+  **For Windows:**
+
+  1. Guide the user to download and install
+     [nvm-windows](https://github.com/coreybutler/nvm-windows/releases).
+  1. Request the user to manually install `nvm-windows` and Node.js, and reply
+     when finished. **Stop and wait** for the user's confirmation.
+  1. After the user confirms, verify Node.js is available:
+     ```bash
+     node --version
+     ```
+
+  **Alternative: Official Installer**
+
+  1. Guide the user to download and install the LTS version from
+     [nodejs.org](https://nodejs.org/en/download).
+  1. Request the user to manually install Node.js and reply when finished.
+     **Stop and wait** for the user's confirmation.
+
+## 2. Verify Firebase CLI
+
+- **Command**: `npx -y firebase-tools@latest --version`
+- **Expected**: Successfully outputs a version string.
+
+## 3. Verify Firebase Authentication
+
+You must be authenticated to manage Firebase projects.
+
+- **Action**: Run `npx -y firebase-tools@latest login`.
+- **Handling**: If the environment is remote or restricted (no browser access),
+  run `npx -y firebase-tools@latest login --no-localhost` instead.
+
+## 4. Install Agent Skills and MCP Server
+
+To fully manage Firebase, the agent needs specific skills and the Firebase MCP
+server installed. Refer to the main `SKILL.md` for direct links to the
+installation instructions specific to your agent environment.
+
+______________________________________________________________________
+
+**CRITICAL AGENT RULE:** Do NOT proceed with any other Firebase tasks until
+EVERY step above has been successfully verified and completed.

package/dist/global-skills/firebase-basics/references/refresh/android_studio.md

@@ -0,0 +1,41 @@
+# Refresh Android Studio Local Environment
+
+Follow these steps to refresh Gemini in Android Studio's local environment,
+ensuring that agent skills are fully up-to-date.
+
+Gemini in Android Studio expects skills to be located at `~/.agents/skills`.
+
+1. **List Available Skills:** Identify all Firebase skills available in the
+   repository:
+
+   ```bash
+   npx -y skills add firebase/agent-skills --list
+   ```
+
+1. **Check Currently Installed Skills:** Check the contents of the skills
+   directory to see what is currently installed:
+
+   ```bash
+   ls -la ~/.agents/skills
+   ```
+
+1. **Add Missing Skills:** Use the `skills` CLI to add skills. If the CLI
+   supports an `android_studio` agent identifier, you can run:
+
+   ```bash
+   npx -y skills add firebase/agent-skills --agent android_studio --skill "*" --yes
+   ```
+
+   If the `skills` CLI does not support Android Studio directly, you can
+   manually copy or symlink the desired skills from your local clone of
+   `firebase/agent-skills` to `~/.agents/skills`.
+
+1. **Update Existing Skills:** To update skills, you can try:
+
+   ```bash
+   npx -y skills update --agent android_studio --yes
+   ```
+
+   If manual installation was used, pull the latest changes from the
+   `firebase/agent-skills` repository and copy the updated files to
+   `~/.agents/skills`.

package/dist/global-skills/firebase-basics/references/refresh/antigravity.md

@@ -0,0 +1,64 @@
+# Refresh Antigravity Local Environment
+
+Follow these steps to refresh Antigravity's local environment, ensuring that
+their agent skills and plugins are fully up-to-date.
+
+Antigravity relies on `npx skills`. Updates should prioritize the global level;
+if skills are installed at the project level, omit the `--global` flag.
+
+1. **List Available Skills:** Identify all Firebase skills available in the
+   repository:
+
+   ```bash
+   npx -y skills add firebase/agent-skills --list
+   ```
+
+1. **Check Currently Installed Skills:** Determine which skills are already
+   installed and linked at both project and global levels:
+
+   ```bash
+   # Check project-level skills
+   npx -y skills list --agent antigravity
+
+   # Check global-level skills
+   npx -y skills list --agent antigravity --global
+   ```
+
+   *Note: If a skill shows `Agents: not linked` in the output, it is installed
+   but not currently available to Antigravity.*
+
+1. **Add Missing or Unlinked Skills:** Compare the results from Step 1 and Step
+   2\. For each missing or unlinked skill, follow the appropriate conditional
+   instruction below:
+
+   - **IF any Firebase skills were found at the PROJECT level in Step 2:** Add
+     the missing skill to the project level:
+
+     ```bash
+     npx -y skills add firebase/agent-skills --agent antigravity --skill "<SKILL_NAME>" --yes
+     ```
+
+   - **IF any Firebase skills were found at the GLOBAL level in Step 2:** Add
+     the missing skill to the global level:
+
+     ```bash
+     npx -y skills add firebase/agent-skills --agent antigravity --skill "<SKILL_NAME>" --global --yes
+     ```
+
+   - **IF NO Firebase skills were found in Step 2:** Add each missing skill to
+     the global level:
+
+     ```bash
+     npx -y skills add firebase/agent-skills --agent antigravity --skill "<SKILL_NAME>" --global --yes
+     ```
+
+1. **Update Existing Skills:** Update all currently installed skills to their
+   latest versions:
+
+   ```bash
+   # Update project-level skills
+   npx -y skills update --agent antigravity --yes
+
+   # Update global-level skills
+   npx -y skills update --agent antigravity --global --yes
+   ```

package/dist/global-skills/firebase-basics/references/refresh/claude.md

@@ -0,0 +1,12 @@
+# Refresh Claude Code Local Environment
+
+Follow these steps to refresh Claude Code's local environment, ensuring that
+their agent skills and plugins are fully up-to-date.
+
+Use Claude Code's native plugin manager instead of `npx`.
+
+1. **Update the Plugin:** Run the specific CLI command to update the Firebase
+   plugin:
+   ```bash
+   claude plugin update firebase@firebase
+   ```

package/dist/global-skills/firebase-basics/references/refresh/gemini-cli.md

@@ -0,0 +1,13 @@
+# Refresh Gemini CLI Local Environment
+
+Follow these steps to refresh Gemini CLI's local environment, ensuring that
+their agent skills and plugins are fully up-to-date.
+
+Use the native Gemini CLI extension manager instead of `npx`.
+
+1. **Update the Extension:** Run the specific CLI command to update:
+   ```bash
+   gemini extensions update firebase
+   ```
+   *Note: If the extension is named differently, replace `firebase` with the
+   correct name from `gemini extensions list`.*

package/dist/global-skills/firebase-basics/references/refresh/other-agents.md

@@ -0,0 +1,67 @@
+# Refresh Other Local Environment
+
+Follow these steps to refresh the local environment of other agents, ensuring
+that their agent skills and plugins are fully up-to-date.
+
+Other agents rely on `npx skills`. Updates should prioritize the global level;
+if skills are installed at the project level, omit the `--global` flag.
+
+Replace `<AGENT_NAME>` with the actual agent name, which can be found in the
+[skills repository README](https://github.com/vercel-labs/skills/blob/main/README.md).
+
+1. **List Available Skills:** Identify all Firebase skills available in the
+   repository:
+
+   ```bash
+   npx -y skills add firebase/agent-skills --list
+   ```
+
+1. **Check Currently Installed Skills:** Determine which skills are already
+   installed and linked for the agent at both project and global levels:
+
+   ```bash
+   # Check project-level skills
+   npx -y skills list --agent <AGENT_NAME>
+
+   # Check global-level skills
+   npx -y skills list --agent <AGENT_NAME> --global
+   ```
+
+   *Note: If a skill shows `Agents: not linked` in the output, it is installed
+   but not currently available to the agent.*
+
+1. **Add Missing or Unlinked Skills:** Compare the results from Step 1 and Step
+   2\. For each missing or unlinked skill, follow the appropriate conditional
+   instruction below:
+
+   - **IF any Firebase skills were found at the PROJECT level in Step 2:** Add
+     the missing skill to the project level:
+
+     ```bash
+     npx -y skills add firebase/agent-skills --agent <AGENT_NAME> --skill "<SKILL_NAME>" --yes
+     ```
+
+   - **IF any Firebase skills were found at the GLOBAL level in Step 2:** Add
+     the missing skill to the global level:
+
+     ```bash
+     npx -y skills add firebase/agent-skills --agent <AGENT_NAME> --skill "<SKILL_NAME>" --global --yes
+     ```
+
+   - **IF NO Firebase skills were found in Step 2:** Add each missing skill to
+     the global level:
+
+     ```bash
+     npx -y skills add firebase/agent-skills --agent <AGENT_NAME> --skill "<SKILL_NAME>" --global --yes
+     ```
+
+1. **Update Existing Skills:** Update all currently installed skills to their
+   latest versions:
+
+   ```bash
+   # Update project-level skills
+   npx -y skills update --agent <AGENT_NAME> --yes
+
+   # Update global-level skills
+   npx -y skills update --agent <AGENT_NAME> --global --yes
+   ```

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

@@ -0,0 +1,23 @@
+# Android Studio Setup
+
+This guide explains how to set up Firebase agent skills for Gemini in Android
+Studio.
+
+## Skills Installation
+
+Gemini in Android Studio expects skills to be located at `~/.agents/skills`.
+
+To install all Firebase skills, run the following command in your terminal:
+
+```bash
+npx -y skills add firebase/agent-skills --skill "*" --yes
+```
+
+Ensure that the skills are installed or linked to the `~/.agents/skills`
+directory.
+
+## MCP Setup
+
+MCP setup is currently skipped for Android Studio as it only supports SSE
+transport, while the Firebase CLI MCP server uses stdio. Direct integration is
+not supported without an SSE-to-stdio proxy.

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

@@ -0,0 +1,98 @@
+# Antigravity Setup
+
+To get the most out of Firebase in Antigravity, follow these steps to install
+the agent skills and the MCP server.
+
+### 1. Install and Verify Firebase Skills
+
+Check if the skills are already installed before proceeding:
+
+1. **Check Local skills**: Run `ls -d .agent/skills/firebase-basics` or
+   `ls -d .agents/skills/firebase-basics`. If the directory exists, 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 antigravity
+   ```
+   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 antigravity --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 Antigravity to interact directly with Firebase projects.
+This is considered the **mandatory extension configuration** required for full
+functionality.
+
+1. **Locate `mcp_config.json`**: Find the configuration file for your operating
+   system:
+
+   - macOS / Linux: `~/.gemini/antigravity/mcp_config.json`
+   - Windows: `%USERPROFILE%\\.gemini\\antigravity\\mcp_config.json`
+
+   *Note: If the `.gemini/antigravity/` directory or `mcp_config.json` file does
+   not exist, create them and initialize the file with `{ "mcpServers": {} }`
+   before proceeding.*
+
+1. **Check Existing Configuration**: Open `mcp_config.json` 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 `mcp_config.json` 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 Antigravity**: Instruct the user to restart the Antigravity
+   application. **Stop and wait** for their confirmation before proceeding.
+1. **Confirm Connection**: Check the MCP server list in the Antigravity UI to
+   confirm that the Firebase MCP server is connected.

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

@@ -0,0 +1,45 @@
+# Claude Code Setup
+
+To get the most out of Firebase in Claude Code, follow these steps to install
+the agent skills and the MCP server.
+
+## Recommended Method: Using Plugins
+
+The recommended method is using the plugin marketplace to install both the agent
+skills and the MCP functionality.
+
+### 1. Install and Verify Plugins
+
+Check if the plugins are already installed before proceeding:
+
+1. **Check Existing Skills**: Run `npx skills list --agent claude-code` to check
+   for local skills. Run `npx skills list --global --agent claude-code` to check
+   for global skills. Note whether the output includes `firebase-basics`.
+1. **Check Existing MCP Configuration**: Run `claude mcp list -s user` and
+   `claude mcp list -s project`. Note whether the output of either command
+   includes `firebase`.
+1. **Determine Installation Path**:
+   - If **both** skills and MCP configuration are found, the plugin is fully
+     installed. **Stop here and skip all remaining setup steps in this
+     document.**
+   - If **neither** are found, proceed to step 4.
+   - If **only one** is found (e.g., skills are installed but MCP is missing, or
+     vice versa), **stop and prompt the user**. Explain the mixed state and ask
+     if they want to proceed with installing the Firebase plugin before
+     continuing to step 4.
+1. **Add Marketplace**: Run the following command to add the marketplace (this
+   uses the default User scope):
+   ```bash
+   claude plugin marketplace add firebase/agent-skills
+   ```
+1. **Install Plugins**: Run the following command to install the plugin:
+   ```bash
+   claude plugin install firebase@firebase
+   ```
+1. **Verify Installation**: Re-run the checks in steps 1 and 2 to confirm the
+   skills and the MCP server are now available.
+
+### 2. Restart and Verify Connection
+
+1. **Restart Claude Code**: Instruct the user to restart Claude Code. **Stop and
+   wait** for their confirmation before proceeding.

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

@@ -0,0 +1,93 @@
+# Cursor Setup
+
+To get the most out of Firebase in Cursor, follow these steps to install the
+agent skills and the MCP server.
+
+### 1. Install and Verify Firebase Skills
+
+Check if the skills are already installed before proceeding:
+
+1. **Check Local skills**: Run `npx skills list --agent cursor`. 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 cursor
+   ```
+   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 cursor --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 Cursor to interact directly with Firebase projects.
+
+1. **Locate `mcp.json`**: Find the configuration file for your operating system:
+
+   - Global: `~/.cursor/mcp.json`
+   - Project: `.cursor/mcp.json`
+
+   *Note: If the directory or `mcp.json` file does not exist, create them and
+   initialize the file with `{ "mcpServers": {} }` before proceeding.*
+
+1. **Check Existing Configuration**: Open `mcp.json` 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 `mcp.json` 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 Cursor**: Instruct the user to restart the Cursor application.
+   **Stop and wait** for their confirmation before proceeding.
+1. **Confirm Connection**: Check the MCP server list in the Cursor UI to confirm
+   that the Firebase MCP server is connected.