Hot reload and debugging
Check loading separately from behavior
Validate plugin.json, hooks.json and module paths first, then event and render logic. Relative paths resolve from the hooks manifest directory. Extensions and exports must match the current toolchain.
Use the local CLI
claude plugin validate ./your-plugin
claude plugin test --help
Commands and test arguments can change by version. Check claude plugin --help first. This site never automatically runs discovered mods, and validation does not replace behavior tests.
Hot reload
Enable development mode following current official documentation. Release timers, subscriptions, processes and network connections on each reload to prevent duplicate event registration.
Useful debugging records
Record CLI and mod versions, the trigger, expected behavior and actual behavior. Reproduce in a minimal repository. Never log API keys, user code or entire conversations.
Guides
What are Claude Code modsMods vs hooks vs skills vs MCPMods vs Cursor and VS Code extensionsWrite a Claude Code mod in TypeScriptMod security: L0–L3 explainedBest Claude Code mods by categoryWhat is a Claude Code mod?How to install a modBuild your first modMod safety essentialsMods, traditional hooks and skills