add-config

Add a new configuration key to Wave Terminal's Go structs, metadata, defaults, and docs.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Wave Terminal users need a reliable, repeatable process to introduce new configuration keys across its Go structs, metadata, defaults, and documentation.

Core Features & Use Cases

  • Update Go Struct Definitions to add the new field and ensure JSON tagging aligns with the configuration system.
  • Add block-level overrides in pkg/waveobj/wtypemeta.go to support per-block customization.
  • Update defaults in pkg/wconfig/defaultconfig/settings.json and docs in docs/docs/config.mdx, ensuring end-to-end wiring from code to docs.
  • Regenerate schema and TypeScript types with the generate task to keep frontend and backend in sync.

Quick Start

Add a new configuration key to Wave Terminal by updating the Go struct, block metadata, defaults, and docs.

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 configuration key to Wave Terminal's settings system?

You can add a new configuration key by updating Go structs with proper JSON tagging, modifying block metadata in wtypemeta.go, updating defaultconfig settings.json, and adjusting config.mdx documentation for complete end-to-end wiring.

What is the process for updating block metadata when adding Wave Terminal config keys?

Updating block metadata requires adding block-level overrides in pkg/waveobj/wtypemeta.go to support per-block customization, ensuring the new configuration key functions correctly across different Wave Terminal blocks.

How do I keep frontend and backend in sync after adding a Wave config key?

After adding a Wave config key, you keep frontend and backend in sync by regenerating the schema and TypeScript types using the generate task, ensuring both layers reflect the updated configuration structure.

Do I need to update documentation when introducing new Wave Terminal configuration keys?

Yes, updating documentation is required when introducing new configuration keys. You must update user-facing docs in docs/docs/config.mdx to ensure the new settings are properly wired from code to documentation for end users.

Can I use this workflow to add per-block customization for Wave Terminal settings?

Yes, you can add per-block customization for Wave Terminal settings by adding block-level overrides in pkg/waveobj/wtypemeta.go, allowing specific blocks to override default configuration values as needed.

What are the limitations of manually adding config keys without regenerating schema types?

Manually adding config keys without regenerating schema types causes frontend and backend desynchronization. Failing to run the generate task leaves TypeScript types outdated, breaking end-to-end wiring of the new configuration key.