config-standards

Define and enforce configuration management standards across SDD components.

39|3|Updated Nov 21, 2025
One-click install
npx skills add https://github.com/LiorCohen/sdd --skill config-standards
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: config-standards
Source: https://github.com/LiorCohen/sdd/tree/main/plugin/fullstack-typescript/skills/components/config/config-standards
Command: npx skills add https://github.com/LiorCohen/sdd --skill config-standards

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

SDD projects often suffer from configuration drift across components and environments. This Skill defines a single source of truth for configuration patterns, ensuring consistency and reliable deployments.

Core Features & Use Cases

  • Structured directory layout and conventions for config at components/config
  • Environment layering with envs/default and envs/{env} to define merge order
  • Type-safe config definitions and JSON Schema validation for runtime safety
  • Local development workflow alignment, including generation, validation, and deployment readiness

Quick Start

Apply the standard configuration layout and validation patterns to your project to enforce consistency from development to production.

Frequently Asked Questions about config-standards

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

FAQPage Schema
How do I prevent configuration drift across multiple environments?

Prevent configuration drift by enforcing a single source of truth for configuration patterns. This involves using a structured directory layout and environment layering to ensure consistency and reliable deployments.

What is the best way to structure YAML configuration files for schema validation?

Structure YAML configuration files using a components/config directory layout with YAML frontmatter metadata. This enables JSON Schema validation for type-safe definitions and runtime safety.

How does environment layering work for multi-environment configuration management?

Environment layering works by defining merge order through envs/default and envs/{env} directories. This ensures base configurations are overridden correctly across multi-environment projects.

Do I need JSON Schema definitions for runtime configuration validation?

You need JSON Schema definitions to enable type-safe config definitions and runtime validation pipelines. This ensures correctness and deployment readiness throughout your local development workflow.

Can I use standard directory conventions for local development configuration generation?

Yes, you can use standard directory conventions for local development configuration generation. The structured layout aligns generation, validation, and deployment readiness workflows directly.