// Prefer explicit configuration over framework defaults to prevent environment-dependent failures
| name | explicit-configuration |
| user-invocable | false |
| description | Prefer explicit configuration over framework defaults to prevent environment-dependent failures |
| allowed-tools | [] |
han-core:explicit-configuration
When configuring services, APIs, or framework features, explicitly set all parameters rather than relying on defaults. Defaults vary across versions, environments, and frameworks.
What works with defaults in development may fail in production. Explicit configuration is documentation that runs.
Database connections:
API calls:
Framework config:
Security settings:
createServer() // relies on default port, middleware, error handling
createServer({
port: config.PORT,
timeout: 30000,
cors: { origin: config.ALLOWED_ORIGINS }
})
Use when building modular Angular applications requiring dependency injection with providers, injectors, and services.
Use when handling async operations in Angular applications with observables, operators, and subjects.
Use when building Angular 16+ applications requiring fine-grained reactive state management and zone-less change detection.
Guides end-to-end feature development through 8 phases: discover requirements, explore codebase patterns, clarify ambiguities with the user, design architecture, implement with TDD, run multi-agent code review, validate all quality gates, and write a blog post. Use when asked to add a feature, implement a new capability, build functionality, or develop a feature end-to-end.
Use when creating or modifying Han plugins. Covers plugin structure, configuration, hooks, skills, and best practices.
Minimize token consumption through efficient tool usage patterns