iOS Games Router
You MUST use this skill for ANY game development, SpriteKit, SceneKit, RealityKit, or interactive simulation work.
When to Use
Use this router when:
- Building a new SpriteKit game or prototype (2D)
- Building a 3D game with SceneKit or RealityKit
- Implementing physics (collisions, contacts, forces, joints)
- Setting up game architecture (scenes, layers, cameras, ECS)
- Debugging SpriteKit, SceneKit, or RealityKit issues
- Optimizing game performance (draw calls, node counts, entity counts, batching)
- Managing game loop, delta time, or pause handling
- Implementing touch/input handling in a game context
- Integrating SpriteKit or RealityKit with SwiftUI
- Working with particle effects, texture atlases, or 3D models
- Looking up SpriteKit, SceneKit, or RealityKit API details
- Migrating from SceneKit to RealityKit
- Building AR games with RealityKit
Routing Logic
SpriteKit (2D)
Architecture, patterns, and best practices → $axiom-spritekit
- Scene graph model, coordinate systems, anchor points
- Physics engine: bitmask discipline, contact detection, body types
- Actions system: sequencing, grouping, named actions, timing
- Input handling: touches, coordinate conversion
- Performance: draw calls, batching, object pooling, SKShapeNode trap
- Game loop: frame cycle, delta time, pause handling
- Scene transitions and data passing
- SwiftUI integration (SpriteView, UIViewRepresentable)
- Metal integration (SKRenderer)
- Anti-patterns and code review checklist
- Pressure scenarios with push-back templates
API reference and lookup → $axiom-spritekit-ref
- All 16 node types with properties and performance notes
- SKPhysicsBody creation methods and properties
- Complete SKAction catalog (movement, rotation, scaling, fading, composition, physics)
- Texture and atlas management
- SKConstraint types and SKRange
- SKView configuration and scale modes
- SKEmitterNode properties and presets
- SKRenderer setup and SKShader syntax
Troubleshooting and diagnostics → $axiom-spritekit-diag
- Physics contacts not firing (6-branch decision tree)
- Objects tunneling through walls (5-branch)
- Poor frame rate (4 top branches, 12 leaves)
- Touches not registering (6-branch)
- Memory spikes and crashes (5-branch)
- Coordinate confusion (5-branch)
- Scene transition crashes (5-branch)
Automated scanning → Launch spritekit-auditor agent or /axiom:audit spritekit (physics bitmasks, draw call waste, node accumulation, action memory leaks, coordinate confusion, touch handling, missing object pooling, missing debug overlays)
SceneKit (3D — Deprecated)
SceneKit is soft-deprecated as of iOS 26. Use for maintenance of existing code only. New 3D projects should use RealityKit.
Maintenance and migration planning → $axiom-scenekit
- Scene graph architecture, coordinate system, transforms
- Rendering: SCNView, SceneView (deprecated), SCNViewRepresentable
- Geometry, PBR materials, shader modifiers
- Lighting, animation (SCNAction, SCNTransaction, CAAnimation bridge)
- Physics: bodies, collision categories, contact delegate
- Asset pipeline: Model I/O, USD/DAE/SCN formats
- ARKit integration (legacy ARSCNView)
- Migration decision tree (when to migrate vs maintain)
- Anti-patterns and pressure scenarios
API reference and migration mapping → $axiom-scenekit-ref
- Complete SceneKit → RealityKit concept mapping table
- Scene graph API: SCNScene, SCNNode, SCNGeometry
- Materials: lighting models, PBR properties, shader modifiers
- Lighting: all light types with properties
- Camera: SCNCamera properties
- Physics: body types, shapes, joints
- Animation: SCNAction catalog, timing functions
- Constraints: all constraint types
RealityKit (3D — Modern)
For non-game 3D content display (product viewers, AR try-on, spatial computing), the ios-graphics router also routes to these RealityKit skills.
Architecture, ECS, and best practices → $axiom-realitykit
- Entity-Component-System mental model and paradigm shift
- Entity hierarchy, transforms, world-space queries
- Built-in and custom components, component lifecycle
- System protocol, update ordering, event handling
- SwiftUI integration: RealityView, Model3D, attachments
- AR on iOS: AnchorEntity types, SpatialTrackingSession
- Interaction: ManipulationComponent, gestures, hit testing
- Materials: SimpleMaterial, PBR, Unlit, Occlusion, ShaderGraph, Custom
- Physics: collision shapes, groups/filters, events, forces
- Animation: transform, USD playback, playback control
- Audio: spatial, ambient, channel
- Performance: instancing, component churn, shape optimization
- Multiplayer: synchronization, ownership
- Anti-patterns and code review checklist
- Pressure scenarios
API reference and lookup → $axiom-realitykit-ref
- Entity API: properties, hierarchy, subclasses
- Complete component catalog with all properties
- MeshResource generators
- ShapeResource types and performance
- System protocol and EntityQuery
- Scene events catalog
- RealityView API: initializers, content, gestures
- Model3D API
- Material system: all types with full property listings
- Animation timing functions and playback control
- Audio components and playback
- RealityRenderer (Metal integration)
Troubleshooting and diagnostics → $axiom-realitykit-diag
- Entity not visible (8-branch decision tree)
- Anchor not tracking (6-branch)
- Gesture not responding (6-branch)
- Performance problems (7-branch)
- Material looks wrong (6-branch)
- Physics not working (6-branch)
- Multiplayer sync issues (5-branch)
Decision Tree
- Building/designing a 2D SpriteKit game? → axiom-spritekit
- How to use a specific SpriteKit API? → axiom-spritekit-ref
- SpriteKit broken or performing badly? → axiom-spritekit-diag
- Maintaining existing SceneKit code? → axiom-scenekit
- SceneKit API reference or migration mapping? → axiom-scenekit-ref
- Building new 3D game or experience? → axiom-realitykit
- How to use a specific RealityKit API? → axiom-realitykit-ref
- RealityKit entity not visible, gestures broken, performance? → axiom-realitykit-diag
- Migrating SceneKit to RealityKit? → axiom-scenekit (migration tree) + axiom-scenekit-ref (mapping table)
- Building AR game? → axiom-realitykit
- Physics contacts not working (SpriteKit)? → axiom-spritekit-diag (Symptom 1)
- Frame rate dropping (SpriteKit)? → axiom-spritekit-diag (Symptom 3)
- Coordinate/position confusion (SpriteKit)? → axiom-spritekit-diag (Symptom 6)
- Need the complete action list? → axiom-spritekit-ref (Part 3)
- Physics body setup reference? → axiom-spritekit-ref (Part 2)
- Entity not visible (RealityKit)? → axiom-realitykit-diag (Symptom 1)
- Gesture not responding (RealityKit)? → axiom-realitykit-diag (Symptom 3)
- Want automated SpriteKit code scan? → spritekit-auditor (Agent)
Anti-Rationalization
| Thought |
Reality |
| "SpriteKit is simple, I don't need a skill" |
Physics bitmasks default to 0xFFFFFFFF and cause phantom collisions. The bitmask checklist catches this in 2 min. |
| "I'll just use SKShapeNode, it's quick" |
Each SKShapeNode is a separate draw call. 50 of them = 50 draw calls. axiom-spritekit has the pre-render-to-texture pattern. |
| "I can figure out the coordinate system" |
SpriteKit uses bottom-left origin (opposite of UIKit). Anchor points add another layer. axiom-spritekit-diag Symptom 6 resolves in 5 min. |
| "Physics is straightforward" |
Three different bitmask properties, modification rules inside callbacks, and tunneling edge cases. axiom-spritekit Section 3 covers all gotchas. |
| "The performance is fine on my device" |
Performance varies dramatically across devices. axiom-spritekit Section 6 has the debug overlay checklist. |
| "SceneKit is fine for our new project" |
SceneKit is soft-deprecated iOS 26. No new features, only security patches. axiom-scenekit has the migration decision tree. |
| "I'll learn RealityKit later" |
Every line of SceneKit is migration debt. axiom-scenekit-ref has the concept mapping table so the transition is concrete, not abstract. |
| "ECS is overkill for a simple 3D app" |
You're already using ECS — Entity + ModelComponent. axiom-realitykit shows how to scale from simple to complex. |
| "I don't need collision shapes for taps" |
RealityKit gestures require CollisionComponent. axiom-realitykit-diag diagnoses this in 2 min vs 30 min guessing. |
| "I'll just use a Timer for game updates" |
Timer-based updates miss frames and aren't synchronized with rendering. axiom-realitykit has the System pattern. |
Critical Patterns
axiom-spritekit:
- PhysicsCategory struct with explicit bitmasks (default
0xFFFFFFFF causes phantom collisions)
- Camera node pattern for viewport + HUD separation
- SKShapeNode pre-render-to-texture conversion
[weak self] in all SKAction.run closures
- Delta time with spiral-of-death clamping
axiom-spritekit-ref:
- Complete node type table (16 types with batching behavior)
- Physics body creation methods (circle cheapest, texture most expensive)
- Full action catalog with composition patterns
- SKView debug overlays and scale mode matrix
axiom-spritekit-diag:
- 5-step bitmask checklist (2 min vs 30-120 min guessing)
- Debug overlays as mandatory first diagnostic step
- Tunneling prevention flowchart
- Memory growth diagnosis via
showsNodeCount trending
axiom-scenekit:
- Migration decision tree (new project → RealityKit, existing → maintain or migrate)
- USDZ asset conversion before migration (
xcrun scntool)
- SceneView deprecation and SCNViewRepresentable replacement
- Pressure scenarios for "just use SceneKit" rationalization
axiom-scenekit-ref:
- Complete SceneKit → RealityKit concept mapping table
- All material lighting models and properties
- Full constraint catalog
axiom-realitykit:
- ECS mental shift table (scene graph thinking → ECS thinking)
- Custom component registration (
registerComponent())
- Read-modify-write pattern for component updates
- CollisionComponent required for all interaction
- System-based updates instead of timers
axiom-realitykit-ref:
- Complete component catalog with all properties
- MeshResource generators and ShapeResource types
- Scene events catalog
- Material system with all PBR properties
axiom-realitykit-diag:
- Entity visibility checklist (8 branches, 2-5 min vs 30-60 min)
- Gesture debugging (CollisionComponent first check)
- Performance diagnosis (entity count, resource sharing, component churn)
- Physics constraint: entities must share an anchor
Example Invocations
User: "I'm building a SpriteKit game"
→ Invoke: $axiom-spritekit
User: "My physics contacts aren't firing"
→ Invoke: $axiom-spritekit-diag
User: "How do I create a physics body from a texture?"
→ Invoke: $axiom-spritekit-ref
User: "Frame rate is dropping in my game"
→ Invoke: $axiom-spritekit-diag
User: "How do I set up SpriteKit with SwiftUI?"
→ Invoke: $axiom-spritekit
User: "What action types are available?"
→ Invoke: $axiom-spritekit-ref
User: "Objects pass through walls"
→ Invoke: $axiom-spritekit-diag
User: "I need to build a 3D game"
→ Invoke: $axiom-realitykit
User: "How do I add a 3D model to my SwiftUI app?"
→ Invoke: $axiom-realitykit
User: "My RealityKit entity isn't showing up"
→ Invoke: $axiom-realitykit-diag
User: "How do I set up physics in RealityKit?"
→ Invoke: $axiom-realitykit-ref
User: "I'm migrating from SceneKit to RealityKit"
→ Invoke: $axiom-scenekit + $axiom-scenekit-ref
User: "What's the RealityKit equivalent of SCNNode?"
→ Invoke: $axiom-scenekit-ref
User: "Should I use SceneKit for my new 3D project?"
→ Invoke: $axiom-scenekit
User: "Tap gestures don't work on my RealityKit entity"
→ Invoke: $axiom-realitykit-diag
User: "How do I set up ECS in RealityKit?"
→ Invoke: $axiom-realitykit
User: "My AR content isn't tracking"
→ Invoke: $axiom-realitykit-diag
User: "What materials are available in RealityKit?"
→ Invoke: $axiom-realitykit-ref
User: "How do I animate entities in RealityKit?"
→ Invoke: $axiom-realitykit-ref
User: "Memory keeps growing during gameplay"
→ Invoke: $axiom-spritekit-diag
User: "What particle emitter settings should I use for fire?"
→ Invoke: $axiom-spritekit-ref
User: "Can you scan my SpriteKit code for common issues?"
→ Invoke: spritekit-auditor agent
1---2name: axiom-ios-games3description: Use when building ANY 2D or 3D game, game prototype, or interactive simulation with SpriteKit, SceneKit, or RealityKit. Covers scene graphs, ECS architecture, physics, actions, game loops, rendering, SwiftUI integration, SceneKit migration.4license: MIT5metadata:6 source: https://skillmd.com/skills/megastep/axiom-ios-games7---89# iOS Games Router1011**You MUST use this skill for ANY game development, SpriteKit, SceneKit, RealityKit, or interactive simulation work.**1213## When to Use1415Use this router when:16- Building a new SpriteKit game or prototype (2D)17- Building a 3D game with SceneKit or RealityKit18- Implementing physics (collisions, contacts, forces, joints)19- Setting up game architecture (scenes, layers, cameras, ECS)20- Debugging SpriteKit, SceneKit, or RealityKit issues21- Optimizing game performance (draw calls, node counts, entity counts, batching)22- Managing game loop, delta time, or pause handling23- Implementing touch/input handling in a game context24- Integrating SpriteKit or RealityKit with SwiftUI25- Working with particle effects, texture atlases, or 3D models26- Looking up SpriteKit, SceneKit, or RealityKit API details27- Migrating from SceneKit to RealityKit28- Building AR games with RealityKit2930## Routing Logic3132### SpriteKit (2D)3334**Architecture, patterns, and best practices** → `$axiom-spritekit`35- Scene graph model, coordinate systems, anchor points36- Physics engine: bitmask discipline, contact detection, body types37- Actions system: sequencing, grouping, named actions, timing38- Input handling: touches, coordinate conversion39- Performance: draw calls, batching, object pooling, SKShapeNode trap40- Game loop: frame cycle, delta time, pause handling41- Scene transitions and data passing42- SwiftUI integration (SpriteView, UIViewRepresentable)43- Metal integration (SKRenderer)44- Anti-patterns and code review checklist45- Pressure scenarios with push-back templates4647**API reference and lookup** → `$axiom-spritekit-ref`48- All 16 node types with properties and performance notes49- SKPhysicsBody creation methods and properties50- Complete SKAction catalog (movement, rotation, scaling, fading, composition, physics)51- Texture and atlas management52- SKConstraint types and SKRange53- SKView configuration and scale modes54- SKEmitterNode properties and presets55- SKRenderer setup and SKShader syntax5657**Troubleshooting and diagnostics** → `$axiom-spritekit-diag`58- Physics contacts not firing (6-branch decision tree)59- Objects tunneling through walls (5-branch)60- Poor frame rate (4 top branches, 12 leaves)61- Touches not registering (6-branch)62- Memory spikes and crashes (5-branch)63- Coordinate confusion (5-branch)64- Scene transition crashes (5-branch)6566**Automated scanning** → Launch `spritekit-auditor` agent or `/axiom:audit spritekit` (physics bitmasks, draw call waste, node accumulation, action memory leaks, coordinate confusion, touch handling, missing object pooling, missing debug overlays)6768### SceneKit (3D — Deprecated)6970**SceneKit is soft-deprecated as of iOS 26.** Use for maintenance of existing code only. New 3D projects should use RealityKit.7172**Maintenance and migration planning** → `$axiom-scenekit`73- Scene graph architecture, coordinate system, transforms74- Rendering: SCNView, SceneView (deprecated), SCNViewRepresentable75- Geometry, PBR materials, shader modifiers76- Lighting, animation (SCNAction, SCNTransaction, CAAnimation bridge)77- Physics: bodies, collision categories, contact delegate78- Asset pipeline: Model I/O, USD/DAE/SCN formats79- ARKit integration (legacy ARSCNView)80- Migration decision tree (when to migrate vs maintain)81- Anti-patterns and pressure scenarios8283**API reference and migration mapping** → `$axiom-scenekit-ref`84- Complete SceneKit → RealityKit concept mapping table85- Scene graph API: SCNScene, SCNNode, SCNGeometry86- Materials: lighting models, PBR properties, shader modifiers87- Lighting: all light types with properties88- Camera: SCNCamera properties89- Physics: body types, shapes, joints90- Animation: SCNAction catalog, timing functions91- Constraints: all constraint types9293### RealityKit (3D — Modern)9495**For non-game 3D content display (product viewers, AR try-on, spatial computing), the ios-graphics router also routes to these RealityKit skills.**9697**Architecture, ECS, and best practices** → `$axiom-realitykit`98- Entity-Component-System mental model and paradigm shift99- Entity hierarchy, transforms, world-space queries100- Built-in and custom components, component lifecycle101- System protocol, update ordering, event handling102- SwiftUI integration: RealityView, Model3D, attachments103- AR on iOS: AnchorEntity types, SpatialTrackingSession104- Interaction: ManipulationComponent, gestures, hit testing105- Materials: SimpleMaterial, PBR, Unlit, Occlusion, ShaderGraph, Custom106- Physics: collision shapes, groups/filters, events, forces107- Animation: transform, USD playback, playback control108- Audio: spatial, ambient, channel109- Performance: instancing, component churn, shape optimization110- Multiplayer: synchronization, ownership111- Anti-patterns and code review checklist112- Pressure scenarios113114**API reference and lookup** → `$axiom-realitykit-ref`115- Entity API: properties, hierarchy, subclasses116- Complete component catalog with all properties117- MeshResource generators118- ShapeResource types and performance119- System protocol and EntityQuery120- Scene events catalog121- RealityView API: initializers, content, gestures122- Model3D API123- Material system: all types with full property listings124- Animation timing functions and playback control125- Audio components and playback126- RealityRenderer (Metal integration)127128**Troubleshooting and diagnostics** → `$axiom-realitykit-diag`129- Entity not visible (8-branch decision tree)130- Anchor not tracking (6-branch)131- Gesture not responding (6-branch)132- Performance problems (7-branch)133- Material looks wrong (6-branch)134- Physics not working (6-branch)135- Multiplayer sync issues (5-branch)136137## Decision Tree1381391. Building/designing a 2D SpriteKit game? → axiom-spritekit1402. How to use a specific SpriteKit API? → axiom-spritekit-ref1413. SpriteKit broken or performing badly? → axiom-spritekit-diag1424. Maintaining existing SceneKit code? → axiom-scenekit1435. SceneKit API reference or migration mapping? → axiom-scenekit-ref1446. Building new 3D game or experience? → axiom-realitykit1457. How to use a specific RealityKit API? → axiom-realitykit-ref1468. RealityKit entity not visible, gestures broken, performance? → axiom-realitykit-diag1479. Migrating SceneKit to RealityKit? → axiom-scenekit (migration tree) + axiom-scenekit-ref (mapping table)14810. Building AR game? → axiom-realitykit14911. Physics contacts not working (SpriteKit)? → axiom-spritekit-diag (Symptom 1)15012. Frame rate dropping (SpriteKit)? → axiom-spritekit-diag (Symptom 3)15113. Coordinate/position confusion (SpriteKit)? → axiom-spritekit-diag (Symptom 6)15214. Need the complete action list? → axiom-spritekit-ref (Part 3)15315. Physics body setup reference? → axiom-spritekit-ref (Part 2)15416. Entity not visible (RealityKit)? → axiom-realitykit-diag (Symptom 1)15517. Gesture not responding (RealityKit)? → axiom-realitykit-diag (Symptom 3)15618. Want automated SpriteKit code scan? → spritekit-auditor (Agent)157158## Anti-Rationalization159160| Thought | Reality |161|---------|---------|162| "SpriteKit is simple, I don't need a skill" | Physics bitmasks default to 0xFFFFFFFF and cause phantom collisions. The bitmask checklist catches this in 2 min. |163| "I'll just use SKShapeNode, it's quick" | Each SKShapeNode is a separate draw call. 50 of them = 50 draw calls. axiom-spritekit has the pre-render-to-texture pattern. |164| "I can figure out the coordinate system" | SpriteKit uses bottom-left origin (opposite of UIKit). Anchor points add another layer. axiom-spritekit-diag Symptom 6 resolves in 5 min. |165| "Physics is straightforward" | Three different bitmask properties, modification rules inside callbacks, and tunneling edge cases. axiom-spritekit Section 3 covers all gotchas. |166| "The performance is fine on my device" | Performance varies dramatically across devices. axiom-spritekit Section 6 has the debug overlay checklist. |167| "SceneKit is fine for our new project" | SceneKit is soft-deprecated iOS 26. No new features, only security patches. axiom-scenekit has the migration decision tree. |168| "I'll learn RealityKit later" | Every line of SceneKit is migration debt. axiom-scenekit-ref has the concept mapping table so the transition is concrete, not abstract. |169| "ECS is overkill for a simple 3D app" | You're already using ECS — Entity + ModelComponent. axiom-realitykit shows how to scale from simple to complex. |170| "I don't need collision shapes for taps" | RealityKit gestures require CollisionComponent. axiom-realitykit-diag diagnoses this in 2 min vs 30 min guessing. |171| "I'll just use a Timer for game updates" | Timer-based updates miss frames and aren't synchronized with rendering. axiom-realitykit has the System pattern. |172173## Critical Patterns174175**axiom-spritekit**:176- PhysicsCategory struct with explicit bitmasks (default `0xFFFFFFFF` causes phantom collisions)177- Camera node pattern for viewport + HUD separation178- SKShapeNode pre-render-to-texture conversion179- `[weak self]` in all `SKAction.run` closures180- Delta time with spiral-of-death clamping181182**axiom-spritekit-ref**:183- Complete node type table (16 types with batching behavior)184- Physics body creation methods (circle cheapest, texture most expensive)185- Full action catalog with composition patterns186- SKView debug overlays and scale mode matrix187188**axiom-spritekit-diag**:189- 5-step bitmask checklist (2 min vs 30-120 min guessing)190- Debug overlays as mandatory first diagnostic step191- Tunneling prevention flowchart192- Memory growth diagnosis via `showsNodeCount` trending193194**axiom-scenekit**:195- Migration decision tree (new project → RealityKit, existing → maintain or migrate)196- USDZ asset conversion before migration (`xcrun scntool`)197- SceneView deprecation and SCNViewRepresentable replacement198- Pressure scenarios for "just use SceneKit" rationalization199200**axiom-scenekit-ref**:201- Complete SceneKit → RealityKit concept mapping table202- All material lighting models and properties203- Full constraint catalog204205**axiom-realitykit**:206- ECS mental shift table (scene graph thinking → ECS thinking)207- Custom component registration (`registerComponent()`)208- Read-modify-write pattern for component updates209- CollisionComponent required for all interaction210- System-based updates instead of timers211212**axiom-realitykit-ref**:213- Complete component catalog with all properties214- MeshResource generators and ShapeResource types215- Scene events catalog216- Material system with all PBR properties217218**axiom-realitykit-diag**:219- Entity visibility checklist (8 branches, 2-5 min vs 30-60 min)220- Gesture debugging (CollisionComponent first check)221- Performance diagnosis (entity count, resource sharing, component churn)222- Physics constraint: entities must share an anchor223224## Example Invocations225226User: "I'm building a SpriteKit game"227→ Invoke: `$axiom-spritekit`228229User: "My physics contacts aren't firing"230→ Invoke: `$axiom-spritekit-diag`231232User: "How do I create a physics body from a texture?"233→ Invoke: `$axiom-spritekit-ref`234235User: "Frame rate is dropping in my game"236→ Invoke: `$axiom-spritekit-diag`237238User: "How do I set up SpriteKit with SwiftUI?"239→ Invoke: `$axiom-spritekit`240241User: "What action types are available?"242→ Invoke: `$axiom-spritekit-ref`243244User: "Objects pass through walls"245→ Invoke: `$axiom-spritekit-diag`246247User: "I need to build a 3D game"248→ Invoke: `$axiom-realitykit`249250User: "How do I add a 3D model to my SwiftUI app?"251→ Invoke: `$axiom-realitykit`252253User: "My RealityKit entity isn't showing up"254→ Invoke: `$axiom-realitykit-diag`255256User: "How do I set up physics in RealityKit?"257→ Invoke: `$axiom-realitykit-ref`258259User: "I'm migrating from SceneKit to RealityKit"260→ Invoke: `$axiom-scenekit` + `$axiom-scenekit-ref`261262User: "What's the RealityKit equivalent of SCNNode?"263→ Invoke: `$axiom-scenekit-ref`264265User: "Should I use SceneKit for my new 3D project?"266→ Invoke: `$axiom-scenekit`267268User: "Tap gestures don't work on my RealityKit entity"269→ Invoke: `$axiom-realitykit-diag`270271User: "How do I set up ECS in RealityKit?"272→ Invoke: `$axiom-realitykit`273274User: "My AR content isn't tracking"275→ Invoke: `$axiom-realitykit-diag`276277User: "What materials are available in RealityKit?"278→ Invoke: `$axiom-realitykit-ref`279280User: "How do I animate entities in RealityKit?"281→ Invoke: `$axiom-realitykit-ref`282283User: "Memory keeps growing during gameplay"284→ Invoke: `$axiom-spritekit-diag`285286User: "What particle emitter settings should I use for fire?"287→ Invoke: `$axiom-spritekit-ref`288289User: "Can you scan my SpriteKit code for common issues?"290→ Invoke: `spritekit-auditor` agent