dev-setuplisted

# /dev-setup User request: "$ARGUMENTS" ## Task Detect the project's structure, propose a dev environment configuration, and generate bash scripts for managing servers, Chrome profiles, and worktree port isolation. ## Process ### Step 0: Ensure dependencies Resolve plugin path: ```bash SKILL_DIR="$(find "$HOME/.claude/plugins/cache" -type d -name "dev-setup" -path "*/skills/dev-setup" 2>/dev/null | head -1)" [[ -z "$SKILL_DIR" ]] && SKILL_DIR="$(find "$HOME" -maxdepth 8 -type d -name "dev-setup" -path "*/skills/dev-setup" 2>/dev/null | head -1)" ``` ```bash bash "$SKILL_DIR/scripts/ensure-deps.sh" ``` If the script exits with an error, show the missing dependency message to the user and stop. Warnings about optional tools can be shown but should not block execution. ### Route: upgrade If `$ARGUMENTS` starts with "upgrade": 1. **Resolve plugin path** — find the `reference/` directory: ```bash SKILL_DIR="$(find "$HOME/.claude/plugins/cache" -type d -name "dev-setup" -path "*/skills/dev-setup" 2>/dev/null | head -1)" [[ -z "$SKILL_DIR" ]] && SKILL_DIR="$(find "$HOME" -maxdepth 8 -type d -name "dev-setup" -path "*/skills/dev-setup" 2>/dev/null | head -1)" echo "SKILL_DIR=$SKILL_DIR" ``` 2. **Find project script dir:** - Parse `package.json` for a `dev:start` script → extract the path → `dirname` - Example: `"dev:start": "bash tools/dev/dev-start.sh"` → `SCRIPT_DIR=tools/dev` - Fallback: `tools/dev/` - If `SCRIPT_DIR` doesn't exist: stop wi