open

Open the React frontend in the default browser using VITE_PORT from .env.

1|Updated Jan 20, 2026
One-click install
npx skills add https://github.com/coopermayne/mcp-galipo --skill open-coopermayne
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: open
Source: https://github.com/coopermayne/mcp-galipo/tree/main/.claude/skills/open
Command: npx skills add https://github.com/coopermayne/mcp-galipo --skill open-coopermayne

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Open the frontend in the default browser using the port configured in the project environment.

Core Features & Use Cases

  • Open the frontend URL in the default browser using the configured port.
  • Works with VITE_PORT (default 5173) to simplify local development previews.
  • Use Case: developers quickly verify the app is serving on the expected port after startup.

Quick Start

Open the frontend in your browser using the port defined in the .env file (defaults to 5173).

Frequently Asked Questions about open

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I open my frontend in the browser using a custom VITE_PORT?

To open your frontend in the browser, the system reads the VITE_PORT from your .env file and launches the default browser. It defaults to port 5173 if VITE_PORT is not specified.

What is the default port used to open a Vite frontend application?

The default port to open a Vite frontend application is 5173. This is used automatically when the VITE_PORT environment variable is not defined in your .env file.

How to quickly preview a local React app in the default browser after startup?

Quickly preview a local React app by triggering the system's default open mechanism. It reads the configured VITE_PORT to launch the exact development URL in your default browser.

Does the browser open command require a specific .env file configuration?

The browser open command does not strictly require a .env file configuration. It looks for VITE_PORT in the .env file, but automatically falls back to port 5173 if the file or variable is missing.

Can I use this to open a frontend for QA workflows on a different port?

Yes, you can use this for QA workflows on a different port. Simply set the desired port number as the VITE_PORT variable in your .env file, and the browser will open that specific URL.