convention-environment-config

Define and validate environment configurations with Pydantic and dotenv.

Updated Mar 19, 2026
One-click install
npx skills add https://github.com/sunLeee/optimization --skill convention-environment-config
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: convention-environment-config
Source: https://github.com/sunLeee/optimization/tree/main/.claude/skills/reference/convention/convention-environment-config
Command: npx skills add https://github.com/sunLeee/optimization --skill convention-environment-config

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Establishes consistent environment configurations across Dev, Staging, and Prod to enable reproducible deployments and reduce configuration drift.

Core Features & Use Cases

  • Environment separation for Dev/Staging/Prod/Test with independent, versioned settings
  • Secret management and injection into runtime environments using AWS Secrets Manager or Vault
  • Configuration validation with Pydantic to catch misconfigurations early
  • 12-Factor App alignment: environment-based configuration, externalized backing services, and verifiable startup behavior
  • CI/CD-friendly templates and schemas for predictable deployments

Quick Start

Define per-environment configurations and load them at startup with the included dotenv loader, optionally injecting secrets from AWS Secrets Manager or Vault.

Frequently Asked Questions about convention-environment-config

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

FAQPage Schema
How do I manage environment configuration across Dev, Staging, and Prod?

Manage environment configuration by defining independent, versioned settings for Dev, Staging, and Prod. This Skill separates environment configurations to enable reproducible deployments and reduce configuration drift across your CI/CD workflows.

How do I validate environment variables with Pydantic to catch misconfigurations?

Validate environment variables with Pydantic by loading dotenv files at startup and applying schema validation. This catches misconfigurations early by enforcing strict types and required fields before your application fully initializes.

Does this approach support injecting secrets from AWS Secrets Manager or Vault?

Yes, this approach supports injecting secrets from AWS Secrets Manager or Vault. It handles secret management by loading external secrets directly into your runtime environment, aligning with 12-Factor App practices for secure configuration.

What is the best way to implement 12-Factor App environment configuration in CI/CD?

The best way to implement 12-Factor App environment configuration in CI/CD is using dotenv loading combined with Pydantic validation. This provides CI/CD-friendly templates and schemas for predictable, verifiable startup behavior across multiple cloud providers.

Can I use this for multi-cloud deployments requiring different runtime targets?

Yes, you can use this for multi-cloud deployments requiring different runtime targets. It covers multiple runtime targets and cloud providers by applying environment separation and verifiable startup behavior within your existing CI/CD workflows.