Unity Agent Skills — AI-Assisted Debugging

AI coding assistants know generic C# and Unity patterns, but they get Jahro-specific details wrong: attribute parameter order, RegisterObject lifecycle, dynamic registration overloads, snapshot modes, and JAHRO_DISABLE semantics. Agent skills fix that.

Agent skills are markdown files you drop into your project. They give your AI assistant (Claude Code, Cursor, Windsurf, or any tool that reads markdown context) exact API knowledge, code templates, and diagnostic decision trees for Jahro and Unity debugging. The result: generated code that works on the first try.

Quick start

git clone https://github.com/jahro-console/unity-agent-skills.git .agents/skills/jahro

Then ask your AI assistant something like:

"Add debug commands to my PlayerController"

The skill activates automatically and the AI generates correct [JahroCommand] attributes, RegisterObject lifecycle, group organization, and parameter handling — without you having to explain Jahro's API.

For Cursor and other assistants, see the full installation guide.

The 8 skills

SkillWhat your AI can do
LoggingReview and improve Debug.Log usage: structured [Tag] Action — key=value format, severity contracts, criticality tiers, boundary-based placement, 10 antipattern detections. Works without Jahro.
SetupDetect Jahro in your project, guide installation via UPM, configure API keys, recommend feature adoption order (logs → commands → watcher → snapshots)
CommandsGenerate [JahroCommand] attributes with correct syntax, RegisterObject boilerplate, group organization, dynamic registration, and overloads
WatcherGenerate [JahroWatch] attributes with supported types, group strategies, and the performance model (values only read when UI is visible)
SnapshotsConfigure snapshot modes (Recording, Streaming All, Streaming Except Editor), QA workflows, session management
ProductionSet up production safety: JAHRO_DISABLE define, auto-disable in release builds, CI/CD guidance, build validation
TroubleshootingDiagnose issues via decision trees: commands not appearing, watcher not updating, console not opening, snapshots failing
MigrationAnalyze existing debug systems (IMGUI menus, custom loggers, cheat frameworks) and generate incremental migration plans

Each skill is a standalone SKILL.md file (~300–450 lines). Most reference two shared files containing the complete Jahro API and common code patterns. Your AI loads only the triggered skill plus references on demand — context stays lean.

Example prompts

These are real prompts you can use after installing the skills:

Logging:

  • "Review the logging in my SaveManager"
  • "Set up logging conventions for our project"

Commands & Watcher:

  • "Add debug commands to my PlayerController"
  • "Monitor these variables at runtime"

Diagnostics:

  • "My commands aren't showing up"
  • "The Jahro console won't open on my Android build"

Migration:

  • "Migrate our OnGUI debug menu to Jahro commands"
  • "Replace our custom logger with structured logging"

Production:

  • "Set up Jahro so it's excluded from release builds"
  • "Add a CI step to verify JAHRO_DISABLE is set"

How skills work

Each skill file contains:

  • YAML frontmatter with name and description fields that tell the AI when to activate (e.g., when you mention "debug commands" or "JahroWatch")
  • Markdown body with structured instructions, decision tables, code templates, verification steps, and contextual awareness rules

Contextual awareness means the AI doesn't wait for you to ask. If it sees OnGUI() debug buttons in your code, the migration skill suggests moving to Jahro commands. If it sees Debug.Log in Update(), the watcher skill suggests [JahroWatch] instead. If it sees bare Debug.Log("here"), the logging skill suggests structured format.

The logging skill is standalone

The jahro-logging skill works without Jahro installed. It teaches your AI structured logging practices for any Unity project: structured format, criticality tiers, boundary-based placement, and 10 antipattern detections. It mentions Jahro as an optional enhancement for log viewing and filtering, but doesn't require it.

If you only want better Debug.Log usage across your team, install just this skill.

Requirements

  • Unity: 2021.3.0f1 or later
  • Jahro: 1.0.0-beta6+ (for Jahro-specific skills)
  • AI assistant: Any assistant that reads markdown context (Claude Code, Cursor, Windsurf, etc.)

Repository

The skills are open-source under the MIT license:

github.com/jahro-console/unity-agent-skills

unity-agent-skills/
├── skills/            # 8 skill files (one SKILL.md each)
├── references/        # Shared API reference and common patterns
├── evals/             # 24 evaluation scenarios for testing skill quality
├── README.md
└── LICENSE

The repo includes 24 evaluation scenarios (3 per skill) and a baseline gap analysis documenting what AI assistants get wrong without skills. This infrastructure tracks skill quality as Jahro's API evolves.

Frequently Asked Questions

What are Unity agent skills? Agent skills are markdown files that teach AI coding assistants domain-specific knowledge. For Jahro, they provide exact attribute syntax, registration patterns, lifecycle rules, and diagnostic decision trees so the AI generates correct Unity debugging code on the first try.

Do agent skills require Jahro? Seven of the eight skills are Jahro-specific. The jahro-logging skill is standalone and teaches structured logging practices for any Unity project — no Jahro required.

Which AI assistants are supported? Claude Code, Cursor, Windsurf, and any assistant that supports markdown context files. See installation for setup instructions.

Are agent skills free? Yes. The skills repo is MIT-licensed and hosted on GitHub.

How do I update the skills? Run git pull in the directory where you cloned the repo. Skills are versioned alongside Jahro releases.

Next steps

Last updated: April 2, 2026