Skill

explicit-configuration

Guides explicit configuration of databases, APIs, frameworks, security, and infrastructure to prevent failures from varying defaults across environments.

code-quality

infrastructure

npx claudepluginhub thebushidocollective/han --plugin core

Tool Access

This skill cannot use any tools. It operates in read-only mode without the ability to modify files or execute commands.

Preview

han-core:explicit-configuration

SKILL.md

Similar Skills

configuration-management

180

Provides guides and best practices for managing app configuration: environment variables, hierarchies, secrets, feature flags, validation, and 12-factor principles. Use for multi-env setups.

9 files

aj-geddes-useful-ai-prompts-4

twelve-factor

Implements 12-Factor principles for cloud-native apps: codebase via Git, dependencies with lockfiles/Docker multistage, config via env vars. For microservices, Kubernetes, containers.

core

twelve-factor

Guides 12-Factor methodology for scalable cloud-native apps. Use for microservices design, container config, Kubernetes deployment, CI/CD pipelines, and environment management.

all-skills

Stats

Parent Repo Stars129

Parent Repo Forks14

Last CommitMar 27, 2026

Actions

View Source View Plugin View on GitHub View README

Help us improve

Share bugs, ideas, or general feedback.

Explicit Configuration

Name

han-core:explicit-configuration

Description

When configuring services, APIs, or framework features, explicitly set all parameters rather than relying on defaults. Defaults vary across versions, environments, and frameworks.

Principle

What works with defaults in development may fail in production. Explicit configuration is documentation that runs.

Examples

Database connections:

Set pool size, timeout, retry policy explicitly
Don't rely on default connection string parsing

API calls:

Set timeout, retry count, headers explicitly
Don't assume default content-type

Framework config:

Set port, environment, logging level explicitly
Don't rely on framework auto-detection

Security settings:

Never rely on default CORS, auth, or session config
Always configure explicitly, even if the default is "secure"

Anti-Pattern

createServer()  // relies on default port, middleware, error handling

Pattern

createServer({
  port: config.PORT,
  timeout: 30000,
  cors: { origin: config.ALLOWED_ORIGINS }
})

When to Apply

Any time you're initializing a service, client, or framework
Any time you're configuring infrastructure (Docker, CI, cloud services)
Any time the behavior difference between dev and production matters