@combos-fun/plugin-renderer-graphics 0.0.45 → 0.0.46

package/agent-skill.md

@@ -1,43 +1,18 @@
 # `@combos-fun/plugin-renderer-graphics` — Agent notes
 
-Vector / procedural shapes for the 2D pipeline. The Component exposes a Pixi `Graphics` API for free-form drawing on the GameObject's container.
-
-## When to read
-
-Read for any vector shape: lines, fills, custom geometry, circles / rectangles drawn on demand.
-
-## Public API
+Read only for procedural 2D vectors such as paths, circles, rectangles, fills, and strokes. Prefer `Img` or `Sprite` for bitmap art.
 
 ```ts
 import { Graphics, GraphicsSystem } from '@combos-fun/plugin-renderer-graphics';
 ```
 
-`componentName = 'Graphics'`, `systemName = 'Graphics'` (class is `GraphicsSystem` — use `game.getSystem(GraphicsSystem)`, not the string).
-
-The `Graphics` Component owns a `graphics` field — a Pixi `Graphics` instance created in `init()`. Use the standard Pixi v8 graphics API (`rect`, `circle`, `fill`, `stroke`, `moveTo`, `lineTo`, etc.) on it.
-
-## Required setup
+`Graphics.componentName = 'Graphics'`; `GraphicsSystem.systemName = 'Graphics'`.
 
-`RendererSystem` then `GraphicsSystem`.
-
-## Common pitfalls
-
-| Symptom | Fix |
-|---------|-----|
-| Nothing drawn | Call `comp.graphics.fill(...)` / `stroke(...)` after path commands; Pixi v8 requires explicit fill/stroke |
-| Drawing only first frame | Pixi `Graphics` is retained — calling `.clear()` then redrawing is needed for dynamic shapes |
-| Performance regression | For static shapes prefer `Img` or `Sprite`; `Graphics` is for dynamic vector content |
-
-## Minimal example
+`Graphics.graphics` is a Pixi v8 `Graphics` instance created during Component init and mounted at index 0 of the GameObject container.
 
 ```ts
-const go = new GameObject('rect', { position: { x: 100, y: 100 } });
-const g = go.addComponent(new Graphics());
-g.graphics.rect(0, 0, 200, 80).fill({ color: 0xff0000 });
+const graphics = go.addComponent(new Graphics()).graphics;
+graphics.rect(0, 0, 200, 80).fill({ color: 0xff0000 });
 ```
 
-(Note: keeping the `addComponent` return is for **demo purposes only**; inside real Components, use `gameObject.getComponent(Graphics)` from a lifecycle hook.)
-
-## Verification
-
-`pnpm --filter @combos-fun/plugin-renderer-graphics run build`.
+Path commands alone do not paint; finish with `fill(...)` or `stroke(...)`. Geometry is retained, so dynamic drawing should call `clear()` before rebuilding the shape. Removing the Component destroys its Graphics instance.

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@combos-fun/plugin-renderer-graphics",
-  "version": "0.0.45",
+  "version": "0.0.46",
   "description": "Vector / procedural shapes",
   "main": "index.js",
   "module": "dist/plugin-renderer-graphics.esm.js",
@@ -36,9 +36,9 @@
   ],
   "author": "sun668 <q947692259@gmail.com>",
   "dependencies": {
-    "@combos-fun/renderer-adapter": "0.0.45",
-    "@combos-fun/engine": "0.0.45",
-    "@combos-fun/plugin-renderer": "0.0.45"
+    "@combos-fun/renderer-adapter": "0.0.46",
+    "@combos-fun/plugin-renderer": "0.0.46",
+    "@combos-fun/engine": "0.0.46"
   },
   "scripts": {
     "build": "node ../../scripts/build-package.mjs"