// Use when creating or modifying Han plugins. Covers plugin structure, configuration, hooks, skills, and best practices.
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.
Minimize token consumption through efficient tool usage patterns
Prefer explicit configuration over framework defaults to prevent environment-dependent failures
| name | plugin-development |
| description | Use when creating or modifying Han plugins. Covers plugin structure, configuration, hooks, skills, and best practices. |
| allowed-tools | ["Read","Write","Edit","Bash","Glob","Grep"] |
This skill provides comprehensive guidance for developing Han plugins.
Han supports several plugin categories:
Every plugin must follow this structure:
my-plugin/
├── .claude-plugin/
│ └── plugin.json # Plugin metadata (required)
├── han-plugin.yml # Hook configuration (optional)
├── skills/ # Skills directory (optional)
│ └── my-skill/
│ └── SKILL.md # Skill definition
├── commands/ # Commands directory (optional)
│ └── my-command.md # Slash command
├── hooks/ # Hook scripts (optional)
│ └── my-hook.sh # Hook implementation
└── README.md # Documentation
The plugin.json file defines metadata:
{
"name": "my-plugin-name",
"version": "1.0.0",
"description": "What the plugin does",
"author": {
"name": "Author Name",
"url": "https://author-website.com"
},
"license": "MIT",
"keywords": ["keyword1", "keyword2"]
}
Required fields:
name - Must match directory nameversion - Semantic versioningDefine validation hooks that run at lifecycle events:
hooks:
my-validation:
event: Stop # When to run
command: bash "hooks/my-hook.sh"
description: What this hook does
# Optional filters:
if_changed: # Only run if these files changed
- "**/*.ts"
dirs_with: # Only run in dirs containing
- "package.json"
Setup - Plugin installationSessionStart - Session beginsUserPromptSubmit - User sends messagePreToolUse - Before tool executionPostToolUse - After tool executionStop - Work completion (validation)SubagentStop - Subagent completionScripts receive:
CLAUDE_PLUGIN_ROOT - Plugin directory pathHAN_SESSION_ID - Current session IDHAN_PROJECT_DIR - Project directoryHAN_FILES - Changed files (space-separated)Skills provide domain expertise:
---
name: skill-name
description: When to use this skill
allowed-tools: [Read, Write, Edit, Bash, Glob, Grep]
---
# Skill Title
Skill content with guidance, examples, and best practices.
Required frontmatter:
name - Skill identifierdescription - When Claude should use this skillCommands provide slash command functionality:
---
description: What the command does
---
Command implementation content...
Invoke with: /plugin-name:command-name
Before publishing, validate your plugin:
cd my-plugin
han plugin validate
This checks:
set -e - Exit on first error"${HAN_FILES}" not $HAN_FILESTest your plugin locally:
# Install from local path
han plugin install /path/to/my-plugin --scope project
# Or add to .claude/settings.json manually
Share your plugin:
han plugin install github:user/repoevent matches lifecycle pointcommand path is correctif_changed/dirs_with filtershan plugin validate for specific errors