fbs-to-agy-export

name	fbs-to-agy-export
description	Prepares a Firebase Studio exported project for use with Antigravity. Make sure to use this skill whenever the user mentions "Antigravity export", "Firebase Studio export", or wants to finalize, finish, or set up a Firebase Studio project. Even if they just say "get me started with this export" or "export to AGY", this is the skill to use.

Preparing Firebase Studio Projects for Antigravity

Prepare a Firebase Studio exported project for use with Antigravity. You must execute these steps sequentially because later steps depend on the environment and dependencies set up in earlier steps. Do not skip steps unless explicitly instructed by a conditional evaluation.

Workflow Instructions

Prerequisites: Context Gathering

Determine the following variables before executing any commands. If automatic determination fails, ask the user.

[!IMPORTANT] Maintain State: These variables define the Current Project State. You MUST refer to these values before every conditional step.

1. Determine Target Folder (<TARGET_FOLDER>):
   • The folder is valid only if it contains an .idx/ subdirectory.
   • Check if the current working directory contains .idx/. If so, set <TARGET_FOLDER> to the current directory.
   • If not, stop and ask the user to provide the correct absolute path to the project folder.
2. Determine the type of project (<FBS_PROJECT_TYPE>):
   • If the project contains next.config.ts, set <FBS_PROJECT_TYPE> to "NextJS".
   • If the project contains pubspec.yaml, set <FBS_PROJECT_TYPE> to "Flutter".
   • If the project contains angular.json, set <FBS_PROJECT_TYPE> to "Angular".
   • Otherwise, attempt to determine the project type by checking the project's primary language.

Step 1: Verify Node.js Environment (>= 20)

Firebase Studio exports require a modern Node.js environment (>= v20) to run build tools and servers. You must ensure this base requirement is met before proceeding.

1. Check Version: Execute node --version in the terminal.
2. Evaluate Result:
   • If the version is >= v20.x.x, validation passes. Proceed immediately to Step 2.
   • If the version is < v20.x.x, or if Node.js is not found, perform one of the remediation paths below based on the OS.

Remediation Path: macOS / Linux

Attempt to install Node.js 24 using nvm.

1. Install nvm:

   curl -o- https://raw.githubusercontent.com/nvm-sh/nvm/v0.40.4/install.sh | bash
   

2. Load nvm: Source the configuration file for the active shell (e.g., source ~/.bash_profile, source ~/.bashrc, source ~/.zprofile, source ~/.zshrc, or source ~/.profile).
3. Install Node:

   nvm install 24
   nvm use 24
   

4. Verify: Run node --version. If it is now >= v20.x.x, proceed to Step 2. If it fails, fallback to the Manual Installation path.

Remediation Path: Windows

Guide the user to use nvm-windows.

1. Instruct: Ask the user to download and install nvm-windows.
2. Wait: Stop and wait for the user to confirm they have installed nvm-windows. Do not execute further steps until they reply.
3. Install Node: Once confirmed, install Node.js 24:

   nvm install 24
   nvm use 24
   

4. Verify: Run node --version. If it is now >= v20.x.x, proceed to Step 2. If it fails, fallback to the Manual Installation path.

Remediation Path: Manual Installation (Fallback)

Use this path if automated tools fail or the OS is unsupported.

1. Instruct: Ask the user to download and manually install Node.js 24+ directly from nodejs.org.
2. Wait: Stop and wait for the user to confirm the installation is complete.
3. Verify: Run node --version. Validate it is >= v20.x.x before proceeding to Step 2.

Step 2: Firebase Login and Export

1. Login: Ensure the user is authenticated with the Firebase CLI.

   npx -y firebase-tools@latest login
   

   (Timeout Warning: If this command hangs waiting for browser interaction, check the terminal output, extract the login URL, provide it to the user, and stop waiting. Do not block indefinitely.)
2. Export Project: Execute the export command using the information gathered in the Prerequisites.

   npx -y firebase-tools@latest studio:export <TARGET_FOLDER> --no-start-antigravity
   

Step 3: Post export check

After the studio:export command finishes, you MUST perform a multiple-point validation:

