run prettier

Author: jhuleatt

.guides/config.json

@@ -6,4 +6,4 @@
       "args": ["-y", "firebase-tools@latest", "experimental:mcp"]
     }
   }
-}
+}

.guides/setup.md

@@ -7,26 +7,24 @@ This guide provides a step-by-step process for setting up a new Firebase Functio
 Replace the contents of `src/index.ts` (or `index.js`) with the following code to create a simple, modern v2 HTTP endpoint.
 
 ```typescript
-import {onRequest} from "firebase-functions/https";
+import { onRequest } from "firebase-functions/https";
 import * as logger from "firebase-functions/logger";
-import {defineString} from "firebase-functions/params";
+import { defineString } from "firebase-functions/params";
 
 // Define a configuration parameter for a greeting
-const greeting = defineString("GREETING", {default: "Hello"});
-
-export const helloWorld = onRequest(
-  { maxInstances: 1 },
-  async (request, response) => {
-    logger.info("Request received!", { structuredData: true });
-    response.send(`${greeting.value()} from Firebase!`);
-  },
-);
+const greeting = defineString("GREETING", { default: "Hello" });
+
+export const helloWorld = onRequest({ maxInstances: 1 }, async (request, response) => {
+  logger.info("Request received!", { structuredData: true });
+  response.send(`${greeting.value()} from Firebase!`);
+});
 ```
 
 **Key points for the agent:**
-*   Always import from `firebase-functions/*` for new functions.
-*   Use `logger` for structured logging.
-*   Use `defineString`, `defineInt`, `defineSecret` for environment configuration instead of `functions.config()`.
+
+- Always import from `firebase-functions/*` for new functions.
+- Use `logger` for structured logging.
+- Use `defineString`, `defineInt`, `defineSecret` for environment configuration instead of `functions.config()`.
 
 ## 2. Build TypeScript
 
@@ -41,10 +39,12 @@ npm run build
 Use the Firebase Emulators to test your function locally before deploying.
 
 Tell the user to run the following command in a separate terminal window to start the emulators:
+
 ```bash
 # Start the functions emulator
 firebase emulators:start --only functions
 ```
+
 The user can then interact with the function at the local URL provided by the emulator.
 
 ## 4. Deploy to Firebase
@@ -55,4 +55,5 @@ Once testing is complete, deploy the function to your Firebase project.
 # Deploy only the functions
 firebase deploy --only functions
 ```
+
 The agent will be prompted to set any parameters defined with `defineString` or other `define` functions that do not have a default value.

.guides/upgrade.md

@@ -4,9 +4,10 @@ This guide provides a step-by-step process for migrating a single Cloud Function
 
 ## 1. Identify a 1st-gen function to upgrade
 
-Find all 1st-gen functions in the directory. 1st-gen functions used a namespaced API like this: 
+Find all 1st-gen functions in the directory. 1st-gen functions used a namespaced API like this:
 
 **Before (1st Gen):**
+
 ```typescript
 import * as functions from "firebase-functions";
 
@@ -28,15 +29,17 @@ Ensure your `firebase-functions` and `firebase-admin` SDKs are up-to-date, and y
 Update your import statements to use the top-level modules.
 
 **After (2nd Gen):**
+
 ```typescript
-import {onRequest} from "firebase-functions/https";
+import { onRequest } from "firebase-functions/https";
 ```
 
 ## 4. Update Trigger Definition
 
 The SDK is now more modular. Update your trigger definition accordingly.
 
 **After (2nd Gen):**
+
 ```typescript
 export const webhook = onRequest((request, response) => {
   // ...
@@ -48,15 +51,17 @@ Here are other examples of trigger changes:
 ### Callable Triggers
 
 **Before (1st Gen):**
+
 ```typescript
 export const getprofile = functions.https.onCall((data, context) => {
   // ...
 });
 ```
 
 **After (2nd Gen):**
+
 ```typescript
