vesper-dev-instance-manager

Launch and manage isolated Vesper dev instances across git worktrees.

1|Updated Jan 26, 2026
One-click install
npx skills add https://github.com/AskTinNguyen/vesper-team-skills --skill vesper-dev-instance-manager
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: vesper-dev-instance-manager
Source: https://github.com/AskTinNguyen/vesper-team-skills/tree/main/vesper-dev-instance-manager
Command: npx skills add https://github.com/AskTinNguyen/vesper-team-skills --skill vesper-dev-instance-manager

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires bun, and includes scripts (resource) components.

What problem does it solve?

This skill orchestrates the creation and operation of isolated Vesper development instances across multiple git worktrees to protect production workspaces and enable safe feature testing.

Core Features & Use Cases

  • Per-instance isolation with dedicated config, workspaces, and data directories.
  • Lifecycle management: build, launch, status, and stop commands.
  • Marker-based isolation: uses environment variables to keep instances separate and prevent cross-talk.
  • Works across macOS and other platforms with per-instance isolation and robust guardrails.

Quick Start

Run the manage-dev-instance.sh script with --instance-number 2 in your target worktree to start a new isolated dev instance.

Frequently Asked Questions about vesper-dev-instance-manager

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

FAQPage Schema
How do I isolate Electron dev instances across git worktrees to prevent production interference?

To isolate Electron dev instances across git worktrees, you use a Bash script-driven lifecycle that applies marker-based configuration via environment variables, keeping per-instance workspaces, config, and data directories separate to prevent cross-talk.

Why does my Vesper dev instance cross-talk with my production workspace?

Dev instances cross-talk with production workspaces when they lack marker-based isolation via environment variables. Applying per-worktree workspace directories and isolated configuration prevents this interference.

Can I manage multiple side-by-side dev apps with per-instance configuration on macOS?

Yes, you can manage multiple side-by-side dev apps with per-instance configuration on macOS. The lifecycle controls support build, launch, status, and stop commands across worktrees with robust guardrails.

What's the best way to manage the lifecycle of isolated dev instances in a multi-worktree environment?

The best way to manage the lifecycle of isolated dev instances is using the provided Bash script to execute build, launch, status, and stop commands, which tracks per-instance state and prevents cross-talk.

When should I not use git worktrees for isolating dev instances?

You should not use git worktrees for isolating dev instances if your project lacks support for marker-based environment variable configuration or if your workflow does not require side-by-side feature testing across multiple worktrees.