What problem does it solve? Git worktrees isolate directories, but the PCHSystem development stack (postgres, backend, mc-test, Vite frontend) anchors its bind mounts, networks, and .env interpolation to the main repository path, causing port conflicts, token mismatches, and containers reading the wrong source code. This Skill provides decision tables and alignment checklists to run the stack correctly from a worktree. ## Core Features & Use Cases - Strategy Decision Table: Chooses among five migration strategies (override mounts, image rebuild, independent stack, frontend-only, MCDR sync) based on what the worktree changed. - Alignment Checklists: Covers port offsets, token/secret consistency (MCDR_SERVICE_TOKEN, POSTGRES_PASSWORD, JWT_SECRET), and Docker network naming so worktree and main stacks do not collide. - Red-Line Traps: Documents hard constraints such as docker cp writing back to main-repo bind mounts, MCDR reload only reading main-repo plugin paths, and never committing vite.config.ts port changes. - Use Case: You created a worktree to test a backend branch while main has uncommitted WIP; the Skill tells you to write a docker-compose.override.yml in the main repo pointing mounts at the worktree, then verify with docker inspect and curl /healthz. ## Quick Start Ask the assistant to start the PCHSystem backend stack from your current git worktree and align its ports and tokens with the main repository stack.