-import {onCall} from "firebase-functions/https";
+import { onCall } from "firebase-functions/https";
 
 export const getprofile = onCall((request) => {
   // ...
@@ -66,15 +71,17 @@ export const getprofile = onCall((request) => {
 ### Background Triggers (Pub/Sub)
 
 **Before (1st Gen):**
+
 ```typescript
 export const hellopubsub = functions.pubsub.topic("topic-name").onPublish((message) => {
   // ...
 });
 ```
 
 **After (2nd Gen):**
+
 ```typescript
-import {onMessagePublished} from "firebase-functions/pubsub";
+import { onMessagePublished } from "firebase-functions/pubsub";
 
 export const hellopubsub = onMessagePublished("topic-name", (event) => {
   // ...
@@ -86,14 +93,17 @@ export const hellopubsub = onMessagePublished("topic-name", (event) => {
 Migrate from `functions.config()` to the new `params` module for environment configuration.
 
 **Before (`.runtimeconfig.json`):**
+
 ```json
 {
   "someservice": {
     "key": "somesecret"
   }
 }
 ```
+
 **And in code (1st Gen):**
+
 ```typescript
 const SKEY = functions.config().someservice.key;
 ```
@@ -102,26 +112,31 @@ const SKEY = functions.config().someservice.key;
 Define params in your code and set their values during deployment.
 
 **In `index.ts`:**
+
 ```typescript
-import {defineString} from "firebase-functions/params";
+import { defineString } from "firebase-functions/params";
 
 const SOMESERVICE_KEY = defineString("SOMESERVICE_KEY");
 ```
+
 Use `SOMESERVICE_KEY.value()` to access the value. For secrets like API keys, use `defineSecret`.
 
 **In `index.ts`:**
+
 ```typescript
-import {defineSecret} from "firebase-functions/params";
+import { defineSecret } from "firebase-functions/params";
 
 const SOMESERVICE_KEY = defineSecret("SOMESERVICE_KEY");
 ```
+
 You will be prompted to set the value on deployment, which is stored securely in Cloud Secret Manager.
 
 ## 6. Update Runtime Options
 
 Runtime options are now set directly within the function definition.
 
 **Before (1st Gen):**
+
 ```typescript
 export const func = functions
   .runWith({
@@ -134,8 +149,9 @@ export const func = functions
 ```
 
 **After (2nd Gen):**
+
 ```typescript
-import {onRequest} from "firebase-functions/https";
+import { onRequest } from "firebase-functions/https";
 
 export const func = onRequest(
   {
@@ -153,9 +169,10 @@ export const func = onRequest(
 Tell the user these steps to migrate safely:
 
 > To migrate traffic safely:
+>
 > 1.  Rename your new 2nd gen function with a different name.
 > 2.  Comment out any existing `minInstances` or `maxInstances` config and instead set `maxInstances` to `1` while testing.
 > 3.  Deploy it alongside the old 1st gen function.
 > 4.  Gradually introduce traffic to the new function (e.g., via client-side changes or by calling it from the 1st gen function).
 > 5.  Add back the original `minInstances` and `maxInstances` settings to the 2nd gen function.
-> 6.  Once you are confident, you can delete the 1st gen function.
+> 6.  Once you are confident, you can delete the 1st gen function.

.guides/usage.md

@@ -1,84 +1,93 @@
 ## Key Guidelines
 
-*   Always use 2nd-gen functions for new development.
-*   Use v1 functions *only* for Analytics, basic Auth, and Test Lab triggers.
-*   Use `firebase-functions` SDK version 6.0.0 and above
-*   Use top-level imports (e.g., `firebase-functions/https`). These are 2nd gen by default.
+- Always use 2nd-gen functions for new development.
+- Use v1 functions _only_ for Analytics, basic Auth, and Test Lab triggers.
+- Use `firebase-functions` SDK version 6.0.0 and above
+- Use top-level imports (e.g., `firebase-functions/https`). These are 2nd gen by default.
 
 ## Configuration: Use Secret Params for API Keys
 
 For sensitive information like API keys (e.g., for LLMs, payment providers, etc.), **always** use `defineSecret`. This stores the value securely in Cloud Secret Manager.
 
 ```typescript
-import {onRequest} from 'firebase-functions/https';
-import {logger} from 'firebase-functions/logger';
-import {defineString, defineSecret} from 'firebase-functions/params';
+import { onRequest } from "firebase-functions/https";
+import { logger } from "firebase-functions/logger";
+import { defineString, defineSecret } from "firebase-functions/params";
 
 // Securely define an LLM API key
-const LLM_API_KEY = defineSecret('LLM_API_KEY');
+const LLM_API_KEY = defineSecret("LLM_API_KEY");
 
 // Example function that uses the secret
 export const callLlm = onRequest({ secrets: [LLM_API_KEY] }, async (req, res) => {
   const apiKey = LLM_API_KEY.value();
-  
+
   // Use the apiKey to make a call to the LLM service
-  logger.info('Calling LLM with API key.');
+  logger.info("Calling LLM with API key.");
 
   // insert code here to call LLM...
-  
-  res.send('LLM API call initiated.');
+
+  res.send("LLM API call initiated.");
 });
 ```
+
 When you deploy a function with `secrets`, the CLI will prompt you to enter the secret's value.
 
 ## Use the Firebase Admin SDK
+
 To interact with Firebase services like Firestore, Auth, or RTDB from within your functions, you need to initialize the Firebase Admin SDK. Call `initializeApp` without any arguments so that Application Default Credentials are used.
 
 1.  **Install the SDK:**
+
     ```bash
     npm i firebase-admin
     ```
 
 2.  **Initialize in your code:**
+
     ```typescript
-    import * as admin from 'firebase-admin';
+    import * as admin from "firebase-admin";
 
     admin.initializeApp();
     ```
+
     This should be done once at the top level of your `index.ts` file.
 
 ## Common Imports
+
 ```typescript
 // HTTPS, Firestore, RTDB, Scheduled, Storage, Pub/Sub, Auth, Logging, Config
-import {onRequest} from 'firebase-functions/https';
-import {onDocumentUpdated} from 'firebase-functions/firestore';
-import {onValueWritten} from 'firebase-functions/database';
-import {onSchedule} from 'firebase-functions/scheduler';
-import {onObjectFinalized} from 'firebase-functions/storage';
-import {onMessagePublished} from 'firebase-functions/pubsub';
-import {beforeUserSignedIn} from 'firebase-functions/identity';
-import {logger, onInit} from 'firebase-functions';
-import {defineString, defineSecret} from 'firebase-functions/params';
+import { onRequest } from "firebase-functions/https";
+import { onDocumentUpdated } from "firebase-functions/firestore";
+import { onValueWritten } from "firebase-functions/database";
+import { onSchedule } from "firebase-functions/scheduler";
+import { onObjectFinalized } from "firebase-functions/storage";
+import { onMessagePublished } from "firebase-functions/pubsub";
+import { beforeUserSignedIn } from "firebase-functions/identity";
+import { logger, onInit } from "firebase-functions";
+import { defineString, defineSecret } from "firebase-functions/params";
 ```
 
-## 1st-gen Functions (Legacy Triggers)**
+## 1st-gen Functions (Legacy Triggers)\*\*
+
 Use the `firebase-functions/v1` import for Analytics and basic Auth triggers. These aren't supported in 2nd gen.
+
 ```typescript
-import * as functionsV1 from 'firebase-functions/v1';
+import * as functionsV1 from "firebase-functions/v1";
 
 // v1 Analytics trigger
-export const onPurchase = functionsV1.analytics.event('purchase').onLog(async (event) => {
-  logger.info('Purchase event', { value: event.params?.value });
+export const onPurchase = functionsV1.analytics.event("purchase").onLog(async (event) => {
+  logger.info("Purchase event", { value: event.params?.value });
 });
 
 // v1 Auth trigger
 export const onUserCreate = functionsV1.auth.user().onCreate(async (user) => {
-  logger.info('User created', { uid: user.uid });
+  logger.info("User created", { uid: user.uid });
 });
 ```
 
 ## Development Commands
-```bash
+
+````bash
 # Install dependencies
 npm install
 
@@ -89,8 +98,12 @@ npm run build
 # Tell the user to run the following command to start the emulators:
 ```bash
 firebase emulators:start --only functions
-```
+````
 
 # Deploy functions
+
 firebase deploy --only functions
+
+```
+
 ```