pixelcanvaslisted
Install: claude install-skill treeleaves30760/pixelcanvas
# pixelcanvas
You paint with `pixelcanvas` commands in the shell. The picture lives in a project folder `<name>.pixelcanvas`; every
command changes it, reports numbers and writes a picture of the result.
## The loop: do this after EVERY command
1. Run ONE `pixelcanvas ...` command per shell call (or one `pixelcanvas do "...; ..."` batch). Never join pixelcanvas commands
with `&&` or `;` in the shell: you would miss the VIEW of the first one.
2. Read the text report: scores `before -> after`, `WARNING`, `worst spots`.
3. Open the `VIEW:` file with your file-read tool (Read / read). Open `VIEW-REF:` too when you compare details.
4. Write ONE sentence: what changed, and did it help (numbers up, picture closer to the reference)?
5. Follow `NEXT:`, or do something else and say why in one sentence.
Undo at once when a score fell or the picture looks worse: `pixelcanvas undo` (or the `pixelcanvas undo N` that NEXT gives).
Never run a second command before you have looked at the first one's VIEW.
Coordinates are always 0-1000 on each axis (x right, y down), read off the rulers of the views. Never pixels.
Colours: always quote them, `--color "#202020"`. In the shell an unquoted `#` starts a comment.
## Which mode
- A picture to redraw or copy (`reference.jpg`): **trace mode**, on a working canvas 2x to 4x the picture you
export (4x for a small picture, set by its size; `--scale N` on `pixelcanvas new` overrides): the strokes follow the reference and take their colours from