add-rpc

Create and implement new RPC commands across Wave Terminal modules.

1|Updated Apr 28, 2026
One-click install
npx skills add https://github.com/MichaelCrowe11/crowe-terminal --skill add-rpc-michaelcrowe11
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: add-rpc
Source: https://github.com/MichaelCrowe11/crowe-terminal/tree/main/.kilocode/skills/add-rpc
Command: npx skills add https://github.com/MichaelCrowe11/crowe-terminal --skill add-rpc-michaelcrowe11

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) components.

What problem does it solve?

This Skill provides comprehensive instructions for adding new RPC commands to the Wave Terminal system, enabling developers to expand its server-client communication functionalities securely and efficiently.

Core Features & Use Cases

  • RPC Extension Guidance: Step-by-step instructions for defining new commands, data types, and implementing in various components.
  • Integration Support: Ensures new RPC calls are properly generated, bound, and accessible across main, Electron, frontend, remote, and terminal modules.
  • Use Case: A developer adding a custom command to fetch user settings from the server, ensuring consistent implementation across all layers.

Quick Start

Follow the guide to implement a new RPC command that retrieves system information from the main server and displays it in the UI.

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 in Wave Terminal?

To add a new RPC command in Wave Terminal, follow the step-by-step guidance for defining data types, generating command bindings, and implementing the logic across the main, Electron, frontend, remote, and terminal modules.

What components need to be updated when extending Wave Terminal RPC functionality?

Extending Wave Terminal RPC functionality requires updating the main server, Electron, frontend, remote, and terminal modules to ensure the new command is properly generated, bound, and accessible across all architectural layers.

How does the RPC generation process work in Wave Terminal?

The RPC generation process in Wave Terminal involves defining new command data types, generating the necessary bindings, and implementing the server-client communication logic to ensure seamless and secure integration across modules.

Do I need to write Go or TypeScript code to implement Wave Terminal RPC extensions?

Yes, implementing Wave Terminal RPC extensions requires writing TypeScript and Go code to define the command structures and implement the logic across the terminal's server-client architecture.

Why are my new RPC calls not accessible in the Wave Terminal frontend?

New RPC calls may not be accessible in the Wave Terminal frontend if the command was not properly generated or bound across all required modules, requiring consistent implementation across main, Electron, and remote layers.

Can I securely fetch server settings using a custom Wave Terminal RPC command?

Yes, you can securely fetch server settings by creating a custom Wave Terminal RPC command that follows the provided integration guide to ensure proper binding and security compliance across the terminal modules.