What problem does it solve?
This skill helps you replace hand-curated KCL env-var groups with forge.yaml per-environment config so your dev/staging/prod values stop drifting and sensitive values are projected safely.
Core Features & Use Cases
- Detect the old vs new shape: Identify legacy
<NAME>_ENV constants/lambdas in deploy/kcl/base.k and confirm the presence of per-env generated config_gen.k.
- Move config ownership to
forge.yaml: Transfer per-env values into environments[<name>].config (inline) or config.<env>.yaml (sibling wins) to match your rollout needs.
- Add proto annotations for correct projection: Mark sensitive fields in
proto/config/v1/config.proto so forge generates secret_ref EnvVars automatically and groups fields into <CATEGORY>_ENV.
Quick Start
Ask the assistant: "Given my current deploy/kcl/base.k, forge.yaml, and proto/config/v1/config.proto, produce a step-by-step migration plan to upgrade from my pre-1.6 env-var soup to per-env environments[].config, including what to annotate and what to delete after regenerating KCL."