Start UI

Start UI - Pre-Flight with Chrome

Purpose

Run the standard /start pre-flight, then verify Chrome DevTools tools are loaded and navigate to the frontend.

Principle

Do not create more nodes to avoid thinking.

Create nodes only when they reduce confusion.

Instructions

Step 1 - Run /start

Invoke the start skill to do the normal pre-flight (CodeGraph, branch check, tool loading).

Step 2 - Verify Chrome tools

Run ToolSearch to load Chrome DevTools tools:

ToolSearch: "+chrome-devtools screenshot"
ToolSearch: "+chrome-devtools navigate"

Then try mcp__chrome-devtools__list_pages to confirm the connection is live.

If Chrome tools are not available, tell the user:

"Chrome tools not available. Run claude mcp list to verify the chrome-devtools MCP server is registered."

Step 3 - Navigate to the frontend

Once Chrome is confirmed connected, navigate to the frontend app:

mcp__chrome-devtools__navigate_page(url: "http://localhost:3000")

Take a screenshot to confirm the app loaded and auth is active. If the page redirects to the login page instead of the app, tell the user:

"Frontend redirected to login. Please authenticate in the browser, then re-run /start-ui."

Step 4 - Output

Append to the /start output:

**Chrome:** ✅ Connected — navigated to localhost:3000 / ❌ Not available

Constraints

• DO NOT read project docs — /start already handles that.
• Keep output under 5 extra lines beyond /start.