You MUST use this skill for ANY game development, SpriteKit, SceneKit, RealityKit, or interactive simulation work.
Works with
AI-first code editor with Composer
Before installing skills in Cursor, ensure your development environment meets these requirements:
node --versionaxiom-ios-gamesExecute the skills CLI command in your project's root directory to begin installation:
Fetches axiom-ios-games from charleswiltgen/axiom and configures it for Cursor.
The CLI shows a list of agents. Use arrow keys and space to select Cursor:
Confirm successful installation by checking the skill directory location:
Restart Cursor to activate axiom-ios-games. Access via /axiom-ios-games in your agent's command palette.
We perform automated surface-level scans (Gen AI Scanner, Socket, Snyk) during installation. These checks detect common vulnerabilities but do not guarantee complete security. Always review skill source code and verify the publisher's reputation before production use.
Skills execute code in your environment. Always review source, verify the publisher, and test in isolation before production.
Submit your Claude Code skill and start earning
Create detailed user stories, acceptance criteria, and feature specs
Example
Generate user stories for 'password reset feature' with acceptance criteria, edge cases, and test scenarios
Reduce spec writing time by 50%, ensure comprehensive coverage
Research competitors, compare features, identify gaps
Example
Analyze 5 competitor products, create feature comparison matrix, suggest differentiation opportunities
Complete competitive research in 2 hours instead of 2 days
Evaluate features using frameworks (RICE, ICE, Kano) and create prioritized backlogs
Example
Score 20 feature ideas using RICE framework, generate prioritized roadmap with rationale
0
total installs
0
this week
767
GitHub stars
0
upvotes
Run in your terminal
0
installs
0
this week
767
stars
You MUST use this skill for ANY game development, SpriteKit, SceneKit, RealityKit, or interactive simulation work.
Use this router when:
Architecture, patterns, and best practices → /skill axiom-spritekit
API reference and lookup → /skill axiom-spritekit-ref
Troubleshooting and diagnostics → /skill axiom-spritekit-diag
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 is soft-deprecated as of iOS 26. Use for maintenance of existing code only. New 3D projects should use RealityKit.
Maintenance and migration planning → /skill axiom-scenekit
API reference and migration mapping → /skill axiom-scenekit-ref
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 → /skill axiom-realitykit
API reference and lookup → /skill axiom-realitykit-ref
Troubleshooting and diagnostics → /skill axiom-realitykit-diag
| 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. |
axiom-spritekit:
0xFFFFFFFF causes phantom collisions)[weak self] in all SKAction.run closuresaxiom-spritekit-ref:
axiom-spritekit-diag:
showsNodeCount trendingaxiom-scenekit:
xcrun scntool)axiom-scenekit-ref:
axiom-realitykit:
registerComponent())axiom-realitykit-ref:
axiom-realitykit-diag:
User: "I'm building a SpriteKit game"
→ Invoke: /skill axiom-spritekit
User: "My physics contacts aren't firing"
→ Invoke: /skill axiom-spritekit-diag
User: "How do I create a physics body from a texture?"
→ Invoke: /skill axiom-spritekit-ref
User: "Frame rate is dropping in my game"
→ Invoke: /skill axiom-spritekit-diag
User: "How do I set up SpriteKit with SwiftUI?"
→ Invoke: /skill axiom-spritekit
User: "What action types are available?"
→ Invoke: /skill axiom-spritekit-ref
User: "Objects pass through walls"
→ Invoke: /skill axiom-spritekit-diag
User: "I need to build a 3D game"
→ Invoke: /skill axiom-realitykit
User: "How do I add a 3D model to my SwiftUI app?"
→ Invoke: /skill axiom-realitykit
User: "My RealityKit entity isn't showing up"
→ Invoke: /skill axiom-realitykit-diag
User: "How do I set up physics in RealityKit?"
→ Invoke: /skill axiom-realitykit-ref
User: "I'm migrating from SceneKit to RealityKit"
→ Invoke: /skill axiom-scenekit + /skill axiom-scenekit-ref
User: "What's the RealityKit equivalent of SCNNode?"
→ Invoke: /skill axiom-scenekit-ref
User: "Should I use SceneKit for my new 3D project?"
→ Invoke: /skill axiom-scenekit
User: "Tap gestures don't work on my RealityKit entity"
→ Invoke: /skill axiom-realitykit-diag
User: "How do I set up ECS in RealityKit?"
→ Invoke: /skill axiom-realitykit
User: "My AR content isn't tracking"
→ Invoke: /skill axiom-realitykit-diag
User: "What materials are available in RealityKit?"
→ Invoke: /skill axiom-realitykit-ref
User: "How do I animate entities in RealityKit?"
→ Invoke: /skill axiom-realitykit-ref
User: "Memory keeps growing during gameplay"
→ Invoke: /skill axiom-spritekit-diag
User: "What particle emitter settings should I use for fire?"
→ Invoke: /skill axiom-spritekit-ref
User: "Can you scan my SpriteKit code for common issues?"
→ Invoke: spritekit-auditor agent
Make data-driven prioritization decisions faster
Draft PRDs, status updates, and stakeholder presentations
Example
Create executive summary of Q3 roadmap, monthly progress report, feature launch announcement
Save 3-5 hours/week on communication overhead
Prerequisites
Time Estimate
30-60 minutes to see productivity improvements
Steps
Common Pitfalls
✓ Do
✗ Don't
💡 Pro Tips
✓ Use when
Use for user story writing, competitive research, roadmap prioritization, stakeholder communication, and PRD drafting. Best for reducing repetitive documentation and research work.
✗ Avoid when
Avoid for strategic product vision (requires deep customer empathy), pricing decisions (needs market and financial expertise), or when face-to-face customer discovery is more valuable than speed.
mattpocock/skills
parcadei/continuous-claude-v3
cursor/plugins
ailabs-393/ai-labs-claude-skills
ailabs-393/ai-labs-claude-skills
pproenca/dot-skills
axiom-ios-games is among the better-maintained entries we tried; worth keeping pinned for repeat workflows.
axiom-ios-games fits our agent workflows well — practical, well scoped, and easy to wire into existing repos.
I recommend axiom-ios-games for anyone iterating fast on agent tooling; clear intent and a small, reviewable surface area.
axiom-ios-games fits our agent workflows well — practical, well scoped, and easy to wire into existing repos.
Keeps context tight: axiom-ios-games is the kind of skill you can hand to a new teammate without a long onboarding doc.
I recommend axiom-ios-games for anyone iterating fast on agent tooling; clear intent and a small, reviewable surface area.
Solid pick for teams standardizing on skills: axiom-ios-games is focused, and the summary matches what you get after install.
axiom-ios-games has been reliable in day-to-day use. Documentation quality is above average for community skills.
We added axiom-ios-games from the explainx registry; install was straightforward and the SKILL.md answered most questions upfront.
Keeps context tight: axiom-ios-games is the kind of skill you can hand to a new teammate without a long onboarding doc.
showing 1-10 of 33