add-setting-env

Merge server-side environment variables into user settings at runtime.

Updated Aug 30, 2025
One-click install
npx skills add https://github.com/cute-baobao/pm --skill add-setting-env-cute-baobao
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: add-setting-env
Source: https://github.com/cute-baobao/pm/tree/main/.agents/skills/add-setting-env
Command: npx skills add https://github.com/cute-baobao/pm --skill add-setting-env-cute-baobao

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This guide helps developers implement server-side environment variables to configure default user settings, ensuring consistent behavior across environments.

Core Features & Use Cases

  • Define per-domain env config in src/envs/<domain>.ts
  • Merge env-driven defaults into the user store at runtime
  • Validate and document server/global config to avoid misconfig

Quick Start

Create a domain-specific env config at src/envs/<domain>.ts and wire it into the server-global config to apply defaults.

Frequently Asked Questions about add-setting-env

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

FAQPage Schema
How do I configure user settings with server environment variables in TypeScript?

To configure user settings with server environment variables, you define per-domain env config files and merge those env-driven defaults into the user store at runtime, ensuring type-safe configuration across environments.

What is the best way to structure domain-specific environment variables for a user store?

The best way to structure domain-specific environment variables is to create dedicated config files for each domain, wire them into the server-global config, and validate the schemas to avoid misconfigurations before merging.

How do I merge environment-derived defaults into a user settings store?

You merge environment-derived defaults into a user settings store by applying safe merging logic during startup or runtime, updating the server and user config wiring to apply the validated domain-specific settings automatically.

When do I need to use environment variables for default user settings?

You need to use environment variables for default user settings when your codebase requires domain-specific settings and consistent behavior across multiple environments, ensuring server-side defaults are safely applied to the user store.

Does this approach support runtime configuration updates for domain settings?

Yes, this approach supports runtime configuration updates for domain settings. The system applies safe merging of env-derived defaults into the user store during startup or runtime, allowing dynamic configuration updates without hardcoding values.