@pixelvibing/cli 0.48.0 → 0.49.1

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@pixelvibing/cli",
-  "version": "0.48.0",
+  "version": "0.49.1",
   "description": "PixelVibing: pixel art game assets from the command line, and the Skills that teach coding assistants to make them.",
   "license": "MIT",
   "homepage": "https://pixelvibing.com",

package/skills/pixelvibing/SKILL.md

@@ -1,6 +1,6 @@
 ---
 name: pixelvibing
-description: Make pixel art for this game with pixel-vibing-cli — objects, creatures, level designs and interface art (a UI laid out as JSON, skill and item icons) generated on the PixelVibing platform, listed, pulled into the project's art and its folder, and exported or sealed for the game. Use when the game needs a sprite, a prop, a creature, a level's art, its HUD or its icons, or art already made for it.
+description: Make pixel art for this game with pixel-vibing-cli — objects, creatures, concept art and interface art (a UI laid out as JSON, skill and item icons) generated on the PixelVibing platform, listed, pulled into the project's art and its folder, and exported or sealed for the game. Use when the game needs a sprite, a prop, a creature, concept art to draw from, a level's art, its HUD or its icons, or art already made for it.
 ---
 
 # PixelVibing art for this game
@@ -31,7 +31,8 @@ Progress and errors go to standard error, and a failure exits 1.
 ```bash
 pixel-vibing-cli generate object --instruction "<what>" --size <cols>x<rows> --yes --json
 pixel-vibing-cli generate creature --instruction "<what>" [--reference <png>]... --yes --json
-pixel-vibing-cli generate level-design --instruction "<what>" --tiles <cols>x<rows> --yes --json
+pixel-vibing-cli generate concept-art --instruction "<what>" [--size <w>x<h>] [--transparent] [--tag <tag>]... --yes --json
+pixel-vibing-cli generate concept-art --instruction "<what>" --pixel-art --tiles <cols>x<rows> --yes --json
 pixel-vibing-cli generate icons --names "<name>,<name>,..." --purpose <skill|item> [--size <16|32|64>] --yes --json
 pixel-vibing-cli generate ui --sketch <file.json> --instruction "<the set, in a line>" --yes --json
 ```
@@ -44,12 +45,23 @@ Each generation uses part of the account's usage limit for the month.
   it is for in the game. Describe the thing itself, not a prompt for a model.
 - **The options.**
   - `--size` is an object's footprint in whole tiles, `1x1` unless given.
-  - `--tiles` is how many tiles a level design is across, `6x4` unless given.
+  - `--tiles` is how many tiles a pixel-art concept art is across, `6x4` unless given.
   - No quality is given: the platform draws each asset at the quality it needs. The share
     printed is the most it may use, and what it does not use is given back.
-  - `--reference` is a PNG to draw from, repeated for several: at most 8 for an object,
-    3 for a creature, a level design or a UI, none for icons. A UI's references are a style
+  - `--reference` is a PNG to draw from, repeated for several: at most 8 for an object
+    or a concept art, 3 for a creature or a UI, none for icons. A UI's references are a style
     to follow (frames, materials, a way of drawing), never what to draw.
+- **Concept art.** The free kind: reference art, a place, a character sheet, a sample menu —
+  whatever the instruction asks. It is drawn as ordinary art, not pixel art, to draw the
+  rest from: make one first, tagged `anchor`, and pass its pulled picture
+  (`pixelvibing/ref/<name>.png`) as `--reference` to what follows.
+  - `--size` is its size in px, `<w>x<h>`, multiples of 16 within `1536x1024` or
+    `1024x1536`, `1536x1024` unless given. `--transparent` cuts its background away, for
+    one thing alone.
+  - `--pixel-art` draws it as a level design instead: pixel art of an area some `--tiles`
+    across, which the editor takes apart into objects and terrain.
+  - `--tag` says what it is for, repeated for several, at most 8: `anchor`, `level-design`,
+    `ui`, `character`, `environment`, `prop`, or one of the project's own.
 - **Interface art.** When the game shows the player something over the world, make it here
   rather than drawing it in code:
   - `icons` makes up to 16 icons that match, from `--names`: `--purpose skill` for a
@@ -74,17 +86,21 @@ Each generation uses part of the account's usage limit for the month.
 ## Listing and pulling
 
 ```bash
-pixel-vibing-cli list [<kind>] --json
+pixel-vibing-cli list [<kind>] [--tag <tag>] --json
 pixel-vibing-cli pull <id|name> [--as <name>] --json
+pixel-vibing-cli tag <id|name> [<tag>...] [--none] --json
 ```
 
 - **Listing.** `list` answers the newest 50 assets. When there are more, it gives a
   `next` id for `--before`. A kind is the generation that made the asset: `object`,
-  `creature`, `level-design`, `rotate`, `animate`…
+  `creature`, `concept-art`, `rotate`, `animate`… `--tag` lists only the concept art
+  carrying that tag, such as `anchor`.
+- **Tags.** `tag` sets a concept art's tags, replacing the ones it had; with none given
+  it shows them and the project's tags, and `--none` takes them all off.
 - **Pulling.** `pull` adds the asset to the project's art on the platform, where the editor
   sees it too, and then writes the folder from the platform. An asset of one picture
   lands as `<name>`, one of several as `<name>/<n>`; an icon set's pieces as `ui/icon/<name>`
-  and a UI's as `ui/sketch/<label>`, each under `pixelvibing/out/`. A level design is kept
+  and a UI's as `ui/sketch/<label>`, each under `pixelvibing/out/`. A concept art is kept
   as a reference, under
   `pixelvibing/ref/`. Pulling again lands nothing while the art still holds it.
 - **Collisions.** `pull` lands nothing under a name the art holds for something else. When