add-setting-env

Environment variables control default user settings by wiring server-side config into the user settings store at startup or deployment. Define domain-specific env vars in src/envs/<domain>.ts, merge them into defaults, and all users inherit the baseline configuration automatically.

Yes, this Skill enforces schemas for environment variables to validate structure and type before merging into the user store. Schema validation ensures safe overrides and prevents misconfigured defaults from reaching users.

Wire environment variables into user settings defaults via domain-specific configuration files. This approach standardizes TypeScript server config across dev, staging, and production environments while maintaining consistent user defaults.

Use environment variables for user setting defaults during environment provisioning, new domain deployments, and when you need consistent baseline settings across all users without manual per-user configuration.

No, this Skill automates documentation and example updates alongside env var merging. Changes to environment-based defaults propagate automatically to docs and examples, keeping them synchronized with actual configuration.

Environment variables merge into user settings as defaults, allowing safe overrides without replacing existing user configuration. New users receive env-based defaults; existing settings remain intact unless explicitly updated.