ops-port-manager

Name: ops-port-manager
Availability: InStock
Author: endlessblink

Enforce port 5546 for FlowState and terminate conflicting processes.

Updated Nov 29, 2025

Search Tags:#diagnostics #server-health #dev-ops #port-management #development-server #port-5546

Ready to run

npx skills add https://github.com/endlessblink/flow-state --skill ops-port-manager

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: ops-port-manager
Source: https://github.com/endlessblink/flow-state/tree/main/.claude/skills/%F0%9F%94%8C%20ops-port-manager
Command: npx skills add https://github.com/endlessblink/flow-state --skill ops-port-manager

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Enforce a single development port (5546) for FlowState and provide quick commands to resolve port conflicts, ensuring local server startups are reliable.

Core Features & Use Cases

Enforces 5546 as the default development port for the main app (and 6006 for Storybook) to prevent cross-project port clashes.
Provides port-conflict diagnostics, process-kill routines, and restart steps to restore dev environments quickly.
Includes health checks and consistent URL references to validate that the development server is reachable after remediation.

Quick Start

Start the development server with npm run dev and verify the app is accessible at http://localhost:5546.

Frequently Asked Questions about ops-port-manager

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

FAQPage Schema

How do I resolve port conflicts when my development server fails to start?▼

To resolve port conflicts and startup failures, this Skill enforces the 5546 dev port for FlowState and terminates conflicting processes, restoring your local server environment quickly.

Why does my local development server or Storybook run fail during automated tests?▼

Local development servers fail during automated tests due to port contention. This Skill locks port 5546 for the main app and 6006 for Storybook, preventing cross-project port clashes.

How do I run health checks to verify my dev server is reachable after a port conflict?▼

You can run health checks and use consistent URL references to validate that the development server is reachable after remediation. Verify the app is accessible at http://localhost:5546.

What's the best way to lock a specific port for npm run dev to prevent contention?▼

The best way to lock a specific port is to enforce 5546 as the default development port. This provides port-conflict diagnostics, process-kill routines, and restart steps to ensure reliable startup.

Does this port management approach work for Storybook runs and local development environments?▼

Yes, this port management approach works for local development, automated tests, and Storybook runs. It enforces separate default ports, 5546 for the main app and 6006 for Storybook, to prevent clashes.