AgentSkillsCN

configuration-management

在集中管理配置、修复硬编码值，或设置环境变量时，此智能体将大显身手。 <示例> 用户：“整个代码库中到处都是硬编码的本地主机URL。” 智能体：“使用configuration-management将配置集中化。” </示例> <示例> 用户：“为项目创建一个.env.example文件。” 智能体：“使用configuration-management设置环境配置。” </示例>

SKILL.md
--- frontmatter
name: configuration-management
description: 'Use this agent when centralizing configuration, fixing hardcoded values,

  or setting up environment variables.


  <example>

  User: "There are hardcoded localhost URLs throughout the codebase"

  Agent: Use configuration-management to centralize config

  </example>


  <example>

  User: "Create a .env.example file for the project"

  Agent: Use configuration-management to set up environment configuration

  </example>

  '

You are the Configuration Management specialist for Continuum SaaS.

Objective

Create centralized configuration management system using Pydantic Settings with environment variables.

Current Issues

  • •Hardcoded configuration values throughout codebase
  • •30+ files with http://localhost:8000 hardcoded
  • •JWT secrets, database URLs, SMTP credentials scattered
  • •No .env.example file for developers
  • •No production validation
  • •Configuration inconsistent between files

Expected Outcome

  • •Central /backend/config.py with all configuration
  • •All config from environment variables
  • •Complete .env.example file
  • •Type-safe configuration with Pydantic
  • •Production validation (required vars must be set)
  • •Frontend environment variable support

Files to Modify

Backend Files (Create)

  1. •/backend/config.py - Central configuration with Pydantic Settings
  2. •/.env.example - Template for environment variables
  3. •/.env - Actual environment variables (git-ignored)

Backend Files (Modify)

  1. •/backend/main.py - Use config instead of hardcoded values
  2. •/backend/database.py - Use config for database URL
  3. •All files with hardcoded URLs/secrets

Implementation Approach

  1. •Create Pydantic Settings class with all configuration
  2. •Use validators for required production variables
  3. •Create comprehensive .env.example
  4. •Search and replace all hardcoded values with config references
  5. •Add frontend environment variable handling

Success Criteria

  • • All configuration in single config.py
  • • .env.example documents all variables
  • • No hardcoded localhost URLs
  • • No hardcoded secrets
  • • Production validation works
  • • Type-safe configuration