Forge

Add a real-browser Playwright test under /e2e for a cross-system feature (rendering, input, camera, animation, physics - anything that only truly proves itself on a real WebGL2 canvas with real DOM input events). Covers when a new feature needs e2e coverage, and the standard for asserting on actual rendered pixels tied back to logic state, not just numeric ECS assertions. Use when writing a new feature that touches rendering, input, or the game loop, or when explicitly asked to add an e2e/integration test.

Create a new ECS component for the Forge engine, a plain data interface plus a createComponentId key, wired into its module's exports. Use when asked to add a new component (e.g. "add a component for X", "create a health component").

Write or update a conceptual guide page in documentation-site/docs/docs for a new or changed Forge feature, focused on practical usage (common use cases, gotchas, performance notes, code smells to avoid) rather than restating the API surface. Also makes sure the public API has JSDoc for the auto-generated API reference. Use when a component, system, class, or module has been added or changed and needs user-facing documentation.