add-rpc

Add RPC commands to Wave Terminal's interface with JSON-typed bindings.

40|9|Updated Mar 22, 2026
One-click install
npx skills add https://github.com/mits-pl/wove --skill add-rpc-mits-pl
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: add-rpc
Source: https://github.com/mits-pl/wove/tree/main/.kilocode/skills/add-rpc
Command: npx skills add https://github.com/mits-pl/wove --skill add-rpc-mits-pl

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Streamlines the process of extending Wave Terminal with new RPC commands by providing a standardized workflow, naming conventions, and end-to-end binding guidance.

Core Features & Use Cases

  • Define new RPC commands in the WshRpcInterface using a Command suffix
  • Create structured request/response types with JSON tags
  • Generate language bindings and ensure cross-layer consistency (Go, TS)
  • Implement the command in the appropriate layer (main server, Electron, frontend, remote, or terminal)

Quick Start

Add a new RPC command by updating the interface, run task generate, implement in the appropriate layer (main server, Electron, frontend, remote, or terminal), and test end-to-end.

Frequently Asked Questions about add-rpc

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I add a new RPC command to Wave Terminal's interface?

To add a new RPC command in Wave Terminal, you define it in the WshRpcInterface using a Command suffix, run the generate task, implement it in the appropriate layer, and test end-to-end.

What's the best way to standardize RPC bindings for cross-language integration?

Standardizing RPC bindings involves enforcing naming conventions, using JSON-typed data for request and response structures, and generating language bindings to ensure cross-layer consistency across Go and TypeScript.

How does the RPC generation workflow handle frontend and backend consistency?

The RPC generation workflow handles frontend and backend consistency by providing a standardized approach that defines structured types, generates bindings, and enforces end-to-end validation for reliable cross-language integration.

Can I implement RPC commands across different layers like the main server and Electron?

Yes, you can implement RPC commands across various layers including the main server, Electron, frontend, remote, or terminal, ensuring the command logic resides in the appropriate layer for your specific use case.

Do I need to define JSON-typed request and response types for Wave Terminal RPCs?

Yes, you need to create structured request and response types with JSON tags to ensure reliable cross-language integration and enforce end-to-end validation within the Wave Terminal RPC binding workflow.