Rejected

Grep here before proposing a new vue-phaserjs component or composable. The recurring theme: if a Phaser primitive has no visual component hierarchy or is app-specific, it stays an imperative call on the object received from @complete rather than becoming a library abstraction.

• Group component — Group isn't a GameObject; v-for covers grouping
• Camera tween helpers — no call site needs them
• Multiple cameras — one-time imperative setup via @complete
• Tilemap layer components — layer creation order is imperative
• Tween component — redundant with useTween
• useTimeline — scene.tweens.chain() suffices
• useSound — service functions own sound
• Input polling composables — per-frame reactivity overhead
• useDrag — events already exposed
• useSceneData — Pinia stores own scene data
• useArcadePhysics — no use case yet
• Scene transition effects — app-specific