vybekiit 0.7.26 → 0.7.27

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

@@ -1,7 +1,7 @@
 ---
 name: expo-overview
 description: "Framework (OSS). Entry point and router for every Expo or EAS task. Load this skill first — before writing code and before choosing another expo-* / eas-* skill — when the request, PRD, or spec mentions Expo, EAS, Expo Go, or an expo-* package, or the project has an `expo` dependency in `package.json`. Within that gate it also covers app specs and designs to implement (tabs, stacks, maps, lists, navigation, building from a screenshot), and phrasings like 'implement a mobile app', 'make my app look native', 'add navigation', 'fetch some data', 'upgrade my SDK', 'add Expo to my existing native app', 'ship to the App Store', or 'I'm new to Expo, where do I start'. A fully specified request (SDK pinned, libraries named, layout given) still routes through here — the shared setup rules still apply. Do NOT load it when neither signal is present: a bare React Native project with no `expo` dependency is not Expo work. Detects the real goal, routes to the right expo-* / eas-* skill, and owns the shared setup rules."
-version: 1.0.0
+version: 1.1.0
 license: MIT
 ---
 
@@ -12,9 +12,9 @@ license: MIT
 **Do not guess the skill from project files alone.** Many Expo goals look similar from
 the filesystem but need different skills.
 
