ng:port-manager

Allocate non-overlapping 10-port blocks to projects via a JSON registry.

Updated Aug 23, 2026
One-click install
npx skills add https://github.com/huunghiaish/ng-skills --skill ng-port-manager
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: ng:port-manager
Source: https://github.com/huunghiaish/ng-skills/tree/main/ng-port-manager
Command: npx skills add https://github.com/huunghiaish/ng-skills --skill ng-port-manager

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Manage dev server port allocations across multiple projects to prevent conflicts and accidental cross-usage.

Core Features & Use Cases

  • Allocates a unique 10-port block per project starting at 20000.
  • Tracks port mappings for common services (Frontend, Backend, Database, Redis, Queue, Admin, WebSocket).
  • Provides commands to list, allocate, release, check, info, and env guidance to prepare environment files.

Quick Start

Run ng:port-manager allocate in your project directory to reserve ports for all services.

Frequently Asked Questions about ng:port-manager

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

FAQPage Schema
How do I prevent dev server port conflicts when running multiple projects concurrently?

To prevent dev server port conflicts, you can allocate non-overlapping port blocks to each project. ThisSkill uses a JSON registry to reserve a unique 10-port block per project starting at 20000, ensuring isolated ports for concurrent services.

What is the best way to automate port allocation for multi-project dev environments?

Automating port allocation for multi-project environments uses a script-based registry to assign and track ports. The system applies an atomic write pattern to a JSON registry file, safely managing port blocks for automation workflows without race conditions.

How do I check which ports are already allocated to my development services?

You can check allocated ports by running the check or list commands provided by the port manager. It reads the JSON registry at ~/.claude/port-registry.json to display current port mappings for services like Frontend, Backend, Database, Redis, Queue, Admin, and WebSocket.

Can I release or reallocate ports for a project after I am done with it?

Yes, you can release allocated ports using the release command, which updates the JSON registry. This frees up the 10-port block previously assigned to that project, preventing port blocking and allowing reallocation for other projects.

How do I prepare environment variables for the ports assigned to my services?

You prepare environment variables by using the env command, which generates guidance for your allocated ports. This maps the reserved port blocks for services like Frontend, Backend, Database, and Redis into environment file configurations.

When do I need a dedicated port registry for my development setup?

You need a dedicated port registry when multiple services must run concurrently across different projects. It prevents accidental cross-usage and conflicts by tracking allocated port blocks in a central JSON file, ensuring no two projects claim the same port.