local-dev-workflow

Generates start.sh scripts with port conflict management and dashboard output.

Updated Dec 13, 2025
One-click install
npx skills add https://github.com/imehr/vet --skill local-dev-workflow
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: local-dev-workflow
Source: https://github.com/imehr/vet/tree/main/.claude/skills/local-dev-workflow
Command: npx skills add https://github.com/imehr/vet --skill local-dev-workflow

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill standardizes the creation of a reliable local development startup script (start.sh) to ensure port isolation, deterministic re-runs, and a clear runtime dashboard, helping teams avoid common environment-start failures.

Core Features & Use Cases

  • Port sovereignty: assigns unique, non-conflicting ports per project to prevent clashes with other running apps.
  • Idempotent startup: the script can be re-run safely; it searches for and terminates processes occupying configured ports before launching.
  • Transparent dashboard: after startup, outputs running services, PIDs, and accessible URLs for quick verification.
  • One-Click startup: orchestrates Docker (when present), backend, frontend, and environment setup with a single script.
  • Template-driven: provides a canonical start.sh pattern and references a shared template in resources/start-script-template.md for adaptation.

Quick Start

Generate a start.sh that follows the Standard start.sh Template in resources/start-script-template.md, place it at your project root, make it executable, and run ./start.sh.

Frequently Asked Questions about local-dev-workflow

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

FAQPage Schema
How do I create an idempotent local development start script that handles port conflicts?

An idempotent local development start script prevents startup failures by including pre-flight checks and a kill_port cleanup function to terminate processes occupying configured ports before launching services.

What is port sovereignty and how does it prevent clashes in local development?

Port sovereignty assigns unique, non-conflicting ports per project to prevent clashes with other running apps. This is enforced within a portable start.sh structure that defines configurable ports.

How do I orchestrate Docker, backend, and frontend startup with a single script?

You can orchestrate Docker, backend, and frontend startup by generating a single start.sh script that manages environment setup and launches all components, outputting a transparent dashboard with running services and URLs.

Does the generated start.sh template work without Docker dependencies?

Yes, the generated start.sh template works without Docker dependencies by orchestrating Docker only when present, while still managing backend, frontend, and environment setup with configurable ports.

Why does my local development startup script fail when ports are already in use?

Local development startup scripts fail when ports are in use because of process conflicts. A robust start.sh script avoids this by enforcing port isolation and running pre-flight checks to kill processes on configured ports.