-1. **Confirm this is Expo work** — the request mentions Expo, or `package.json` has an
-   `expo` dependency. If neither holds, stop: this skill does not apply. A bare React
-   Native project with no `expo` dependency is not Expo work.
+1. **Confirm this is Expo or EAS work** — the request mentions Expo or EAS, or
+   `package.json` has an `expo` dependency. Otherwise this skill does not apply.
+   A native app using EAS for delivery qualifies without an Expo runtime.
 2. **Read the user's goal** — what outcome do they want, in plain terms?
 3. **Classify it** using the Skill Map below, translating casual phrasing to a goal.
 4. **Confirm intent** if ambiguous ("Sounds like you want to ship to the stores — that's
@@ -27,7 +27,7 @@ Match the goal to a category, then the skill, then load that leaf's `SKILL.md`.
 
 **Build the app**
 - `expo-project-structure` — folder layout for a **new** Expo Router project: where screens, components, and config live (never restructure an existing app to match)
-- `expo-native-ui` — screens, styling, semantic colors, native controls, SF Symbols, media, animations, layout
+- `expo-native-ui` — screens, styling, semantic colors, native controls, SF Symbols, media, layout
 - `expo-router` — navigation: file-based routes, tabs / stacks / modals / sheets, links, headers
 - `expo-animation` — motion and gestures: Reanimated worklets, Gesture Handler, screen transitions, sheet and press feedback, haptics, and fixing animation that stutters on device
 - `expo-ui` — native UI components via `@expo/ui`: BottomSheet, Picker, Slider, Switch, Menu, Button, FieldGroup (grouped form sections), List / ListItem, and more — real SwiftUI on iOS, Jetpack Compose on Android. The universal layer needs SDK 56+ and runs in Expo Go; the drop-in replacements (`@gorhom/bottom-sheet`, `datetimepicker`, …) and platform-specific layers also exist on SDK 55.
@@ -40,17 +40,18 @@ Match the goal to a category, then the skill, then load that leaf's `SKILL.md`.
 > **Component selection rule:** whenever you need a UI component (list rows, bottom sheets, pickers, sliders, menus, buttons, segmented controls, toggles), **consult `expo-ui` first** to check whether `@expo/ui` has a native equivalent before reaching for a React Native built-in or a community library. Native `@expo/ui` components give the best platform fit, and on SDK 56+ the universal ones run in Expo Go with no custom build. Load `expo-ui` alongside `expo-native-ui` for any app that renders lists, detail sheets, or form controls. One exception: `@expo/ui` `List` renders native grouped rows (an iOS Settings screen), **not** a virtualized list — use `FlatList` / `FlashList` for large datasets.
 
 **Ship & operate**
-- `eas-app-stores` — build and submit to the App Store / Play Store / TestFlight, versions, and store metadata
+- `eas-app-stores` — build and submit iOS/Android apps (Expo and other React Native projects, plus existing native apps), TestFlight, versions, and store metadata
 - `eas-hosting` — deploy the web bundle to EAS Hosting; also author Expo Router API routes (`+api.ts` handlers) and their environments / domains
 - `eas-workflows` — EAS Workflow YAML and CI/CD pipelines
 - `eas-simulator` — run and drive the app on a remote iOS / Android simulator on EAS cloud
 - `expo-dev-client` — custom development builds
+- `eas-update` — configure, publish, test, and debug compatible over-the-air updates
 - `eas-update-insights` — OTA update health: crash rate, adoption, payload size
 - `eas-observe` — startup / launch / TTI performance with EAS Observe
 
 **Extend natively**
 - `expo-module` — native modules and views (Swift / Kotlin) with the Expo Modules API
-- `expo-brownfield` — embed Expo / React Native in an existing native app
+- `expo-brownfield` — embed Expo / React Native screens in native SwiftUI/UIKit or Android apps; isolated artifacts and integrated builds
 - `expo-app-clip` — iOS App Clip target (AASA, smart app banner)
 
 **Maintain & learn**
@@ -62,17 +63,21 @@ Match the goal to a category, then the skill, then load that leaf's `SKILL.md`.
 
 Some everyday phrasings don't obviously map to a skill name — translate before routing:
 
-- "Make it look native" → grouped controls / settings forms = `expo-ui`; screens, styling, animations = `expo-native-ui`; navigation = `expo-router`.
+- "Make it look native" → grouped controls / settings forms = `expo-ui`; screens, styling = `expo-native-ui`; motion = `expo-animation`; navigation = `expo-router`.
 - "Make the screens consistent" / "clean up the styling" / "set up a theme or design tokens" → `expo-design-system`.
-- "Ship it" / "get an .ipa or .apk" / "release to the stores" → `eas-app-stores` (build + submit, TestFlight, versions, store metadata).
+- "It looks AI-generated" / "too generic, not native" → `expo-design-system` (named native-slop tells + audit), with `expo-native-ui` for the platform idioms.
+- "Ship it" / "get an .ipa or .apk" / "release to the stores" / "put my Swift app on TestFlight" → `eas-app-stores` (build + submit, TestFlight, versions, store metadata).
 - "I'm new / where do I start" → scaffold first (see Shared setup rules), then route by goal.
 
 ## Shared setup rules
 
-These apply across every Expo skill, so handle them here once instead of repeating them
-in each leaf.
+Apply the rules that match the project and the requested task.
 
-- **No Expo project yet?** Start one the standard way before routing to a feature skill:
+- **Native app using EAS for delivery?** Route to `eas-app-stores`; its
+  `references/native-ios.md` covers SwiftUI/UIKit on iOS. Keep the existing native
+  project. Apply EAS auth/linking below; Expo scaffolding, SDK, and package-install
+  rules do not apply to this path.
+- **Starting a new Expo app?** Start one the standard way before routing to a feature skill:
   `npx create-expo-app@latest`, laying out folders per `expo-project-structure`. Then
   classify the user's goal and route.
 - **Detect the SDK version** before giving version-specific advice: read the `expo`

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

@@ -7,7 +7,7 @@ license: MIT
 
 # Expo Router Navigation
 
-Navigation and routing for Expo Router apps. For screen styling, colors, controls, animations, media, and visual effects, use the `expo-native-ui` skill.
+Navigation and routing for Expo Router apps. For screen styling, colors, controls, media, and visual effects, use the `expo-native-ui` skill; for motion and gestures, use `expo-animation`.
 
 ## References
 
@@ -217,18 +217,20 @@ export default function Layout({ segment }) {
         headerLargeTitleShadowVisible: false,
         headerLargeStyle: { backgroundColor: "transparent" },
         headerTitleStyle: { color: colors.label },
-        headerLargeTitle: true,
+        headerLargeTitleEnabled: true,
         headerBlurEffect: "none",
         headerBackButtonDisplayMode: "minimal",
       }}
     >
       <Stack.Screen name={screen} options={{ title: titles[screen] }} />
