// Reduce token waste by batching tool calls and avoiding narration between sequential operations
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
| name | silent-execution |
| user-invocable | false |
| description | Reduce token waste by batching tool calls and avoiding narration between sequential operations |
| allowed-tools | [] |
han-core:silent-execution
When executing a sequence of related tool calls (running tests, fixing lint, applying edits), batch operations and report results only when complete.
Anti-pattern (wasteful):
"Now I'll run the tests..." [runs tests] "Tests passed. Now I'll run the linter..." [runs linter] "Linting clean. Let me check types..."
Pattern (efficient):
[runs tests, linter, type-check] "All quality gates pass: tests (42 passed), lint (clean), types (no errors)."
~50-100 tokens per batch cycle. Over a typical session with 20+ build cycles, this saves 1,000-2,000 tokens.
