Image Workspace Setup

Register the folder the user treats as their image production workspace. Individual projects live as subfolders inside it.

Data store

${CLAUDE_USER_DATA:-${XDG_DATA_HOME:-$HOME/.local/share}/claude-plugins}/image-production/workspace.json

Do not write under ~/.claude/.

Procedure

1. Check for existing config

DATA_DIR="${CLAUDE_USER_DATA:-${XDG_DATA_HOME:-$HOME/.local/share}/claude-plugins}/image-production"
CONFIG="$DATA_DIR/workspace.json"
test -f "$CONFIG" && cat "$CONFIG"

If one exists, show the path and ask whether to keep or change it.

2. Ask the user

1. Existing or new? — do they already have an image workspace, or should one be created?
2. Path?
   • Existing: ask for absolute path; verify with test -d.
   • New: propose ~/media-workspaces/images as the default. Don't auto-create until the user confirms.

3. (New only) Version control

Ask whether to git init the workspace. Default no — image libraries can be large.

4. Create + persist

mkdir -p "$DATA_DIR"
mkdir -p "<chosen-path>"   # only if new

Write workspace.json:

{
  "path": "/absolute/path",
  "created": "<ISO-8601>",
  "version_controlled": false,
  "type": "image"
}

Use realpath to canonicalize.

5. Confirm

Print the registered path. Remind the user they can now say "open my image workspace" or "create a new image project".