jahro-migration
Installation
SKILL.md
Jahro Migration
Help users migrate from custom debug tools to Jahro. Analyze existing code, classify what to replace/keep/adapt, and generate migrated code incrementally.
Migration Decision Guide
When the user shares their existing debug code, classify each component:
| What are you migrating? | Jahro Replacement | Action |
|---|---|---|
IMGUI debug buttons (OnGUI + GUI.Button) |
[JahroCommand] + Visual Mode |
Replace — Visual Mode provides a better button UI |
| Canvas-based debug UI | [JahroCommand] + Visual Mode |
Replace — eliminates UI maintenance |
| Custom command parser (string → command) | [JahroCommand] + Text Mode |
Replace — Jahro handles parsing and type conversion |
| Cheat code system (dictionary/registry) | [JahroCommand] with groups |
Replace — typed parameters, auto-discovery |
| Custom Debug.Log wrapper | Remove or keep | Jahro intercepts Debug.Log automatically — wrapper often unnecessary |
| Performance HUD (FPS, memory overlay) | [JahroWatch] groups |
Replace — Watcher provides organized monitoring |
| File-based logger | Keep | Jahro doesn't write to files — keep if file logging is needed |
| Custom Inspector/Editor tools | Evaluate | May complement Jahro — keep if Editor-only tools |
| Analytics-based logging | Keep | Different purpose — Jahro is for debugging, not analytics |