kunkunsh

Use when migrating kkrpc projects across breaking stable API changes, replacing classic IoInterface/*IO adapters, next entries, validation/interceptor options, transport imports, or opt-in streaming/remote-reference entries.

Use when building TypeScript RPC with kkrpc stable APIs, choosing native Transport<RPCMessage> adapters, or integrating validation, middleware, transferables, streaming, remote references, relay, or inspector tooling.

Use when implementing kkrpc clients or servers in non-TypeScript languages, speaking the stable compact protocol, transports, and reference implementations in Go, Python, Rust, or Swift.

Use the plugin for global keyboard/mouse event monitoring and input simulation in Tauri desktop apps, with JS bindings in tauri-plugin-user-input-api.

Use when working in the kunkun-components repo (or consuming its published packages) and the user asks how to install, import, configure the Tailwind/CSS entry and theme tokens, style, build, demo, migrate, or debug usage of @kksh/react, @kksh/vue, @kksh/svelte5, or the legacy @kksh/svelte package. Reach for this especially when @kksh components render blank or unstyled, when wiring up the Tailwind v4 entry / @custom-variant bridge / theme registry, or when setting up a demo app — even if the user doesn't name the skill.