pko-tools

Reference guide for PKO (Pirates King Online) game client source code. Use this skill when you need to understand: (1) Game 3D file format specifications (.lgo, .lmo, .lws, .lac files), (2) How the game engine uses character, mesh, animation, or map data, (3) Verify if current import/export code correctly handles game file structures, (4) Understand bone/skeleton hierarchies, texture mapping, or animation systems, (5) Debug or validate any aspect of the file conversion between PKO formats and glTF.

Inspect PKO binary files by parsing them through Kaitai adapters and printing structured JSON. Use this skill when asked to inspect, dump, examine, or debug a PKO game file (.lmo, .lgo, .lab, .map, .obj, .eff, .lit). Also triggers on /pko-inspect.

Test-Driven Development (TDD) best practices for pko-tools repository. Use this skill when implementing new features, fixing bugs, or refactoring code in either the Rust backend (src-tauri/) or TypeScript/React frontend (src/). Specifically use when (1) adding new functionality that needs tests, (2) writing tests before implementation (red-green-refactor), (3) debugging failing tests, (4) improving test coverage, or (5) setting up test infrastructure.

IMPORTANT: You MUST invoke this skill BEFORE doing any exploration or research yourself when the user says "code tour", "give me a tour", "tour of", "walk me through", "show me how X works", "explain the codebase", "guided tour", "teach me about", or asks to understand a service's architecture or code structure. Do NOT use the Explore agent or read files yourself — invoke this skill first. Interactive educational tour using tmux side pane with nvim.

ALWAYS load this skill before performing ANY tmux operation — including opening panes, splitting windows, running commands in panes, sending keystrokes, or checking pane output. Do NOT improvise tmux pane layout logic inline; all pane creation must go through scripts/split-pane.sh as documented here. Failing to load this skill first will produce incorrect window targeting and unwanted focus shifts.

Prepare a PKO Tools release changelog end to end. Use when asked to bump the app version, draft or update release notes, capture changelog screenshots, or package a release entry from recent work. Covers version sync across package.json/Tauri/Cargo, CHANGELOG.md authoring, screenshot capture through the Tauri MCP app, and optional tag/release prep.