explicit-configuration
Prefer explicit configuration over framework defaults to prevent environment-dependent failures
来源信息
- 仓库
- TheBushidoCollective/han
- 最近来源活动
- 2026年3月27日 13:19
- 检测到的 SKILL.md 语言
- 英语
- 星标
- 198
- Forks
- 24
安装方式
默认使用会先检查来源的 Prompt；你也可以切换为直接命令，或下载本地副本。
检查来源文件
决定是否安装前，请先阅读 SKILL.md，以及 SkillsMP 当前展示的配套文件。
正在显示 SKILL.md
SKILL.md
来源说明 · 只读预览- name
- explicit-configuration
- user-invocable
- false
- description
- Prefer explicit configuration over framework defaults to prevent environment-dependent failures
- allowed-tools
- []
# 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
在 GitHub 查看