[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M7F17WDFWQ8TSDZ2J2BGD1RJ":3,"skill-same:01M7F17WDFWQ8TSDZ2J2BGD1RJ":54},{"skillNo":4,"name":5,"nameZh":6,"description":7,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":16,"categories":17,"keywords":18,"publishedAt":19,"linkOnly":20,"markdownContent":21,"markdownBody":22,"frontMatter":23,"refName":26,"commitSha":27,"skillDirectory":28,"forksCount":14,"repositoryHtmlUrl":29,"repositoryHomepageUrl":6,"ownerHtmlUrl":30,"ownerBlogUrl":31,"ownerDescription":32,"updatedAt":33,"install":34,"resources":47},"01M7F17WDFWQ8TSDZ2J2BGD1RJ","ios-spatial-graphics-and-games",null,"Route, implement, or review iOS and visionOS spatial, AR, 2D game, 3D scene, custom Metal, and Game Center features. Use when a feature uses camera\u002Fworld tracking, RealityKit entities, RealityView or ImmersiveSpace, SpriteKit, GameplayKit, Metal, controllers, or GameKit multiplayer and needs measured performance and physical-device proof.","shotcowboystyle\u002Fag-skills","shotcowboystyle","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F62471?v=4","01M7EZTCFCZJ6K3MYW8BPM4X6R","Curtis Blanton","01M7EZTCG1S5M04J90A931X9BX",0,"MIT","https:\u002F\u002Fgithub.com\u002Fshotcowboystyle\u002Fag-skills\u002Fblob\u002Fmain\u002Fplugins\u002Fios-ops\u002Fskills\u002Fios-spatial-graphics-and-games\u002FSKILL.md",[],[],"2026-11-16 10:05:34",false,"---\nname: ios-spatial-graphics-and-games\ndescription: Route, implement, or review iOS and visionOS spatial, AR, 2D game, 3D scene, custom Metal, and Game Center features. Use when a feature uses camera\u002Fworld tracking, RealityKit entities, RealityView or ImmersiveSpace, SpriteKit, GameplayKit, Metal, controllers, or GameKit multiplayer and needs measured performance and physical-device proof.\nallowed-tools: Read, Grep, Glob, Edit, Write, Bash\nlast_verified: 2026-08-19\n---\n\n# iOS Spatial, Graphics, and Games\n\n## Overview\n\nUse this skill to choose the smallest Apple graphics or game layer that meets the product outcome, while keeping device\u002Fsession state, domain or simulation state, rendering, input, networking, accessibility, and proof separate.\n\n`device\u002Fsession availability -> domain or simulation state -> scene\u002Frenderer -> input\u002Fnetwork event -> review\u002Fpersistence`\n\n## Read before acting\n\n- Inspect the actual Xcode targets, platform\u002Fdevice family, deployment target, scene roles, camera usage description, capabilities, entitlements, asset formats, controller\u002Finput routes, persistence, Game Center configuration, and existing renderer\u002Fgame loop.\n- Read the [knowledge-base map](..\u002Fios-knowledge-base\u002Freferences\u002FREADME.md), [spatial graphics and games route](..\u002Fios-knowledge-base\u002Freferences\u002F40-framework-routes\u002F06-spatial-graphics-and-games.md), [RealityKit\u002FARKit\u002Fspatial deep dive](..\u002Fios-knowledge-base\u002Freferences\u002F42-framework-deep-dives\u002F04-realitykit-arkit-and-spatial.md), [Metal\u002FSpriteKit\u002Fgame deep dive](..\u002Fios-knowledge-base\u002Freferences\u002F42-framework-deep-dives\u002F05-metal-spritekit-and-game-routes.md), and [spatial\u002Fgraphics\u002Fgame recipes](..\u002Fios-knowledge-base\u002Freferences\u002F70-code-recipes\u002F18-spatial-graphics-and-game-recipes.md).\n- For proof levels, read the [build\u002Fdevice\u002Frelease checklist](..\u002Fios-knowledge-base\u002Freferences\u002F60-verification\u002F01-build-device-and-release-checklist.md) and [accessibility checklist](..\u002Fios-knowledge-base\u002Freferences\u002F60-verification\u002F02-accessibility-and-adaptability-checklist.md). Refresh the exact official Apple pages in the Sources section before relying on availability, scene roles, device support, input behavior, or Game Center rules.\n\n## Route workflow\n\n1. State the user outcome: 2D game, interactive 3D object, camera\u002Fworld-tracked placement, visionOS window\u002Fvolume, immersive space, custom shader\u002Fcompute, or Game Center session.\n2. Choose the highest-level route that meets a measured need: SpriteKit for 2D scenes\u002Factions\u002Fphysics; GameplayKit for state machines, entities\u002Fcomponents, pathfinding, and deterministic game algorithms; RealityKit for interactive 3D\u002Fspatial entities; ARKit for supported camera\u002Fworld understanding; SwiftUI plus `RealityView`\u002F`SpriteView`\u002FMetal integration for native shells; Metal only for direct GPU control or a measured rendering\u002Fcompute requirement.\n3. Record target configuration: platform, device family, scene role, camera\u002Fmotion\u002Finput support, usage descriptions, capabilities\u002Fentitlements, asset\u002Fmodel formats, Game Center\u002Faccount\u002Fserver requirements, and non-spatial fallback. Mark availability as `to-verify` until the target SDK and hardware are checked.\n4. Model separate state machines. For AR: idle, permission explanation, unsupported, initializing, running-normal\u002Flimited, interrupted, relocalizing, paused, stopped. For games: unauthenticated, authenticating, restricted\u002Fready, matchmaking, connecting, playing, disconnected, ended. For rendering: loading, ready, frame work, resource failure, background, teardown.\n5. Keep product state or simulation state authoritative. Build or rebuild `Entity`\u002Fcomponent graphs and `SKNode` trees from stable app-owned IDs, semantic roles, transforms, and serialized game state; do not make generated scene hierarchies the only durable record.\n6. Bound per-frame work. Avoid asset loading, pipeline compilation, large allocations, unbounded inference, or blocking I\u002FO in the render\u002Fupdate loop. Define frame-drop, pause, interruption, background, low-power, thermal, memory-pressure, and slow-device behavior.\n7. Make input and accessibility plural: touch, controller, keyboard\u002Ftrackpad, system gestures, voice or alternative controls as appropriate; semantic labels, readable summaries, reduced motion, captions, contrast, non-color feedback, and a non-AR\u002Fnon-spatial route for core actions.\n8. Verify in layers: compile the real target, run deterministic scene\u002Fgame fixtures, test state transitions and asset failures, then use the oldest supported and target physical devices. Record OS build, device, scene\u002Flighting\u002Fenvironment, asset set, frame time, dropped frames, memory, GPU\u002FCPU use, battery, thermal state, and input\u002Faccessibility observations.\n\n## Fast path\n\nSelect the renderer and one frame-budgeted vertical slice with a capability gate and a 2D or phone fallback. Measure the update, render, input, and resource path on the target device class before adding assets, networking, multiplayer, or a second scene.\n\n## Framework boundaries\n\n### ARKit, RealityKit, and visionOS\n\n- ARKit coordinates camera\u002Fmotion\u002Fworld understanding for supported configurations. `ARSession.run` is asynchronous; `pause()` stops processing but does not make a prior pose or placement permanently true. Treat tracking as normal, limited, interrupted, relocalizing, or unavailable.\n- RealityKit owns high-level entities, components, systems, animation, physics, and spatial content. Keep a scene adapter between app-owned domain events and the entity graph; bound updates and do not mutate scene content from arbitrary view callbacks.\n- SwiftUI windows and controls remain the native shell. Use `RealityView` for supported 3D content and `ImmersiveSpace` only when the outcome needs content outside a bounded window. Make immersive entry\u002Fexit asynchronous and observable; provide loading, error, dismissal, safety, and non-immersive routes.\n- Camera frames, world maps, room\u002Fscene understanding, hand\u002Feye\u002Fperson observations, and spatial layouts can reveal private spaces and routines. Minimize capture and retention, redact logs, explain data movement, and provide deletion. A plane, mesh, anchor, or pose is framework data with uncertainty, not a measurement, identity, safety guarantee, or construction proof.\n\n### SpriteKit, GameplayKit, Metal, and GameKit\n\n- SpriteKit is the high-level 2D scene\u002Faction\u002Fphysics route; host it in a SwiftUI shell when menus, settings, purchases, accessibility, or system navigation need native controls.\n- GameplayKit algorithms should be testable without a renderer. Use deterministic fixtures or seeded randomness for state machines, pathfinding, entities\u002Fcomponents, and reproducible bug reports.\n- Metal exposes devices, command queues, buffers\u002Ftextures, shaders, pipelines, and render\u002Fcompute passes. Use it only for a measurable requirement, keep resources on the same `MTLDevice`, define synchronization\u002Fownership, and profile before optimizing.\n- GameKit authentication, Game Center restrictions, matchmaking, `GKMatch` transport, player account state, cloud\u002Fleaderboard state, and game simulation are separate. A match is not authoritative game truth; validate messages, bound rates\u002Fsizes, handle duplicate callbacks, player changes, joins\u002Fleaves, disconnects, and offline\u002Frestricted play.\n\nFurther sections — read when the above is not enough: `references\u002Fdetails.md`.\n","# iOS Spatial, Graphics, and Games\n\n## Overview\n\nUse this skill to choose the smallest Apple graphics or game layer that meets the product outcome, while keeping device\u002Fsession state, domain or simulation state, rendering, input, networking, accessibility, and proof separate.\n\n`device\u002Fsession availability -> domain or simulation state -> scene\u002Frenderer -> input\u002Fnetwork event -> review\u002Fpersistence`\n\n## Read before acting\n\n- Inspect the actual Xcode targets, platform\u002Fdevice family, deployment target, scene roles, camera usage description, capabilities, entitlements, asset formats, controller\u002Finput routes, persistence, Game Center configuration, and existing renderer\u002Fgame loop.\n- Read the [knowledge-base map](..\u002Fios-knowledge-base\u002Freferences\u002FREADME.md), [spatial graphics and games route](..\u002Fios-knowledge-base\u002Freferences\u002F40-framework-routes\u002F06-spatial-graphics-and-games.md), [RealityKit\u002FARKit\u002Fspatial deep dive](..\u002Fios-knowledge-base\u002Freferences\u002F42-framework-deep-dives\u002F04-realitykit-arkit-and-spatial.md), [Metal\u002FSpriteKit\u002Fgame deep dive](..\u002Fios-knowledge-base\u002Freferences\u002F42-framework-deep-dives\u002F05-metal-spritekit-and-game-routes.md), and [spatial\u002Fgraphics\u002Fgame recipes](..\u002Fios-knowledge-base\u002Freferences\u002F70-code-recipes\u002F18-spatial-graphics-and-game-recipes.md).\n- For proof levels, read the [build\u002Fdevice\u002Frelease checklist](..\u002Fios-knowledge-base\u002Freferences\u002F60-verification\u002F01-build-device-and-release-checklist.md) and [accessibility checklist](..\u002Fios-knowledge-base\u002Freferences\u002F60-verification\u002F02-accessibility-and-adaptability-checklist.md). Refresh the exact official Apple pages in the Sources section before relying on availability, scene roles, device support, input behavior, or Game Center rules.\n\n## Route workflow\n\n1. State the user outcome: 2D game, interactive 3D object, camera\u002Fworld-tracked placement, visionOS window\u002Fvolume, immersive space, custom shader\u002Fcompute, or Game Center session.\n2. Choose the highest-level route that meets a measured need: SpriteKit for 2D scenes\u002Factions\u002Fphysics; GameplayKit for state machines, entities\u002Fcomponents, pathfinding, and deterministic game algorithms; RealityKit for interactive 3D\u002Fspatial entities; ARKit for supported camera\u002Fworld understanding; SwiftUI plus `RealityView`\u002F`SpriteView`\u002FMetal integration for native shells; Metal only for direct GPU control or a measured rendering\u002Fcompute requirement.\n3. Record target configuration: platform, device family, scene role, camera\u002Fmotion\u002Finput support, usage descriptions, capabilities\u002Fentitlements, asset\u002Fmodel formats, Game Center\u002Faccount\u002Fserver requirements, and non-spatial fallback. Mark availability as `to-verify` until the target SDK and hardware are checked.\n4. Model separate state machines. For AR: idle, permission explanation, unsupported, initializing, running-normal\u002Flimited, interrupted, relocalizing, paused, stopped. For games: unauthenticated, authenticating, restricted\u002Fready, matchmaking, connecting, playing, disconnected, ended. For rendering: loading, ready, frame work, resource failure, background, teardown.\n5. Keep product state or simulation state authoritative. Build or rebuild `Entity`\u002Fcomponent graphs and `SKNode` trees from stable app-owned IDs, semantic roles, transforms, and serialized game state; do not make generated scene hierarchies the only durable record.\n6. Bound per-frame work. Avoid asset loading, pipeline compilation, large allocations, unbounded inference, or blocking I\u002FO in the render\u002Fupdate loop. Define frame-drop, pause, interruption, background, low-power, thermal, memory-pressure, and slow-device behavior.\n7. Make input and accessibility plural: touch, controller, keyboard\u002Ftrackpad, system gestures, voice or alternative controls as appropriate; semantic labels, readable summaries, reduced motion, captions, contrast, non-color feedback, and a non-AR\u002Fnon-spatial route for core actions.\n8. Verify in layers: compile the real target, run deterministic scene\u002Fgame fixtures, test state transitions and asset failures, then use the oldest supported and target physical devices. Record OS build, device, scene\u002Flighting\u002Fenvironment, asset set, frame time, dropped frames, memory, GPU\u002FCPU use, battery, thermal state, and input\u002Faccessibility observations.\n\n## Fast path\n\nSelect the renderer and one frame-budgeted vertical slice with a capability gate and a 2D or phone fallback. Measure the update, render, input, and resource path on the target device class before adding assets, networking, multiplayer, or a second scene.\n\n## Framework boundaries\n\n### ARKit, RealityKit, and visionOS\n\n- ARKit coordinates camera\u002Fmotion\u002Fworld understanding for supported configurations. `ARSession.run` is asynchronous; `pause()` stops processing but does not make a prior pose or placement permanently true. Treat tracking as normal, limited, interrupted, relocalizing, or unavailable.\n- RealityKit owns high-level entities, components, systems, animation, physics, and spatial content. Keep a scene adapter between app-owned domain events and the entity graph; bound updates and do not mutate scene content from arbitrary view callbacks.\n- SwiftUI windows and controls remain the native shell. Use `RealityView` for supported 3D content and `ImmersiveSpace` only when the outcome needs content outside a bounded window. Make immersive entry\u002Fexit asynchronous and observable; provide loading, error, dismissal, safety, and non-immersive routes.\n- Camera frames, world maps, room\u002Fscene understanding, hand\u002Feye\u002Fperson observations, and spatial layouts can reveal private spaces and routines. Minimize capture and retention, redact logs, explain data movement, and provide deletion. A plane, mesh, anchor, or pose is framework data with uncertainty, not a measurement, identity, safety guarantee, or construction proof.\n\n### SpriteKit, GameplayKit, Metal, and GameKit\n\n- SpriteKit is the high-level 2D scene\u002Faction\u002Fphysics route; host it in a SwiftUI shell when menus, settings, purchases, accessibility, or system navigation need native controls.\n- GameplayKit algorithms should be testable without a renderer. Use deterministic fixtures or seeded randomness for state machines, pathfinding, entities\u002Fcomponents, and reproducible bug reports.\n- Metal exposes devices, command queues, buffers\u002Ftextures, shaders, pipelines, and render\u002Fcompute passes. Use it only for a measurable requirement, keep resources on the same `MTLDevice`, define synchronization\u002Fownership, and profile before optimizing.\n- GameKit authentication, Game Center restrictions, matchmaking, `GKMatch` transport, player account state, cloud\u002Fleaderboard state, and game simulation are separate. A match is not authoritative game truth; validate messages, bound rates\u002Fsizes, handle duplicate callbacks, player changes, joins\u002Fleaves, disconnects, and offline\u002Frestricted play.\n\nFurther sections — read when the above is not enough: `references\u002Fdetails.md`.\n",{"name":5,"description":7,"allowed-tools":24,"last_verified":25},"Read, Grep, Glob, Edit, Write, Bash",1787097600000,"main","f846d9a97082ff30d613b55a085cef425d822473","plugins\u002Fios-ops\u002Fskills\u002Fios-spatial-graphics-and-games","https:\u002F\u002Fgithub.com\u002Fshotcowboystyle\u002Fag-skills","https:\u002F\u002Fgithub.com\u002Fshotcowboystyle","https:\u002F\u002Fshotcowboystyle.github.io","Building smarter with AI, automation & modern tools. Exploring how far one person can go without a big team using today’s AI.","2026-11-10 04:58:27",{"source":8,"skillName":5,"commands":35,"prompt":45,"zipAvailable":46},[36,39,42],{"tool":37,"command":38},"npx","npx skills add shotcowboystyle\u002Fag-skills --skill ios-spatial-graphics-and-games",{"tool":40,"command":41},"bunx","bunx skills add shotcowboystyle\u002Fag-skills --skill ios-spatial-graphics-and-games",{"tool":43,"command":44},"pnpm","pnpm dlx skills add shotcowboystyle\u002Fag-skills --skill ios-spatial-graphics-and-games","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fshotcowboystyle\u002Fag-skills\u002Fblob\u002Fmain\u002Fplugins\u002Fios-ops\u002Fskills\u002Fios-spatial-graphics-and-games\u002FSKILL.md",true,[48],{"path":49,"resourceType":50,"resourceTypeDesc":51,"sizeBytes":52,"sourceHtmlUrl":53},"references\u002Fdetails.md","REFERENCE","参考文档",6015,"https:\u002F\u002Fgithub.com\u002Fshotcowboystyle\u002Fag-skills\u002Fblob\u002Fmain\u002Fplugins\u002Fios-ops\u002Fskills\u002Fios-spatial-graphics-and-games\u002Freferences\u002Fdetails.md",[55,61,68,75,82,89],{"skillNo":56,"name":57,"nameZh":6,"description":6,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":58,"categories":59,"keywords":60,"publishedAt":19},"01M7F1YRY5S5QRJ1V0BJS130QX","no-description","https:\u002F\u002Fgithub.com\u002Fshotcowboystyle\u002Fag-skills\u002Fblob\u002Fmain\u002Ftests\u002Ffixtures\u002Fno-description\u002FSKILL.md",[],[],{"skillNo":62,"name":63,"nameZh":6,"description":64,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":65,"categories":66,"keywords":67,"publishedAt":19},"01M7F1Y9BV2FJNQJ3NB32JS5CM","good-skill","Fixture skill that satisfies every rule.","https:\u002F\u002Fgithub.com\u002Fshotcowboystyle\u002Fag-skills\u002Fblob\u002Fmain\u002Ftests\u002Ffixtures\u002Fgood-skill\u002FSKILL.md",[],[],{"skillNo":69,"name":70,"nameZh":6,"description":71,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":72,"categories":73,"keywords":74,"publishedAt":19},"01M7F1XXBQ3NQRXZSS0KAGAR9V","broken-link","Links to a reference file that does not exist.","https:\u002F\u002Fgithub.com\u002Fshotcowboystyle\u002Fag-skills\u002Fblob\u002Fmain\u002Ftests\u002Ffixtures\u002Fbroken-link\u002FSKILL.md",[],[],{"skillNo":76,"name":77,"nameZh":6,"description":78,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":79,"categories":80,"keywords":81,"publishedAt":19},"01M7F1XBX4R46NR9W0HXQ7XCDX","Bad_Name","Name violates the kebab-case rule and does not match the directory.","https:\u002F\u002Fgithub.com\u002Fshotcowboystyle\u002Fag-skills\u002Fblob\u002Fmain\u002Ftests\u002Ffixtures\u002Fbad-name\u002FSKILL.md",[],[],{"skillNo":83,"name":84,"nameZh":6,"description":85,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":86,"categories":87,"keywords":88,"publishedAt":19},"01M7F1WNAF8WNEQ7S5HKT5VK0D","skill-authoring","Write, review, and validate portable agent skills in SKILL.md format. Use when creating a new skill, editing an existing one, or asked whether a skill follows the Agent Skills spec.","https:\u002F\u002Fgithub.com\u002Fshotcowboystyle\u002Fag-skills\u002Fblob\u002Fmain\u002Fskills\u002Fskill-authoring\u002FSKILL.md",[],[],{"skillNo":90,"name":91,"nameZh":6,"description":92,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":93,"categories":94,"keywords":95,"publishedAt":19},"01M7F1W30TC0XFNSF7YBRGETK2","weigh-bags","Record scale readings for each bag — empty (tare), outbound, current, final — and reconcile them against the itemised inventory to find unaccounted weight. Use when the user gives a bag weight, says how heavy something is, weighs their luggage, or asks how close to the limit they are. Appends to bags.yaml and runs scripts\u002Freconcile.py.","https:\u002F\u002Fgithub.com\u002Fshotcowboystyle\u002Fag-skills\u002Fblob\u002Fmain\u002Fplugins\u002Ftravel-packing-assistant\u002Fskills\u002Fweigh-bags\u002FSKILL.md",[],[]]