Use this skill when the task is specifically about the local pixr CLI in this repository or its home-directory defaults under ~/.pixr.
Typical triggers:
Do not use this skill for general Gemini API design discussions that are not tied to this CLI.
Prefer the installed binary when available:
pixrIf you are working inside this repo and do not want to depend on a global link, use:
npm run dev -- npm run pixr -- Use pixr help for global help or pixr for command help.
Run pixr config --json.
pixr profile listpixr profile show pixr profile init pixr config --profile --json pixr model ...pixr save-dir ...~/.pixr/INSTRUCTION.md~/.pixr/STYLE.md~/.pixr/prompts/.md ~/.nano-image/STYLE.md~/.pixr/assets or ~/.pixr/profiles//assets and verify with pixr refs --json.Remember that pixr keeps only the latest three default asset images by modified time.
For generation details and command recipes, read references/command-reference.md.
Key rules:
generate or gen for prompt-only creation.edit for text-guided changes to an existing image.vary for one or more Gemini-generated variations of an existing image.~/.pixr/config.json.--save-to or --output, that overrides the saved default output directory.png; jpg, jpeg, and webp are supported through local conversion.For persistent settings and file layout, read references/defaults-and-files.md.
Prefer command-driven config changes:
pixr model pixr modelspixr save-dir --set "" pixr save-dir --clear-save-dirpixr profile init --model ... --save-dir ... pixr profile init Avoid editing ~/.pixr/config.json directly unless the user explicitly asks for a manual file edit.
Read references/troubleshooting.md when:
After making changes or guiding usage:
--json when you need machine-readable confirmation共 1 个版本