add-config

Add a new configuration setting to Wave Terminal across Go structs, defaults, docs, and frontend types.

Updated Apr 26, 2026
One-click install
npx skills add https://github.com/lihonghuacgk/waveterm --skill add-config-lihonghuacgk
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: add-config
Source: https://github.com/lihonghuacgk/waveterm/tree/main/.kilocode/skills/add-config
Command: npx skills add https://github.com/lihonghuacgk/waveterm --skill add-config-lihonghuacgk

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Streamlines adding a new configuration setting to Wave Terminal.

Core Features & Use Cases

  • Provides a standardized workflow to add a new configuration key across the Go backend, defaults, documentation, and frontend typings.
  • Enables optional block-level metadata integration when needed and ensures schema regeneration with the build task.
  • Real-world scenario: a developer adds a new "darkMode" setting that can be configured globally and overridden per block.

Quick Start

Add the new key to the Go struct, wire it into block metadata if needed, provide a default and docs, then run task generate to refresh schemas and frontend types.

Frequently Asked Questions about add-config

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

FAQPage Schema
How do I add a new config setting to Wave Terminal?

Adding a new Wave Terminal configuration option requires updating Go structs, providing a default value, writing documentation, and running the generate task to synchronize schemas and frontend typings.

What steps are needed to update Wave Terminal config schemas and frontend types?

Updating Wave Terminal config schemas and frontend types requires modifying Go code first, then running the generate build task to regenerate schemas and ensure consistency across the configuration system and UI.

Can I add block-level metadata for a new Wave Terminal config option?

Yes, when adding a new Wave Terminal config setting, you can integrate optional block-level metadata into the Go structs, allowing settings to be configured globally and overridden per block.

Why do my Wave Terminal frontend types not match the new Go config defaults?

Frontend types mismatch new Go config defaults when the generate task is skipped. You must run the schema generation task after modifying Go structs and defaults to synchronize the configuration system.

What is the required workflow for modifying Go config structs in Wave Terminal?

The required workflow for modifying Go config structs involves updating the Go code, setting a default value, adding documentation, optionally wiring block metadata, and regenerating schemas with the build task.