@pixelvibing/cli 0.10.0 → 0.11.0

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@pixelvibing/cli",
-  "version": "0.10.0",
+  "version": "0.11.0",
   "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 HUD, skill and item icons, pieces laid out in a sketch) generated on the PixelVibing platform, listed and pulled into pixelvibing/out/, and sealed into the game's container. 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, level designs and interface art (a HUD, skill and item icons, pieces laid out in a sketch) 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.
 ---
 
 # PixelVibing art for this game
@@ -90,13 +90,21 @@ pixel-vibing-cli pull <id|name> [--as <name>] --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`…
-- **Pulling.** `pull` writes an asset of one picture as `pixelvibing/out/<name>.png`, and
-  one of several as `pixelvibing/out/<name>/<n>.png`; a HUD set's pieces as
-  `pixelvibing/out/ui/hud/<piece>.png`, an icon set's as `pixelvibing/out/ui/icon/<name>.png`
-  and a UI sketch's as `pixelvibing/out/ui/sketch/<label>.png`.
-  It downloads again only when the platform's copy changed.
-- **Collisions.** `pull` never writes over a picture it did not pull. When it refuses,
-  give the asset another name with `--as`.
+- **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>`; a HUD set's pieces as `ui/hud/<piece>`,
+  an icon set's as `ui/icon/<name>` and a UI sketch's as `ui/sketch/<label>`, each under
+  `pixelvibing/out/`. A level design or a HUD mockup 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
+  it refuses, give the asset another name with `--as`. A terrain set is landed from the
+  editor's Library, never from `pull`.
+- **The folder is the platform's.** `pixelvibing/` is written from the platform project and
+  never read back: change art in the editor, or by generating, not by editing its files.
+- **A folder with its own art.** A folder that kept a map or art before it was linked is
+  refused until it is moved: `pixel-vibing-cli move` sends it once to a platform project
+  holding nothing. Over a project that already has art, pass `--aside` to keep the folder's
+  own files under `pixelvibing/before-platform/`. Ask the person which before doing either.
 - **Using the art.** Use the pictures where they are, or copy them into the game's own
   asset folders. A copy is not tracked.
 
@@ -108,7 +116,9 @@ pixel-vibing-cli export <default|pixi|phaser|godot> [--out <dir>] --json
 
 - **What it makes.** Every picture under `pixelvibing/out/`, packed into sprite sheets,
   with the animations, and the map as placed sprites. It goes into
-  `pixelvibing/export/<engine>/`, or `--out`.
+  `pixelvibing/export/<engine>/`, or `--out`. It first brings the folder to the platform's
+  state, map and art, so it exports what the editor saved; `--offline` exports the folder
+  as it is.
 - **The formats.**
   - `pixi`: a TexturePacker JSON Hash spritesheet per sheet, for `Assets.load`.
   - `phaser`: a multi-atlas for `load.multiatlas`, and `animations.json` for
@@ -129,7 +139,8 @@ pixel-vibing-cli export <default|pixi|phaser|godot> [--out <dir>] --json
 ## Sealing
 
 `pixel-vibing-cli seal` builds `pixelvibing/build/assets.eac` from every picture under
-`pixelvibing/out/`, as the editor does, for a game that reads the container.
+`pixelvibing/out/`, as the editor does, for a game that reads the container. It brings the
+art from the platform first, unless `--offline`.
 
 ## By hand