Keewano Unity SDK
Loading...
Searching...
No Matches
AI-Assisted Integration with Claude Code

Overview

Keewano publishes an official Claude Code skill that turns Claude into a proactive integration partner for the Keewano Unity SDK. Once installed, Claude surveys your Unity project for instrumentation gaps, proposes concrete event reports at specific file/line locations, flags anti-patterns in existing usage, and helps you produce an event stream that reads like the player's story.

The skill is optional. The Keewano Unity SDK itself does not require it; install only if your team uses Claude Code.

Installation

The skill lives in its own GitHub repository: https://github.com/Keewano/Keewano-UnitySDK-ClaudeCode-Skill.

Copy the keewano-unity-sdk/ folder from the repo into Claude Code's skills directory.

Project-scoped (versioned with your game; available to everyone on the team running Claude Code in the project):

<your-unity-project>/.claude/skills/keewano-unity-sdk/SKILL.md

User-scoped (available across all your Claude Code sessions, in any project):

~/.claude/skills/keewano-unity-sdk/SKILL.md

After copying, restart Claude Code (or start a new session) so it loads the skill. Claude auto-activates the skill when you work on Keewano-related code.

What Claude Does With It

Once active, Claude understands:

  • The Keewano data model and reporting patterns: small atomic events as a temporal narrative, scoped opener/closer pairs (windows, levels, encounters), item exchanges, IAP server-validation requirements.
  • Where in a Unity codebase analytics belong: IAP managers, ad mediation handlers, tutorial controllers, level managers, virtual economy code, custom popups.
  • Anti-patterns to flag in existing instrumentation: pre-aggregated summary events, raw-store-callback IAP reporting, direction-only loc strings, hand-edited generated files, generic GameObject names that land in the stream verbatim.
  • The custom-events workflow: writing JSONs in Assets/KeewanoCustomEvents/ and triggering codegen via the Custom Events Editor's Save button.

Claude proposes concrete edits with file/line citations, asks for context it can't infer from the code, and stays additive, instrumenting alongside your existing logic rather than redesigning your architecture.