vybekiit 0.7.34 → 0.7.35

package/dist/global-skills/expo-project-structure/SKILL.md

@@ -109,7 +109,7 @@ Based on [Expo app folder structure best practices](https://expo.dev/blog/expo-a
 ## 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-project-structure" "<actionable feedback>"
+npx --yes @expo/agent-cli@latest feedback --category skills --subject "expo-project-structure" "<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.
+If an agent repeatedly fails at an Expo task or the user has to step in, submit a brief report of the task, expected result, and what went wrong using `--category evals` and the relevant Expo package or command as `--subject`.

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

@@ -235,7 +235,7 @@ export default function Layout({ segment }) {
 ## 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-router" "<actionable feedback>"
+npx --yes @expo/agent-cli@latest feedback --category skills --subject "expo-router" "<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.
+If an agent repeatedly fails at an Expo task or the user has to step in, submit a brief report of the task, expected result, and what went wrong using `--category evals` and the relevant Expo package or command as `--subject`.

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

@@ -96,7 +96,7 @@ references/
 ## 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-ui" "<actionable feedback>"
+npx --yes @expo/agent-cli@latest feedback --category skills --subject "expo-ui" "<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.
+If an agent repeatedly fails at an Expo task or the user has to step in, submit a brief report of the task, expected result, and what went wrong using `--category evals` and the relevant Expo package or command as `--subject`.

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

@@ -145,7 +145,7 @@ The new architecture is enabled by default, the app.json field `"newArchEnabled"
 ## 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-upgrade" "<actionable feedback>"
+npx --yes @expo/agent-cli@latest feedback --category skills --subject "expo-upgrade" "<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.
+If an agent repeatedly fails at an Expo task or the user has to step in, submit a brief report of the task, expected result, and what went wrong using `--category evals` and the relevant Expo package or command as `--subject`.

package/dist/global-skills/expo-web-to-native/SKILL.md

@@ -86,7 +86,7 @@ Pass on parity of **content and behavior** — not pixels: a nativized screen sh
 ## 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-web-to-native" "<actionable feedback>"
+npx --yes @expo/agent-cli@latest feedback --category skills --subject "expo-web-to-native" "<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.
+If an agent repeatedly fails at an Expo task or the user has to step in, submit a brief report of the task, expected result, and what went wrong using `--category evals` and the relevant Expo package or command as `--subject`.

package/dist/global-skills/expo-web-to-native/references/verify-on-device.md

@@ -29,7 +29,7 @@ agent-browser screenshot web.png   # visual reference
 **Tip:** capture web baselines for every screen once, up front, then diff against them instead of re-opening the web app each iteration.
 
 **B. Capture the native screen** (iOS shown via `simctl`; Android note below):
-1. Run the app: `npx expo start --ios` (Expo Go). On **SDK 56+ both `@expo/ui` and DOM components run in Expo Go** — no dev build, no `react-native-webview` to install; reach for a dev build (the `expo-dev-client` skill) only for *custom* native modules. Stale-bundle trap: a CI-mode Metro + cached Expo Go can show an old build — terminate Expo Go and add `--clear` if a change doesn't appear.
+1. Run the app: `npx expo start --ios` (Expo Go). To keep the onboarding sheet, dev menu, and Tools button out of your screenshots on SDK 57 and earlier, and on the URLs you open yourself in step 3, see `../../expo-overview/references/launch-without-dev-menu.md`. On **SDK 56+ both `@expo/ui` and DOM components run in Expo Go** — no dev build, no `react-native-webview` to install; reach for a dev build (the `expo-dev-client` skill) only for *custom* native modules. Stale-bundle trap: a CI-mode Metro + cached Expo Go can show an old build — terminate Expo Go and add `--clear` if a change doesn't appear.
 2. Boot a sim: `xcrun simctl boot <udid>` (`xcrun simctl list devices available`); `open -a Simulator`.
 3. Open the route: deep-link `xcrun simctl openurl booted "exp://<lan-ip>:8081/--/<route>?<params>"`, or argent `launch-app` + `gesture-tap`.
 4. Capture: `xcrun simctl io booted screenshot native.png`, or `argent run describe --udid <udid>` for structure.

package/dist/global-skills/firebase-app-hosting-basics/SKILL.md

@@ -50,6 +50,8 @@ This is the recommended flow for most users.
        "ignore": [
          "node_modules",
          ".git",
+         ".next",
+         ".vercel",
          "firebase-debug.log",
          "firebase-debug.*.log",
          "functions"
@@ -62,9 +64,20 @@ This is the recommended flow for most users.
    [Configuration](references/configuration.md) for more information on how to
    do so.
 
-1. If the app needs safe access to sensitive keys, use
-   `npx -y firebase-tools@latest apphosting:secrets` commands to set and grant
-   access to secrets.
+1. Create the backend if it does not exist (`apphosting:backends:list`; switch
+   `--primary-region`, e.g. `us-east4`, if a region hits its 10-backend quota):
+
+   ```bash
+   npx -y firebase-tools@latest apphosting:backends:create --backend my-app-id --primary-region us-central1 --root-dir /
+   ```
+
+1. If the app needs safe access to sensitive keys, set and grant access after
+   creating the backend:
+
+   ```bash
+   printf '%s' '<value>' | npx -y firebase-tools@latest apphosting:secrets:set <secret-name> --data-file - --force
+   npx -y firebase-tools@latest apphosting:secrets:grantaccess <secret-name> --backend my-app-id
+   ```
 
 1. Run `npx -y firebase-tools@latest deploy` when you are ready to deploy.
 

package/dist/global-skills/firebase-app-hosting-basics/references/cli_commands.md

@@ -33,10 +33,6 @@ using the Firebase Console.
 
 - **Purpose**: Deletes a backend and its associated resources.
 
-### `npx -y firebase-tools@latest apphosting:rollouts:list <backend-id>`
-
-- **Purpose**: Lists the history of rollouts for a backend.
-
 ## Secrets Management
 
 App Hosting uses Cloud Secret Manager to securely handle sensitive environment
@@ -46,20 +42,20 @@ variables (like API keys).
 
 - **Purpose**: Creates or updates a secret in Cloud Secret Manager and makes it
   available to App Hosting.
-- **Behavior**: Prompts for the secret value (hidden input).
+- **Behavior**: Prompts for the secret value interactively, or reads from stdin
+  via `printf '%s' '<value>'` with `--data-file - --force`.
 
 ### `npx -y firebase-tools@latest apphosting:secrets:grantaccess <secret-name>`
 
 - **Purpose**: Grants the App Hosting service account permission to access the
   secret.
-- **Note**: Often handled automatically by `secrets:set`, but useful for
-  debugging permission issues or granting access to existing secrets.
+- **Note**: Pass `--backend <backend-id>` when reusing or updating an existing
+  secret.
 
 ## Automated deployment via GitHub (CI/CD)
 
-**IMPORTANT** Only use these commands if you are setting up automated
-deployments via GitHub. If you are managing deployments using
-`npx -y firebase-tools@latest deploy`, DO NOT use these commands.
+**IMPORTANT** Only use this command for GitHub CI/CD deployments, not with
+`npx -y firebase-tools@latest deploy`.
 
 ### `npx -y firebase-tools@latest apphosting:rollouts:create <backend-id>`
 
@@ -70,10 +66,12 @@ deployments via GitHub. If you are managing deployments using
 - **Use Case**: Useful for redeploying without code changes, or rolling back to
   a specific commit.
 
+## Backend Creation
+
 ### `npx -y firebase-tools@latest apphosting:backends:create`
 
-- **Purpose**: Creates a new App Hosting backend. Use this when setting up
-  automated deployments via GitHub.
+- **Purpose**: Creates a new App Hosting backend (pass `--backend`,
+  `--primary-region`, and `--root-dir` for non-interactive deploys).
 - **Options**:
   - `--app <webAppId>`: The ID of an existing Firebase web app to associate with
     the backend.

package/dist/global-skills/firebase-app-hosting-basics/references/configuration.md

@@ -47,7 +47,8 @@ Controls the resources allocated to the Cloud Run service that serves your app.
 
 ## `env` (Environment Variables)
 
-Defines environment variables available during build and/or runtime.
+Defines environment variables available during build and/or runtime (local
+`.env*` files are not uploaded, so declare required variables or secrets here).
 
 - `variable`: The name of the env var (e.g., `NEXT_PUBLIC_API_URL`).
 - `value`: A literal string value.

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

@@ -41,7 +41,8 @@ Complete these setup steps before proceeding:
        [references/setup/other_agents.md](references/setup/other_agents.md)
 
 1. **Authentication:** Ensure you are logged in to Firebase so that commands
-   have the correct permissions. Run `npx -y firebase-tools@latest login`. For
+   have the correct permissions. Run `npx -y firebase-tools@latest login:list`
+   first; if not logged in, run `npx -y firebase-tools@latest login`. For
    environments without a browser (e.g., remote shells), use
    `npx -y firebase-tools@latest login --no-localhost`.
 
@@ -51,15 +52,16 @@ Complete these setup steps before proceeding:
 
 1. **Active Project:** Most Firebase tasks require an active project context.
 
-   > [!IMPORTANT] **For Agents:** Before proceeding with project configuration,
-   > you MUST pause and ask the developer if they prefer to:
+   > [!IMPORTANT] **For Agents:** If no Project ID was provided, you MUST pause
+   > and ask the developer if they prefer to:
    >
    > 1. **Provide an existing Firebase Project ID**, or
    > 1. **Create a new Firebase project**.
 
    - **If using an existing Project ID:**
 
-     1. Check the current project by running `npx -y firebase-tools@latest use`.
+     1. Check the current project with `npx -y firebase-tools@latest use` (if
+        `firebase.json` is missing at the project root, create `{}` first).
 
      1. If the command outputs `Active Project: <project-id>`, confirm with the
         user if this is the intended project.

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

@@ -8,8 +8,8 @@ If you haven't already created a project:
 npx -y firebase-tools@latest projects:create
 ```
 
-Register your web app (use `my-web-app` as the literal nickname when providing
-examples):
+Check existing web apps first (`npx -y firebase-tools@latest apps:list WEB`), or
+register one (use `my-web-app` as the literal nickname when providing examples):
 
 ```bash
 npx -y firebase-tools@latest apps:create web my-web-app
@@ -31,7 +31,7 @@ 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>
+npx -y firebase-tools@latest apps:sdkconfig WEB <APP_ID>
 ```
 
 Copy the output config object into your initialization file: