add-setting-env

Configure server-side environment variables to control default user settings.

1|Updated May 20, 2026

Search Tags:#typescript #environment #env #config-management #server-config #user-settings

Ready to run

npx skills add https://github.com/mDevsLabs/mAI --skill add-setting-env-mdevslabs

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: add-setting-env
Source: https://github.com/mDevsLabs/mAI/tree/main/.agents/skills/add-setting-env
Command: npx skills add https://github.com/mDevsLabs/mAI --skill add-setting-env-mdevslabs

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill configures server-side environment variables to control default values for user settings, enabling consistent behavior across environments.

Core Features & Use Cases

Define and expose environment variables for domain-specific user settings.
Merge server-config values into the user store and ensure runtimeEnv mapping is respected.
Use in self-hosted deployments to simplify defaults for new users and for different deployment targets.

Quick Start

Create or update a server-side environment variable for a user setting domain and verify the default value is applied on new user creation.

Frequently Asked Questions about add-setting-env

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

FAQPage Schema

How do I set default user settings using server environment variables?▼

To set default user settings using server environment variables, define TypeScript env schemas and wire them into your server config. This merges server-config values into the user store, ensuring consistent defaults across self-hosted deployments.

Can I use TypeScript env schemas to manage self-hosted deployment configurations?▼

Yes, you can use TypeScript env schemas to manage self-hosted deployment configurations. This approach centralizes user preferences by mapping runtimeEnv values, ensuring new users receive consistent default settings across different deployment targets.

What is the best way to merge server config values into a user store?▼

The best way to merge server config values into a user store is to map them through runtimeEnv configurations. This ensures server-side environment variables override default user settings correctly while respecting TypeScript schema definitions.

How do I update .env.example when adding new environment variables for user settings?▼

When adding new environment variables for user settings, update the .env.example file to document the changes. This ensures the TypeScript env schemas are transparent and helps maintain consistent server config mappings across self-hosted deployments.

Why are my server-side environment variable defaults not applying to new users?▼

Server-side environment variable defaults may not apply to new users if runtimeEnv mapping is misconfigured. Ensure your TypeScript env schemas properly merge server-config values into the user store and are correctly wired into the global config.

Do I need a self-hosted deployment to configure default user preferences via env vars?▼

No, while self-hosted deployments benefit greatly from configuring default user preferences via env vars for different targets, any application that centralizes user settings can use TypeScript env schemas to enforce consistent default values.