Skip to main content 홈 크리에이터 ajbcoding claude-skill-eval moai-alfred-config-schema
moai-alfred-config-schema Enterprise configuration schema validation and management orchestrator with JSON Schema v2024-12, Context7 integration, semantic versioning compliance, environment variable management, secrets handling, multi-environment support, and configuration-as-code best practices; activates for config validation, schema enforcement, environment setup, secrets management, and configuration audits
설치로 이동 Skills Marketplace 커뮤니티가 만든 AI 스킬을 발견하고 탐색하세요.
Codex 또는 Claude로 설치 이 Prompt를 복사해 Codex, Claude 또는 다른 어시스턴트에 붙여 넣으면 Skill 페이지를 검토하고 설치를 진행할 수 있습니다.
직접 명령은 검토 Prompt를 거치지 않습니다. 실행하기 전에 소스를 확인하세요.
npx skills add https://github.com/AJBcoding/claude-skill-eval --skill moai-alfred-config-schema명령은 한 줄로 유지됩니다. 복사하기 전에 가로로 스크롤해 전체 내용을 확인하세요.
로컬 사본을 원하시나요? SkillsMP에서 현재 제공할 수 있는 파일을 다운로드하세요.
Zip 다운로드 다운로드 중... name moai-alfred-config-schema version 4.0.0 created 2025-11-11T00:00:00.000Z updated 2025-11-12T00:00:00.000Z status stable description Enterprise configuration schema validation and management orchestrator with JSON Schema v2024-12, Context7 integration, semantic versioning compliance, environment variable management, secrets handling, multi-environment support, and configuration-as-code best practices; activates for config validation, schema enforcement, environment setup, secrets management, and configuration audits keywords ["configuration-schema","json-schema","config-management","environment-management","secrets-handling","semantic-versioning","configuration-as-code","schema-validation","multi-environment","enterprise-config"] allowed-tools ["Read","Write","Edit","Bash","AskUserQuestion","mcp__context7__resolve-library-id","mcp__context7__get-library-docs","WebFetch"]
Enterprise Configuration Schema Management v4.0.0
Skill Metadata
Field Value Skill Name moai-alfred-config-schema Version 4.0.0 Enterprise (2025-11-12) Standards JSON Schema v2024-12, RFC 8174 keywords, TOML/YAML best practices AI Integration ✅ Context7 MCP for official docs Auto-load When config validation or management needed Environments development, staging, production + custom Lines of Content 900+ with 12+ production examples Progressive Disclosure 3-level (quick-start, patterns, advanced)
What It Does
Provides comprehensive guidance for managing project configuration with JSON Schema validation, environment-specific overrides, secrets management, semantic versioning compliance, and configuration-as-code best practices.
Configuration Hierarchy (3-Layer)
Layer 1: Base Configuration
File : .moai/config/config.json (checked into repo)
{
"project" : {
"name" : "moai-adk" ,
"version" : "0.22.5" ,
"description" : "SPEC-First TDD Development Kit"
} ,
"language" : {
"primary" : "en" ,
"conversation_language"
:
"ko"
,
"supported"
:
[
"en"
,
"ko"
,
"ja"
]
}
,
"git_strategy"
:
{
"use_gitflow"
:
true
,
"main_branch"
:
"main"
,
"develop_branch"
:
"develop"
}
,
"document_management"
:
{
"enabled"
:
true
,
"enforce_structure"
:
true
}
}
Checked into version control
No secrets, credentials, or API keys
Environment-agnostic defaults
Semantic versioning format
Layer 2: Environment Overrides Files : .moai/config/.env.{environment} (NOT checked in)
# .moai/config/.env.production
DATABASE_URL=postgresql://prod-db.example.com/production
API_KEY=sk-prod-xxxxxxxxxxxx
REDIS_URL=redis://prod-cache.example.com:6379
DEBUG=false
LOG_LEVEL=error
One file per environment
Contains secrets and env-specific values
MUST be in .gitignore
Loaded at runtime based on NODE_ENV/ENVIRONMENT
Layer 3: Local Development Overrides File : .moai/config/.env.local (NOT checked in)
# .moai/config/.env.local (developer-specific)
DATABASE_URL=postgresql://localhost/mydb
API_KEY=sk-dev-xxxxxxxxxxxx
DEBUG=true
LOG_LEVEL=debug
Developer-specific settings
Takes precedence over everything
NEVER committed to repo
Used for local testing with real services
JSON Schema v2024-12 Validation
Base Schema Structure {
"$schema" : "https://json-schema.org/draft/2024-12/schema" ,
"$id" : "https://moai-adk.dev/schemas/config-v4.0.0.json" ,
"title" : "MoAI-ADK Configuration Schema" ,
"description" : "Configuration schema for MoAI Agentic Development Kit v4.0.0" ,
"type" : "object" ,
"required" : [ "project" , "language" , "git_strategy" ] ,
"properties" : {
"project" : {
"type" : "object" ,
"required" : [ "name" , "version" ] ,
"properties" : {
"name" : {
"type" : "string" ,
"minLength" : 1 ,
"maxLength" : 100 ,
"pattern" : "^[a-z0-9][a-z0-9-]*[a-z0-9]$" ,
"description" : "Project name (kebab-case)"
} ,
"version" : {
"type" : "string" ,
"pattern" : "^\\d+\\.\\d+\\.\\d+(-[a-zA-Z0-9]+)*$" ,
"description" : "Semantic version (e.g., 0.22.5)"
}
}
} ,
"language" : {
"type" : "object" ,
"properties" : {
"conversation_language" : {
"type" : "string" ,
"enum" : [ "en" , "ko" , "ja" , "es" , "fr" , "de" , "zh" , "pt" , "ru" ]
}
}
}
} ,
"additionalProperties" : false }
Configuration Validation Checklist
Required Validations Check Standard Tool JSON Schema v2024-12 compliance JSON Schema ajv, jsonschema No hardcoded secrets Security grep, git-secrets Semantic versioning format RFC 8174 regex, semver library Environment variables defined Best practice dotenv-cli, envman Type correctness JSON typing JSON validator Required fields present Schema JSON Schema validator
Security Validation
{
"database" : {
"password" : "super_secret_123"
},
"api_key" : "sk-1234567890"
}
{
"database" : {
"password" : "${DB_PASSWORD}"
},
"api_key" : "${API_KEY}"
}
.env
.env .local
.env .*.local
.vercel /
config/.env *
Environment Management
Standard Environments development → Local development with mock services
staging → Pre-production testing
production → Live production environment
test → Automated testing with fixtures
Loading Strategy function loadConfig (environment : string const baseConfig = require ('.moai/config/config.json' );
const envConfig = loadEnvFile (`.moai/config/.env.${environment} ` );
const localConfig = loadEnvFile ('.moai/config/.env.local' );
return {
...baseConfig,
...envConfig,
...localConfig
};
}
Secrets Management Best Practices
DO
✅ Store secrets in .env.{environment} files
✅ Load at runtime via environment variables
✅ Use secret management tools (AWS Secrets Manager, Vault, etc.)
✅ Rotate secrets regularly
✅ Use strong, random values
✅ Document secret naming conventions
✅ Audit access to secrets
✅ Enable secret scanning in CI/CD
DON'T
❌ Commit .env files to repo
❌ Hardcode API keys, passwords, tokens
❌ Share secrets in Slack, email, or tickets
❌ Use weak or predictable values
❌ Leave old secrets in git history
❌ Print secrets in logs
❌ Commit credentials to .gitignore
❌ Use same secret across environments
Git Safety for Configuration
.gitignore Configuration # Configuration secrets
.env
.env.local
.env.*.local
.moai/config/.env*
# Deployment platform secrets
.vercel/
.netlify/
.firebase/
.aws/credentials
# IDE secrets
.vscode/settings.json
.idea/workspace.xml
# OS secrets
.DS_Store
# Never commit these patterns
**/secrets.*
**/credentials.*
**/api[_-]?key*
**/password*
**/token*
Pre-Commit Verification #!/bin/bash
echo "Checking for committed secrets..."
git diff --cached | grep -i \
-e "api[_-]?key" \
-e "secret" \
-e "password" \
-e "token" \
-e ".env" \
-e "credentials"
if [ $? -eq 0 ]; then
echo "ERROR: Secrets detected in staged files!"
exit 1
fi
exit 0
Semantic Versioning in Config Format : MAJOR.MINOR.PATCH[-PRERELEASE][+BUILD]
0.22.5 → Stable release
0.22.5-alpha → Alpha pre-release
0.22.5-beta.1 → Beta release #1
0.22.5+build.123 → Build metadata
0.22.5-rc.1+build.2 → Release candidate with build info
MAJOR (0→1): Breaking changes, major rewritesMINOR (22→23): New features, backward compatiblePATCH (5→6): Bug fixes onlyPre-release : Experimental, not production-readyBuild metadata : Informational only, doesn't affect version precedence
Configuration-as-Code Best Practices
Pattern 1: Type-Safe Configuration
interface AppConfig {
project : {
name : string ;
version : string ;
};
language : {
conversation_language : 'en' | 'ko' | 'ja' ;
};
git_strategy : {
use_gitflow : boolean ;
main_branch : string ;
};
}
function validateConfig (config : unknown AppConfig {
const schema = require ('./schemas/config-v4.0.0.json' );
const valid = ajv.validate (schema, config);
if (!valid) {
throw new Error (`Config validation failed: ${ajv.errorsText()} ` );
}
return config as AppConfig ;
}
Pattern 2: Environment-Specific Defaults function getConfig (environment : string AppConfig {
const baseConfig = readConfigFile ('config.json' );
const envConfig = readEnvFile (`.env.${environment} ` );
const localConfig = readEnvFile ('.env.local' );
const defaults = {
development : { debug : true , logLevel : 'debug' },
staging : { debug : false , logLevel : 'info' },
production : { debug : false , logLevel : 'error' }
};
return {
...baseConfig,
...defaults[environment],
...envConfig,
...localConfig
};
}
Pattern 3: Secrets Validation function validateSecrets (config : AppConfig void {
const requiredSecrets = [
'DATABASE_URL' ,
'API_KEY' ,
'JWT_SECRET'
];
for (const secret of requiredSecrets) {
if (!process.env [secret]) {
throw new Error (`Missing required secret: ${secret} ` );
}
if (secret === 'API_KEY' && !process.env [secret].startsWith ('sk-' )) {
throw new Error (`Invalid API_KEY format` );
}
}
}
Related Skills
moai-alfred-practices (Best practices patterns)moai-foundation-specs (Specification management)
For detailed schema reference : reference.md For real-world examples : examples.md Last Updated : 2025-11-12Status : Production Ready (Enterprise v4.0.0)
Enterprise-grade security expertise with production-ready patterns for OWASP Top 10 2021, zero-trust architecture, threat modeling (STRIDE, PASTA), secure SDLC, DevSecOps automation, cloud security, cryptography, identity & access management, and compliance frameworks (SOC 2, ISO 27001, GDPR, CCPA).
