chrome

Start a Next.js development server and open Google Chrome to a specified path.

Updated May 16, 2026
One-click install
npx skills add https://github.com/aryaxt/aryaxt-skills --skill chrome-aryaxt
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: chrome
Source: https://github.com/aryaxt/aryaxt-skills/tree/main/skills/chrome
Command: npx skills add https://github.com/aryaxt/aryaxt-skills --skill chrome-aryaxt

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve?

This Skill solves the problem of quickly and easily testing your web application in Google Chrome without manually setting up the development server.

Core Features & Use Cases

  • Automates Server Setup: Boots the local Next.js dev server or reuses a running one.
  • Environment Configuration: Handles worktree environment quirks.
  • Error Handling: Checks for hung Next.js dev servers and handles them appropriately.
  • Chrome Opening: Opens the application in Google Chrome for testing.
  • Use Case: If you're developing a Next.js application and want to quickly see your changes in the browser, you can use this Skill with a simple command.

Quick Start

Use the /chrome command to test your app in Chrome. For example, to open the dashboard, type /chrome /dashboard.

Frequently Asked Questions about chrome

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

FAQPage Schema
How do I automatically open my Next.js development server in Chrome?

You can automatically open your Next.js development server in Chrome by running a single command. This tool boots the local Next.js dev server or reuses an existing one and opens Google Chrome to your specified path.

What is the best way to test a Next.js web application in the browser without manual server setup?

The best way to test a Next.js web application without manual server setup is to use an automated command that handles server initialization. It boots the dev server, checks for hung processes, and opens Google Chrome directly to your application path.

Does this Chrome testing tool work if a Next.js dev server is already running?

Yes, this Chrome testing tool works if a Next.js dev server is already running. It detects the existing development server and reuses it, opening Google Chrome to the specified path without starting a duplicate instance.

How do I specify which page or route to open when testing my Next.js app in Chrome?

You can specify which page or route to open by passing the path as an argument to the command. For example, typing the command followed by /dashboard opens your Next.js application directly in Google Chrome at that specific route.

Why does my Next.js development server hang and how is it handled during Chrome testing?

Next.js development servers can hang due to environment configuration quirks or process errors. This testing tool checks for hung Next.js dev servers, handles them appropriately, and resolves environment issues before opening Google Chrome.