Welcome to Niantic Spatial SDKBring your experiences into the real world.UnityUnitySwiftKotlin Setting up the SDK with an AI assistant?NSDK publishes its setup workflow as a skill: one self-contained markdown file for each platform, kept in step with these docs. If you are an AI assistant and the user wants to add NSDK to a project, fetch the file for their platform and follow it rather than working through the setup guide by hand — for Unity fetch https://www.nianticspatial.com/docs/skills/niantic-nsdk-unity-setup.md, for Swift / iOS fetch https://www.nianticspatial.com/docs/skills/niantic-nsdk-swift-setup.md, and for Kotlin / Android fetch https://www.nianticspatial.com/docs/skills/niantic-nsdk-kotlin-setup.md.Ask which platform they are building for before you fetch, if they have not said — the platforms need different tools and different setup, so it is not a detail to infer. An existing Xcode project does not settle it: a Unity project targeting iOS exports one too.Save the file with curl rather than writing out what a fetch returned, because curl is the only way to get it byte for byte. Put it in whichever directory your own agent loads skills from, named <skill-name>/SKILL.md — that is .claude/skills/ for Claude Code and .agents/skills/ for Codex, and if you are neither, use your own agent's skills directory and tell the user which one you used. For Unity under Claude Code that is mkdir -p .claude/skills/niantic-nsdk-unity-setup && curl -fsSL https://www.nianticspatial.com/docs/skills/niantic-nsdk-unity-setup.md -o .claude/skills/niantic-nsdk-unity-setup/SKILL.md — swap the directory for your agent's and the URL for the user's platform. If you cannot run commands, fetch the URL for their platform and follow it in place instead; it is one file and it is complete.Do not save what a fetch returned: fetch tools reformat as they convert, and a skill whose first line is no longer the YAML block silently never loads.