-      <Stack.Screen name="i/[id]" options={{ headerLargeTitle: false }} />
+      <Stack.Screen name="i/[id]" options={{ headerLargeTitleEnabled: false }} />
     </Stack>
   );
 }
 ```
 
+`headerLargeTitleEnabled` is the SDK 56+ option name; older SDKs use `headerLargeTitle`, which is deprecated upstream.
+
 ## Submitting Feedback
 If you encounter errors, misleading or outdated information in this skill, report it so Expo can improve:
 ```bash

package/dist/global-skills/expo-router/references/tabs.md

@@ -302,7 +302,7 @@ export default function HomeStack() {
     <Stack>
       <Stack.Screen
         name="index"
-        options={{ title: "Home", headerLargeTitle: true }}
+        options={{ title: "Home", headerLargeTitleEnabled: true }}
       />
       <Stack.Screen name="details" options={{ title: "Details" }} />
     </Stack>
@@ -403,14 +403,14 @@ import {
   ThemeProvider,
   DarkTheme,
   DefaultTheme,
-} from "@react-navigation/native";
+} from "expo-router/react-navigation";
 import { useColorScheme } from "react-native";
 import { Stack } from "expo-router";
 
 export default function Layout() {
   const colorScheme = useColorScheme();
   return (
-    <ThemeProvider theme={colorScheme === "dark" ? DarkTheme : DefaultTheme}>
+    <ThemeProvider value={colorScheme === "dark" ? DarkTheme : DefaultTheme}>
       <Stack />
     </ThemeProvider>
   );
@@ -420,12 +420,12 @@ export default function Layout() {
 If the app only uses a light or dark theme, you can directly pass `DarkTheme` or `DefaultTheme` to `ThemeProvider` without checking the color scheme.
 
 ```tsx
-import { ThemeProvider, DarkTheme } from "@react-navigation/native";
+import { ThemeProvider, DarkTheme } from "expo-router/react-navigation";
 import { Stack } from "expo-router";
 
 export default function Layout() {
   return (
-    <ThemeProvider theme={DarkTheme}>
+    <ThemeProvider value={DarkTheme}>
       <Stack />
     </ThemeProvider>
   );

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

@@ -81,7 +81,9 @@ These steps only apply when `ios/` and/or `android/` directories exist in the pr
 - If using Expo SDK 54 or later, ensure react-native-worklets is installed — this is required for react-native-reanimated to work.
 - Enable React Compiler in SDK 54+ by adding `"experiments": { "reactCompiler": true }` to app.json — it's stable and recommended
 - Delete sdkVersion from `app.json` to let Expo manage it automatically
-- Remove implicit packages from `package.json`: `@babel/core`, `babel-preset-expo`, `expo-constants`.
+- Review formerly implicit packages such as `@babel/core`, `babel-preset-expo`, and `expo-constants` individually instead of removing them wholesale. Keep any package that an installed dependency declares as a required peer.
+- Keep `expo-constants` as a direct dependency whenever `expo-router` is installed. Expo Router imports it and declares it as a required peer; relying on a transitive copy can break native autolinking outside Expo Go.
+- After removing any dependency, immediately run `npx expo-doctor` and restore anything it reports as a missing required peer.
 - If the babel.config.js only contains 'babel-preset-expo', delete the file
 - If the metro.config.js only contains expo defaults, delete the file
 

package/dist/global-skills/expo-web-to-native/references/false-friends.md

@@ -11,7 +11,7 @@ This is the single source of truth for the mapping; the SKILL.md steps name a fe
 | `<div>`, `<section>`, `<span>` | `<View>` | `View` is the only generic container; no semantic element variants. |
 | `<p>`, `<h1>`, raw text in JSX | `<Text>` | **All** text must sit inside `<Text>`. Bare strings in a `View` throw. |
 | `<img src>` | `<Image>` / `expo-image` | `expo-image` adds caching, blurhash, transitions. Remote images need an explicit `width`/`height` or a flex parent. |
-| `<button>`, `<a>` | `<Pressable>` (or `TouchableOpacity`) | No default styling, no hover. Wrap label text in `<Text>`. |
+| `<button>`, `<a>` | `<Pressable>` | No default styling, no hover. Wrap label text in `<Text>`. |
 | `<input>` | `<TextInput>` | Controlled via `value` + `onChangeText` (not `onChange`/`e.target.value`). |
 | `<ul>/<li>` rendered with `.map()` | `<FlatList>` / `<FlashList>` | `.map()` over a long list mounts every row at once → jank. Use a virtualized list with `data` + `renderItem`. |
 
@@ -29,7 +29,7 @@ This is the single source of truth for the mapping; the SKILL.md steps name a fe
 
 | Web | Native | Gotcha |
 |---|---|---|
-| `className` / CSS files | `StyleSheet.create` or NativeWind | Plain RN has no className. For Tailwind muscle memory use NativeWind (`expo-tailwind-setup`). |
+| `className` / CSS files | `StyleSheet.create` or NativeWind | Plain RN has no className. For Tailwind muscle memory use NativeWind. |
 | CSS cascade & inheritance | none | Styles don't inherit (except a few `Text` props like `color`/`fontSize` to nested `Text`). Style each node. |
 | `display: flex` opt-in, default `row` | flex always on, default **`column`** | Biggest layout surprise: flex is the only layout model and the main axis is vertical by default. |
 | `px`, `rem`, `%` | unitless numbers (dp) | `padding: 16` = density-independent pixels. `%` works in some props; no `rem`/`em`/`vh`. |

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

@@ -31,7 +31,7 @@ Disclosed reference for [`expo-web-to-native`](../SKILL.md), step 4. `false-frie
 The table gets the right *components*; "native" also lives in *motion and touch* - and a web port arrives with almost none, so you must add it. The tooling is in `expo-router` (navigation/transitions) and `expo-native-ui` (motion/effects); reach for it, don't hand-roll:
 
 - **Transitions for free** - use Expo Router's native-stack so push/pop, modals, and sheets animate with real platform physics; shared-element zoom via `expo-router` `zoom-transitions.md`.
-- **Motion** - Reanimated (`withSpring`/`withTiming`; `entering`/`exiting` for list items) + `react-native-gesture-handler` for swipes/drags → `expo-native-ui` `animations.md`.
+- **Motion** - Reanimated (`withSpring`/`withTiming`) + `react-native-gesture-handler` for swipes/drags → load the `expo-animation` skill (purpose gate, timing values, interruption).
 - **Touch** — `expo-haptics` on commits, selection changes, and pull-to-refresh — choreography, not just a toast buzz.
 - **Native rhythm** — large-title collapse on scroll, momentum / inverted scroll, a keyboard that pushes content (`KeyboardAvoidingView`).
 - **Respect reduced motion** — gate non-essential animation on Reanimated's `useReducedMotion()`.

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

@@ -42,7 +42,7 @@ Use the Gemini Developer API as a default, and only Agent Platform Gemini API
 
 The library is part of the standard Firebase Web SDK.
 
-`npm install -g firebase@latest`
+`npm install firebase@latest`
 
 If you're in a firebase directory (with a firebase.json) the currently selected
 project will be marked with "current" using this command:
@@ -177,21 +177,18 @@ without deploying new client code. See
 
 ## Initialization Code References
 
-| Language,   | Gemini API | Context URL                                     |
-: Framework,  : provider   :                                                 :
-: Platform    :            :                                                 :
-| :---------- | :--------- | :---------------------------------------------- |
-| Web Modular | Gemini     | firebase://docs/ai-logic/get-started            |
-: API         : Developer  :                                                 :
-:             : API        :                                                 :
-:             : (Developer :                                                 :
-:             : API)       :                                                 :
-| iOS (Swift) | Gemini     | [ios_setup.md](references/ios_setup.md)         |
-:             : Developer  :                                                 :
-:             : API        :                                                 :
-| Flutter     | Gemini     | [flutter_setup.md](references/flutter_setup.md) |
-: (Dart)      : Developer  :                                                 :
-:             : API        :                                                 :
+-   **Web Modular API**
+    -   Provider: Gemini Developer API
+    -   Reference: [usage_patterns_web.md](references/usage_patterns_web.md)
+-   **Android (Kotlin)**
+    -   Provider: Gemini Developer API
+    -   Reference: [usage_patterns_android.md](references/usage_patterns_android.md)
+-   **iOS (Swift)**
+    -   Provider: Gemini Developer API
+    -   Reference: [ios_setup.md](references/ios_setup.md)
+-   **Flutter (Dart)**
+    -   Provider: Gemini Developer API
+    -   Reference: [flutter_setup.md](references/flutter_setup.md)
 
 > [!WARNING] **CRITICAL: Use current model names:** Always check the
 > [Firebase AI Logic Models documentation](https://firebase.google.com/docs/ai-logic/models.md.txt)

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

@@ -88,8 +88,8 @@ content.
 
 ```swift
 let safetySettings = [
-  SafetySetting(category: .harassment, threshold: .blockLowAndAbove),
-  SafetySetting(category: .hateSpeech, threshold: .blockMediumAndAbove)
+  SafetySetting(harmCategory: .harassment, threshold: .blockLowAndAbove),
+  SafetySetting(harmCategory: .hateSpeech, threshold: .blockMediumAndAbove)
 ]
 
 let model = FirebaseAI.firebaseAI().generativeModel(
@@ -128,13 +128,12 @@ systems. *Note: Advanced workflows like function calling generally require a
 multi-turn Chat Session to handle the back-and-forth execution.*
 
 ```swift
-let getStockPriceTool = Tool(functionDeclarations: [
+let getStockPriceTool = Tool.functionDeclarations([
   FunctionDeclaration(
     name: "getStockPrice",
     description: "Get the current stock price for a given symbol.",
     parameters: [
-      "symbol": Schema(
-        type: .string,
+      "symbol": .string(
         description: "The stock symbol, e.g. AAPL"
       )
     ]

package/dist/global-skills/firebase-ai-logic-basics/references/usage_patterns_android.md

@@ -39,8 +39,8 @@ content using a Gemini model:
 
 ```kotlin
 import com.google.firebase.ai.FirebaseAI
-import com.google.firebase.ai.ktx.ai
-import com.google.firebase.ktx.Firebase
+import com.google.firebase.Firebase
+import com.google.firebase.ai.ai
 
 class MainActivity : AppCompatActivity() {
 
@@ -112,10 +112,10 @@ val image1: Bitmap = ... // Load your bitmap
 val image2: Bitmap = ...
 
 val response = model.generateContent(
-    content("Analyze these images for me") {
+    content {
         image(image1)
         image(image2)
-        text("Compare these two items.")
+        text("Analyze these images for me. Compare these two items.")
     }
 )
 Log.d(TAG, response.text)

package/dist/global-skills/firebase-ai-logic-basics/references/usage_patterns_web.md

@@ -23,7 +23,7 @@ const app = initializeApp(firebaseConfig);
 const ai = getAI(app, { backend: new GoogleAIBackend() });
 
 const generationConfig = {
-  candidate_count: 1,
+  candidateCount: 1,
   maxOutputTokens: 2048,
   stopSequences: [],
   temperature: 0.7,      // Balanced: creative but focused
@@ -141,7 +141,7 @@ const model = getGenerativeModel(ai, {
 const prompt = 'Generate an image of the Eiffel Tower with fireworks in the background.';
 
 // To generate an image, call `generateContent` with the text input
-const result = model.generateContent(prompt);
+const result = await model.generateContent(prompt);
 
 // Handle the generated image
 try {
@@ -166,7 +166,7 @@ const jsonModel = getGenerativeModel(ai, {
     generationConfig: {
         responseMimeType: "application/json",
         // Optional: Define a schema
-        schema = Schema.object({ ... });
+        responseSchema: Schema.object({ ... })
     }
 });
 

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

@@ -66,13 +66,16 @@ Configure Firebase Authentication in `firebase.json` by adding an 'auth' block:
 ```
 {
   "auth": {
-  "authorizedDomains": ["localhost"],
     "providers": {
       "anonymous": true,
       "emailPassword": true,
       "googleSignIn": {
         "oAuthBrandDisplayName": "Your Brand Name",
-        "supportEmail": "support@example.com"
+        "supportEmail": "support@example.com",
+        "authorizedRedirectUris": [
+          "https://my-project-id.firebaseapp.com/__/auth/handler",
+          "http://localhost:4000"
+        ]
       }
     }
   }
@@ -82,10 +85,10 @@ Configure Firebase Authentication in `firebase.json` by adding an 'auth' block:
 > [!NOTE] If the Google Sign-In popup opens and immediately closes with the
 > error `[firebase_auth/unauthorized-domain]`, it means the domain is not
 > authorized. For local development, ensure `localhost` is included in the
-> **Authorized Domains** list in the Firebase Console or via the
-> `authorizedDomains` field in `firebase.json`. **CRITICAL**: Do NOT include the
-> protocol or port number in the Authorized Domains list (e.g., use `localhost`,
-> NOT `http://localhost:9090`).
+> **Authorized Domains** list in the Firebase Console (Authentication >
+> Settings > Authorized domains). **CRITICAL**: Do NOT include the protocol or
+> port number in the Authorized Domains list (e.g., use `localhost`, NOT
+> `http://localhost:9090`).
 
 **CRITICAL**: After configuring `firebase.json`, you MUST deploy the auth
 configuration to the Firebase backend for the changes to take effect. This is
@@ -113,6 +116,8 @@ Enable other providers in the Firebase Console.
 **Android (Kotlin)** See
 [references/client_sdk_android.md](references/client_sdk_android.md).
 
+**iOS (Swift)** See [references/ios_setup.md](references/ios_setup.md).
+
 ### 3. Security Rules
 
 Secure your data using `request.auth` in Firestore/Storage rules.

package/dist/global-skills/firebase-auth-basics/references/client_sdk_android.md

@@ -37,9 +37,9 @@ ______________________________________________________________________
 In your Activity or Fragment, initialize the `FirebaseAuth` instance:
 
 ```kotlin
+import com.google.firebase.Firebase
 import com.google.firebase.auth.FirebaseAuth
-import com.google.firebase.auth.ktx.auth
-import com.google.firebase.ktx.Firebase
+import com.google.firebase.auth.auth
 
 class MainActivity : AppCompatActivity() {
 
@@ -47,8 +47,7 @@ class MainActivity : AppCompatActivity() {
 
     override fun onCreate(savedInstanceState: Bundle?) {
         super.onCreate(savedInstanceState)
-        val auth = Firebase.auth
-        
+        auth = Firebase.auth
         setContent {
             MaterialTheme {
                 Text("Auth initialized!")
@@ -75,7 +74,7 @@ class MainActivity : ComponentActivity() {
     override fun onCreate(savedInstanceState: Bundle?) {
         super.onCreate(savedInstanceState)
         val auth = Firebase.auth
-        
+
         setContent {
             MaterialTheme {
                 Text("Auth initialized!")

package/dist/global-skills/firebase-auth-basics/references/client_sdk_web.md

@@ -76,9 +76,9 @@ signInWithPopup(auth, provider)
 > it means the domain hosting your app is not authorized for OAuth operations in
 > your Firebase project.
 >
-> - **Fix**: Add your domain (e.g., `localhost` for local testing) to the
->   Authorized Domains list in the Firebase Console (Authentication > Settings >
->   Authorized domains) or in your `firebase.json` auth config.
+> -   **Fix**: Add your domain (e.g., `localhost` for local testing) to the
+>     Authorized Domains list in the Firebase Console (Authentication >
+>     Settings > Authorized domains).
 > - **CRITICAL**: Do NOT include the protocol or port number when adding the
 >   domain (e.g., use `localhost`, NOT `http://localhost:9090`).
 

package/dist/global-skills/firebase-auth-basics/references/flutter_setup.md

@@ -24,16 +24,17 @@ platform-specific quirks.
   `<meta name="google-signin-client_id" ... />` tag in `web/index.html`, the
   Dart Web Debug Service (DWDS) and the app will throw an assertion error and
   **hang infinitely**, resulting in a blank screen.
-- **Common Workaround**: If you intend to use Firebase Auth's
-  `signInWithPopup(GoogleAuthProvider())` for the web, you can conditionally
-  skip the local `GoogleSignIn` package initialization entirely:
-  ```dart
-  import 'package:flutter/foundation.dart' show kIsWeb;
+-   **Common Workaround**: If you intend to use Firebase Auth's
+    `signInWithPopup(GoogleAuthProvider())` for the web, you can conditionally
+    skip the local `GoogleSignIn` package initialization entirely:
 
-  if (!kIsWeb) {
+    ```dart
+    import 'package:flutter/foundation.dart' show kIsWeb;
+
+    if (!kIsWeb) {
     await GoogleSignIn.instance.initialize();
-  }
-  ```
+    }
+    ```
 
 ## 3. Web Logout Crashes
 
@@ -42,14 +43,15 @@ platform-specific quirks.
   `await GoogleSignIn.instance.signOut();` during the user's logout flow on the
   Web platform evaluates against an uninitialized context or unsupported
   environment, crashing the app.
-- **Solution**: Conditionally separate the logout logic for Web to rely entirely
-  on `FirebaseAuth`:
-  ```dart
-  if (!kIsWeb) {
+-   **Solution**: Conditionally separate the logout logic for Web to rely
+    entirely on `FirebaseAuth`:
+
+    ```dart
+    if (!kIsWeb) {
       await GoogleSignIn.instance.signOut();
-  }
-  await FirebaseAuth.instance.signOut();
-  ```
+    }
+    await FirebaseAuth.instance.signOut();
+    ```
 
 ## 4. Prototyping Workaround: Bypassing Firestore Composite Indices
 
@@ -99,19 +101,17 @@ class AuthService {
         return await _auth.signInWithPopup(authProvider);
       } else {
         // Mobile uses standard flow
-        final GoogleSignInAccount? googleUser = await GoogleSignIn.instance.authenticate();
-        if (googleUser == null) return null; // Cancelled
+        final GoogleSignInAccount googleUser = await GoogleSignIn.instance.authenticate();
+        final GoogleSignInAuthentication googleAuth = googleUser.authentication;
 
-        final GoogleSignInAuthentication googleAuth = await googleUser.authentication;
-        
         final AuthCredential credential = GoogleAuthProvider.credential(
           idToken: googleAuth.idToken,
         );
-        
+
         return await _auth.signInWithCredential(credential);
       }
     } catch (e) {
-      print("Error during Google Sign-In: \$e");
+      print("Error during Google Sign-In: $e");
       return null;
     }
   }
@@ -124,7 +124,7 @@ class AuthService {
       }
       await _auth.signOut();
     } catch (e) {
-      print("Error signing out: \$e");
+      print("Error signing out: $e");
     }
   }
 }
@@ -140,9 +140,8 @@ closes.
   `Sign-in failed: [firebase_auth/unauthorized-domain] This domain is not authorized for OAuth operation for your Firebase project.`
 - **Cause**: The domain (usually `localhost` during local testing) is not listed
   in the Authorized Domains in the Firebase Console.
-- **Solution**: Add `localhost` to the Authorized Domains list in the Firebase
-  Console (Authentication > Settings > Authorized domains) or in your
-  `firebase.json` auth config.
+-   **Solution**: Add `localhost` to the Authorized Domains list in the Firebase
+    Console (Authentication > Settings > Authorized domains).
 - **CRITICAL**: Do NOT include the protocol or port number when adding the
   domain (e.g., use `localhost`, NOT `http://localhost:9090`). Flutter Web often
   runs on random ports or specific ports, but Firebase Auth only cares about the

package/dist/global-skills/firebase-auth-basics/references/security_rules.md

@@ -1,8 +1,10 @@
 # Authentication in Security Rules
 
 Firebase Security Rules work with Firebase Authentication to provide rule-based
-access control. For better advice on writing safe security rules, enable the
-`firebase-firestore-basics` or `firebase-storage-basics` skills.
+access control. For Firestore Security Rules (`firestore.rules`), delegate to the
+`firestore-rules-author` subagent if subagent delegation is available, or
+see the `firestore-rules-creation` skill otherwise. For Cloud Storage rules,
+enable the `firebase-storage-basics` skill.
 
 The `request.auth` variable contains authentication information for the user
 requesting data.

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

@@ -15,7 +15,7 @@ to create them.
 - **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>`
+  `npx -y firebase-tools@latest apps:create ANDROID <display-name> --package-name=<package-name>`
 
 The `google-services.json` file must be present in the Android app's module
 directory. If missing, get the config using the Firebase CLI:
@@ -64,7 +64,8 @@ plugins {
        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")
+       implementation("com.google.firebase:firebase-crashlytics")
+       implementation("com.google.firebase:firebase-analytics")
    }
    ```
 
@@ -82,7 +83,7 @@ App-level `build.gradle.kts` (`<project>/<app-module>/build.gradle.kts`)
    ```kotlin
    dependencies {
        // ... other dependencies
-       implementation("com.google.firebase:firebase-crashlytics-ndk:18.6.2")
+       implementation("com.google.firebase:firebase-crashlytics-ndk")
    }
    ```
 
@@ -91,12 +92,14 @@ App-level `build.gradle.kts` (`<project>/<app-module>/build.gradle.kts`)
    required to symbolicate native crash reports.
 
    ```kotlin
+   import com.google.firebase.crashlytics.buildtools.gradle.CrashlyticsExtension
+
    android {
        // ... other config
        buildTypes {
            getByName("release") {
                // ...
-               firebaseCrashlytics {
+               configure<CrashlyticsExtension> {
                    nativeSymbolUploadEnabled = true
                }
            }

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

@@ -16,7 +16,7 @@ Use the `firebase-tools` CLI to set up the project if necessary.
 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>`
+   `npx -y firebase-tools@latest apps:create IOS <display-name> --bundle-id=<bundle-id>`
 1. **Link the GoogleService-Info.plist file:** Use the script in the
    `xcode-project-setup` skill to obtain the config and link.
 
@@ -65,9 +65,9 @@ two options to be done manually.
 
 **For SwiftUI Apps (in `AppDelegate.swift`):**
 
-````
 *File: `AppDelegate.swift`*
 ```swift
+import UIKit
 import FirebaseCore
 import Dispatch // For DispatchQueue
 
@@ -85,7 +85,6 @@ class AppDelegate: NSObject, UIApplicationDelegate {
   }
 }
 ```
-````
 
 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

package/dist/global-skills/firebase-data-connect/SKILL.md

@@ -117,6 +117,7 @@ generate:
     package: "com.example.dataconnect"
   swiftSdk:
     outputDir: "../ios-app/DataConnect"
+    package: "DataConnectGenerated"
 ```
 
 Generate SDKs:
@@ -175,7 +176,7 @@ Follow these patterns based on your current task:
    `npx -y firebase-tools@latest emulators:start --only dataconnect`.
 1. Write schema and operations.
 1. Seed local test data into `seed_data.gql`. Read
-   [reference/data_seeding.md](reference/data_seeding.md#local-prototyping-data-seeding).
+   [reference/data_seeding.md](reference/data_seeding.md#1-local-prototyping-data-seeding).
 1. Run `npx -y firebase-tools@latest dataconnect:compile` or
    `npx -y firebase-tools@latest dataconnect:sdk:generate` to validate them.
 1. Use the operations in your app and build it.

package/dist/global-skills/firebase-data-connect/examples.md

@@ -196,12 +196,12 @@ query MyProfile @auth(level: USER)
     operation: "UpdateProfile",
     condition: "mutation.auth.uid == request.auth.uid"
   }) {
-  user(uid_expr: "auth.uid") { id name }
+  user(uid_expr: "auth.uid") { uid displayName }
 }
 
 # Counterpart mutation for MyProfile
 mutation UpdateProfile($name: String!) @auth(level: USER) {
-  user_update(id_expr: "auth.uid", data: { name: $name })
+  user_update(key: { uid_expr: "auth.uid" }, data: { displayName: $name })
 }
 
 # Time-based: live leaderboard refreshing every 30 seconds
@@ -221,13 +221,13 @@ import { subscribe } from 'firebase/data-connect';
 // Subscribe to movie list — refreshes when AddReview mutation runs
 const unsubMovies = subscribe(listMoviesRef({ genre: 'Action' }), {
   onNext: (result) => updateMovieList(result.data.movies),
-  onError: (error) => console.error(error)
+  onErr: (error) => console.error(error) // Observer object property is `onErr` (positional overload parameter is `onError`)
 });
 
 // Subscribe to leaderboard — refreshes every 30 seconds
 const unsubLeaderboard = subscribe(movieLeaderboardRef(), {
   onNext: (result) => updateLeaderboard(result.data.movies),
-  onError: (error) => console.error(error)
+  onErr: (error) => console.error(error)
 });
 
 // Cleanup