// Minimize token consumption through efficient tool usage patterns
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.
Prefer explicit configuration over framework defaults to prevent environment-dependent failures
| name | token-efficiency |
| user-invocable | false |
| description | Minimize token consumption through efficient tool usage patterns |
| allowed-tools | [] |
han-core:token-efficiency
Minimize token consumption without sacrificing quality. Every token spent on overhead is a token not available for thinking.
| Wasteful | Efficient |
|---|---|
| Read file → Write entire file with 1 line changed | Edit the specific line |
cat file.txt via Bash | Read tool |
find . -name "*.ts" via Bash | Glob **/*.ts |
| "Let me start by reading the file to understand..." | Just read it |
Always. Token efficiency is not premature optimization — it directly extends how much work fits in a session.