start-servers

Launches, restarts, and checks ASP.NET Core, Vite, and DevConsole development servers via PowerShell.

10|3|Updated Mar 7, 2026
One-click install
npx skills add https://github.com/Cynthia1070711/PHYCOOL_Tools --skill start-servers-cynthia1070711
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: start-servers
Source: https://github.com/Cynthia1070711/PHYCOOL_Tools/tree/main/config-templates/claude/skills/start-servers
Command: npx skills add https://github.com/Cynthia1070711/PHYCOOL_Tools --skill start-servers-cynthia1070711

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve? Managing multiple local development servers (an ASP.NET Core backend, a Vite frontend, and a dual-process DevConsole) manually is error-prone: ports get squatted by zombie processes, half-dead servers report as running, and HTTPS certificate reloads silently break the browser. This Skill automates starting, restarting, and health-checking all project dev servers with a single command. ## Core Features & Use Cases - Full or Selective Startup: Launch all servers at once or target individual ones (pcpt on 7135, vite on 5173, dvc on 5174 plus its API on 3001). - Restart and Status Checks: Kill port-occupying processes and restart cleanly, or run a check-only mode that reports PID, process name, and foreign port occupiers. - Zombie and Half-Dead Detection: Detects mismatched process names on ports and dual-process servers whose API port died while the UI port stayed alive, then recovers automatically. - Backend stdout Capture: Advanced mode tees ASP.NET Core stdout to timestamped log files for 4-layer pipeline diagnostics (Kestrel, middleware, controller, EF Core), feeding evidence into a systematic-debugging workflow. - Use Case: After running dotnet dev-certs https --clean && --trust, Chrome shows ERR_CERT_AUTHORITY_INVALID because Kestrel cached the old certificate; invoke the restart mode for pcpt to force a cert reload. ## Quick Start Ask the AI to start all development servers, or say "restart pcpt" to bounce only the ASP.NET Core backend after a certificate change.

Frequently Asked Questions about start-servers

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

FAQPage Schema
How do I start all local dev servers with one command?

Run the start-servers PowerShell script with no arguments to launch every configured server: the ASP.NET Core app on port 7135, Vite on 5173, and DevConsole on 5174. Each process starts hidden in the background with output redirected to per-server log files.

How to restart a single ASP.NET Core dev server on Windows?

Pass the server code with the restart flag, for example pcpt --restart. The script kills the process listening on port 7135, waits for the port to free, then relaunches dotnet run and verifies the port is listening again within 30 seconds.

Why does Chrome show ERR_CERT_AUTHORITY_INVALID after renewing dotnet dev-certs?

Kestrel caches the old HTTPS certificate in memory and does not reload it after dotnet dev-certs --clean and --trust. Restart the backend server so it loads the new certificate matching the CurrentUser\Root trust store.

Why does my dev server show running but the API returns connection refused?

Dual-process servers can enter a half-dead state where the UI port stays bound but the API process died. The script detects this by checking both ports, kills the surviving process, and performs a full restart of both processes independently.

Can I check which process is blocking a port before starting servers?

Yes, the --check mode reports each port's status with the owning PID and process name, and flags foreign occupiers that do not match the expected process. This identifies port squatters such as unrelated tools holding ephemeral sockets.

How do I capture ASP.NET Core stdout logs for debugging silent failures?

Pipe the script output through Tee-Object to write a timestamped log file while keeping console output visible. Combine this with Debug-level logging in appsettings.Development.json to trace requests across Kestrel, middleware, controllers, and EF Core.