han

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

Prefer explicit configuration over framework defaults to prevent environment-dependent failures

Reduce token waste by batching tool calls and avoiding narration between sequential operations

Resume work on a pull request by loading its context, diff, CI status, and review comments

Load PR context for the current branch using GitHub MCP tools

Load MR context for the current branch using GitLab MCP tools

Manage git worktrees - list active worktrees, prune stale ones, and merge work back into the main branch.

Create a new discipline plugin with specialized agents

Create a new technique plugin for a technology (language, tool, framework, or validation)

Use when responding to production incidents following SRE principles and best practices.

Use when building comprehensive monitoring and observability systems.

Use when building reliable and scalable distributed systems.

Use after modifying existing systems to update blueprint documentation. Read blueprints before changes, update after. Prevents documentation drift.

Use when managing blueprints directory structure and avoiding duplication. Always search existing blueprints before creating to prevent duplicate documentation. Handles naming conventions and cross-references.

Use when creating or updating technical blueprint documentation for new features, API changes, or architectural modifications. Always search existing blueprints first to avoid duplication, then write with proper structure.

Research a specific system and create or update its blueprints/ documentation

Deeply research all systems and create or update blueprints/ documentation for the entire codebase

Use when fundamental C data structures including arrays, structs, linked lists, trees, and hash tables with memory-efficient implementations.

Use when c systems programming including file I/O, processes, signals, and system calls for low-level system interaction.

Use when modern C++ features from C++11/14/17/20 including auto, lambdas, range-based loops, structured bindings, and concepts.

Use when C++ smart pointers including unique_ptr, shared_ptr, and weak_ptr for automatic memory management following RAII principles.

Use when C++ templates and metaprogramming including template specialization, SFINAE, type traits, and C++20 concepts.

Use when C# asynchronous programming with async/await, Task, ValueTask, ConfigureAwait, and async streams for responsive applications.

Use when lINQ (Language Integrated Query) with query and method syntax, deferred execution, expression trees, and performance optimization.

Use when C# nullable reference types and value types for null safety, nullable annotations, and patterns for handling null values.

Use when Django Class-Based Views for building modular, reusable views. Use when creating CRUD operations and complex view logic.

Use when Django ORM patterns with models, queries, and relationships. Use when building database-driven Django applications.

Use when Django REST Framework for building APIs with serializers, viewsets, and authentication. Use when creating RESTful APIs.

Use when validating and casting data with Ecto changesets including field validation, constraints, nested changesets, and data transformation. Use for ensuring data integrity before database operations.

Use when querying data with Ecto.Query DSL including where clauses, joins, aggregates, preloading, and query composition. Use for building flexible database queries in Elixir applications.

Use when defining data structures using Ecto schemas including fields, associations, embedded schemas, and schema metadata. Use for modeling domain data in Elixir applications.

Use when defining and working with Ecto schemas including field types, associations, and embedded schemas. Use when modeling database entities in Elixir.

Use when Effect concurrency patterns including fibers, fork, join, parallel execution, and race conditions. Use for concurrent operations in Effect applications.

Use when Effect core patterns including Effect<A, E, R> type, succeed, fail, sync, promise, and Effect.gen for composing effects. Use for basic Effect operations.

Use when Effect dependency injection patterns including Context, Layer, service definitions, and dependency composition. Use for managing dependencies in Effect applications.