add-setting-env

Automate environment variable setup for default user settings in TypeScript projects.

Updated Feb 1, 2026
One-click install
npx skills add https://github.com/Chenm4/VoiceChatAssistant --skill add-setting-env-chenm4
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: add-setting-env
Source: https://github.com/Chenm4/VoiceChatAssistant/tree/main/lobehub-main/.agents/skills/add-setting-env
Command: npx skills add https://github.com/Chenm4/VoiceChatAssistant --skill add-setting-env-chenm4

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill provides a structured approach to introduce environment variables to configure default user settings, enabling flexible, environment-based configuration rather than hardcoded values.

Core Features & Use Cases

  • Define domain-specific environment variables in a centralized place.
  • Seamlessly merge server config into the user settings store for consistent defaults.
  • Update .env.example and documentation to reflect new variables for onboarding and deployment.

Quick Start

Create src/envs/<domain>.ts with the env schema and export <domain>Env, then wire into getServerGlobalConfig and update the user store accordingly. Update the .env.example with YOUR_ENV_VAR guidance and document the change across the hosting docs.

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 default user settings using environment variables in a TypeScript backend?

To configure default user settings with environment variables, define domain-specific schemas in TypeScript and merge server config into the user store. This enables deployment-time configuration instead of hardcoded values.

What is the best way to manage server config for local testing and deployment?

Managing server config for testing involves adding environment variables to a centralized global config. Update the .env.example file with guidance to ensure consistent onboarding and deployment scenarios across domains.

Do I need a specific env parsing utility to set user defaults via server env vars?

Yes, setting user defaults via server env vars requires a TypeScript project with an env parsing utility like zod-based schemas. This validates and merges centralized server configs into the user store.

How do I add environment variables to a centralized server config in TypeScript?

To add environment variables to centralized server config, create src/envs/<domain>.ts with the env schema and export <domain>Env. Wire this into getServerGlobalConfig and update the user store.

When should I use environment variables for user settings instead of hardcoded values?

Use environment variables for user settings when you need flexible, environment-based configuration across domains rather than hardcoded values. This approach supports diverse deployment-time configurations and local testing scenarios.