From image-production
Register or create the user's image production workspace — a folder on disk where they keep image projects. Use on first run, or when the user says "set up my image workspace", "register my image workspace", "change my image workspace path", or similar. Persists the path so other skills (open-workspace, new-project) can reference it.
npx claudepluginhub danielrosehill/claude-code-plugins --plugin image-productionThis skill is limited to using the following tools:
Register the folder the user treats as their image production workspace. Individual projects live as subfolders inside it.
Guides Next.js Cache Components and Partial Prerendering (PPR): 'use cache' directives, cacheLife(), cacheTag(), revalidateTag() for caching, invalidation, static/dynamic optimization. Auto-activates on cacheComponents: true.
Guides building MCP servers enabling LLMs to interact with external services via tools. Covers best practices, TypeScript/Node (MCP SDK), Python (FastMCP).
Share bugs, ideas, or general feedback.
Register the folder the user treats as their image production workspace. Individual projects live as subfolders inside it.
${CLAUDE_USER_DATA:-${XDG_DATA_HOME:-$HOME/.local/share}/claude-plugins}/image-production/workspace.json
Do not write under ~/.claude/.
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.
test -d.~/media-workspaces/images as the default. Don't auto-create until the user confirms.Ask whether to git init the workspace. Default no — image libraries can be large.
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.
Print the registered path. Remind the user they can now say "open my image workspace" or "create a new image project".