Browser-based HTML5 game editor and runtime: PixiJS 2D, Three.js 3D, React UI, and a TypeScript engine for multiple games
Skill Claude CodeCodexCursor
Add a new supported asset format/type through catalogue schema, importer or editor workflow, project-server, Asset Browser, preview, Inspector picker, resolver, runtime load, and tests. Use when introducing a new AssetType, importer, generated artifact, or when import works but editor/runtime cannot resolve the file.
Skill Claude CodeCodexCursor
Add an undoable editor command for scene, asset, prefab, or tilemap mutations. Use when implementing create/delete/rename/move/property edits, continuous gestures that must commit one history entry, or when UI currently mutates DocumentManager without CommandManager.
Skill Claude CodeCodexCursor
Add a dockable editor panel (Dockview id, React view, default layout, persisted layout version, subscriptions, cleanup). Use when adding panels such as Animation, Profiler, Tilemap tools, Physics debugger, Audio mixer, or Prefab overrides as a new dock region — not Inspector sections.
Skill Claude CodeCodexCursor
Add a new scene node type end-to-end (domain component, Zod schema, factory, editor registry, Inspector, Pixi/Three renderer, clone/undo, tests). Use when adding a creatable Hierarchy/Node-menu type, visual or Three leaf, Hit Zone / Mask-like extra, or when schema is added but renderer/editor support is missing.
Skill Claude CodeCodexCursor
Plan and land architectural or cross-package changes (dependency direction, scene/domain schema, runtime/editor boundaries, persistence format, renderer abstractions, project-server APIs). Use when changing multiple packages, serialized formats, or package boundaries — not for localized UI, styling, or test-only edits.
Skill Claude CodeCodexCursor
Create game Script components (defineComponent + OOP behaviour class) for games/ /src/components or packages/game-components. Use when adding a game component, script component, behaviour, Loading/Change Scene logic, bus event handlers, or Inspector Add Component entries.
Skill Claude CodeCodexCursor
Scaffold a new independently buildable game under games/ (package.json, project.json, Vite, scenes, runtime boot). Use when adding a new game, game package, games/ project, Pixi-only / Three-only / hybrid game, or copying editor-features-demo / solitaire / muonline-game.
Skill Claude CodeCodexCursor
Plan and implement a production-quality feature in the hybrid PixiJS/Three.js game editor while preserving architecture, undo/redo, persistence and tests. Use for editor UI/core work that is not a specialized add-node-type, add-asset-type, add-editor-command, add-editor-panel, or modify-scene-schema slice.
Skill Claude CodeCodexCursor
Implement gameplay/runtime features (GameRuntime services, input, audio, timers, scene transitions, script lifecycle, shared game systems) without importing editor UI. Use when changing runtime packages or games/ behaviour that is not a new Script component and not editor chrome.
Skill Claude CodeCodexCursor
Safely change persisted scene, prefab, project, asset, or tileset JSON (Zod, TypeScript, defaults, loaders, backward compatibility, tests). Use when adding/removing/renaming serialized fields, bumping format versions, or loading old games//assets JSON would otherwise break.
Skill Claude CodeCodexCursor
Measure and fix editor or runtime performance regressions (per-frame work, Pixi/Three loops, React rerenders, scene rebuilds, allocations). Use when investigating jank, GC pressure, high draw calls, or before optimizing hot paths — not for speculative micro-edits.
Skill Claude CodeCodexCursor
Update repository documentation so it matches the implementation (README, PROJECT.md, docs/ topic pages, hotkeys, feature tables). Use after a user-visible or architectural change when existing docs would be wrong or incomplete — not to rewrite roadmap or add churn.
At most 3 mods per repository are shown here, and a mod shipped inside a plugin is left to that plugin's page — the rest are on their repository pages: