add-setting-env

Define TypeScript environment variables and merge them into global configuration.

Updated Aug 23, 2026
One-click install
npx skills add https://github.com/razgulay/my-lobe-chat --skill add-setting-env-razgulay
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: add-setting-env
Source: https://github.com/razgulay/my-lobe-chat/tree/main/.agents/skills/add-setting-env
Command: npx skills add https://github.com/razgulay/my-lobe-chat --skill add-setting-env-razgulay

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill guides teams in adding environment variables to configure default values for user settings across server and application code.

Core Features & Use Cases

  • Define environment variables for domain-level settings using TypeScript schemas.
  • Merge and expose env values to the application via a centralized global config.
  • Document and standardize updates to the server config and user store.

Quick Start

Create a TypeScript env definition for the domain under src/envs/<domain>.ts and expose it through the global configuration. Update the user settings store to consume the new environment variable and provide an example in .env.example. Run the app and verify the default values load correctly.

Frequently Asked Questions about add-setting-env

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

FAQPage Schema
How do I manage default user settings with environment variables in a multi-domain TypeScript project?

You can manage default user settings by defining TypeScript environment variable schemas for your domain and merging them into a centralized global server configuration. This ensures consistent defaults are exposed across your multi-domain application.

What's the best way to standardize environment variable configuration across server and application code?

The best way to standardize environment variable configuration is to create TypeScript env definitions under src/envs/<domain>.ts and expose them through a centralized global config. Update the user store to consume these values and document examples in .env.example.

Can I use TypeScript schemas to define domain-level settings for a multi-domain project?

Yes, you can use TypeScript schemas to define domain-level settings. By creating env definitions for each domain and merging them into a global configuration, you expose standardized default values to both server and application code.

How do I integrate new environment variables into an existing user store and global config?

To integrate new environment variables, create a TypeScript env definition for the domain, merge it into the global server configuration, and update the user settings store to consume the new values. Verify default values load correctly by running the app.

Why do my default user settings fail to load after updating the server config?

Default user settings fail to load if the new environment variables are not properly merged into the global configuration or consumed by the user store. Ensure you provide accurate examples in .env.example and verify the app loads the defaults correctly.