1. Verify CLI Availability:
   • Collect a list of CLIs you need to build and run this project. The potential CLIs can be found in
     • In the Antigravity global MCP configuration file, inspect its command property (e.g., if "command": "dart" is specified). Note its platform-dependent location:
       • macOS / Linux: ~/.gemini/antigravity/mcp_config.json
       • Windows: %APPDATA%geminiantigravitymcp_config.json (or ~AppDataRoaminggeminiantigravitymcp_config.json)
     • In .idx/dev.nix file, inspect its command property (e.g., if command = ["foo" "bar" "baz"]; is specified).
     • Inspect README.md file for any additional information.
     • Check the value of <FBS_PROJECT_TYPE> for more information:
       • If <FBS_PROJECT_TYPE> is "NextJS", check CLI used in nextjs.md.
       • If <FBS_PROJECT_TYPE> is "Flutter", check CLI used in flutter.md.
       • If <FBS_PROJECT_TYPE> is anything else, use your best knowledge base on <FBS_PROJECT_TYPE> to determine the CLI used to build and run the project.
   • Check if that specific CLI command is currently installed and available in the system PATH (e.g., by executing which <command> on Mac/Linux or where <command> on Windows).
   • If the required CLI is not available:
     • Since Node.js is already installed, prioritize using npx to trigger the CLI if it's available as an npm package (e.g., you can modify the MCP config to use "command": "npx", "args": ["-y", "<package>", ...]).
     • If it cannot be run via npx (e.g., dart), proactively attempt to install the CLI yourself using the OS-appropriate package manager (e.g., brew install dart on macOS, apt-get on Linux).
     • If the automated installation fails or is not possible, explicitly ask the user to install the specific CLI and stop to wait for them to confirm completion.
   • For macOS / Linux, source the configuration file for the active shell (e.g., source ~/.bash_profile, source ~/.bashrc, source ~/.zprofile, source ~/.zshrc, or source ~/.profile).
2. Verify Project Health by trying to compile and build the project.
   • Check the value of <FBS_PROJECT_TYPE> for more information:
     • If <FBS_PROJECT_TYPE> is "NextJS", follow instructions in nextjs.md.
     • If <FBS_PROJECT_TYPE> is "Flutter", follow instructions in flutter.md.
     • If <FBS_PROJECT_TYPE> is anything else, follow instructions in other.md.

Step 4: Preview

Validate that the exported project can be previewed. The command can usually be found in .idx/dev.nix file, ex.

    previews = {
      enable = true;
      previews = {
        web = {
          command = ["npm" "run" "dev" "--" "--port" "$PORT" "--hostname" "0.0.0.0"];
          manager = "web";
        };
      };
    };

Focus on web preview for now. You can evaluate project health by checking:

• If the preview server starts successfully, wait for the URL to be displayed.
• Open the URL in the browser.
• Ask the user if the app is running correctly.
• If any command fails (install, typecheck, build, start), analyze the error output and attempt to fix the code automatically. If you cannot fix it, stop and consult the user.
• If the app is not running correctly, stop the preview server and ask the user for more information.
• Functional Verification: If applicable and the project has a web UI, use your browser tools or a browser subagent to navigate to the preview URL. Verify the page renders without critical console errors, and perform basic interaction testing (e.g., clicking primary buttons).

Step 5: Build Local Knowledge

To minimize repeating investigation work in future sessions, you must codify the build and preview commands that you have discovered into reusable Antigravity workflows.

Create the following two workflow files in the target project folder:

• <TARGET_FOLDER>/.agents/workflows/build_project.md: Write a step-by-step workflow detailing every command required to install dependencies, compile, and build the project.
• <TARGET_FOLDER>/.agents/workflows/preview_project.md: Write a step-by-step workflow detailing the exact commands needed to start the preview server and test the project.

Step 6: Restart Antigravity

Instruct the user to restart their Antigravity IDE environment so that all configurations take effect.

1. Instruct: Tell the user they must restart Antigravity IDE to pick up the changes.
2. Wait: Stop and wait for the user to confirm they have restarted their IDE.

---

Completion: Once all steps above (including Step 6) have been successfully handled, notify the user that the Firebase Studio project export and Antigravity preparation are complete.

---

Examples

Example 1: User requests export Input: Can you help me finish this Firebase Studio export? Output:

• Invokes fbs-to-agy-export skill.
• Checks for .idx/ in current folder.
• Discovers .idx/ exists. Sets <TARGET_FOLDER> to ..
• Discovers next.config.ts. Sets <FBS_PROJECT_TYPE> to "NextJS".
• (Proceeds to Step 1...)

Example 2: Target folder unclear Input: Export to Antigravity. Output:

• Invokes fbs-to-agy-export skill.
• Checks for .idx/ in current folder. Not found.
• Asks user: "Please provide the absolute path to the project folder containing the .idx/ subdirectory."
• (Upon user answering with /Users/user/my-app) Sets <TARGET_FOLDER> to /Users/user/my-app.
• (Proceeds with prerequisites check...)