claude-code-plugin-ref…
Explain plugin, skill, command, agent, and hook mechanics used here. Use when authoring or debugging plugins. Do not use for ops;…
Select hook scope (plugin, project, global) by audience. Use when authoring a hook.
Claude Code
$ npx -y skills add athola/claude-night-market --skill hook-scope-guide --agent claude-code
Codex
$ npx skills add athola/claude-night-market --skill hook-scope-guide -a codex -y
Cursor
$ npx skills add athola/claude-night-market --skill hook-scope-guide -a cursor -y
Gemini CLI
$ npx skills add athola/claude-night-market --skill hook-scope-guide -a gemini-cli -y
GitHub Copilot
$ npx skills add athola/claude-night-market --skill hook-scope-guide -a github-copilot -y
OpenCode
$ npx skills add athola/claude-night-market --skill hook-scope-guide -a opencode -y
Windsurf
$ npx skills add athola/claude-night-market --skill hook-scope-guide -a windsurf -y
name: hook-scope-guide description: 'Select hook scope (plugin, project, global) by audience. Use when authoring a hook.' category: hook-development
This skill helps you choose the right location for Claude Code hooks based on their purpose, audience, and persistence needs.
Three questions pick the scope: who needs this hook, should it be version controlled, and how long should it persist. Plugin hooks (`hooks/hooks.json` in the plugin) serve plugin users while the plugin is enabled. Project hooks (`.claude/settings.json`) serve the team and are committed. Global hooks (`~/.claude/settings.json`) serve only you, in every session, and are never committed.
The question tree, per-scope configuration and examples, loading precedence, security considerations, migration and troubleshooting are written once, in `plugins/abstract/skills/hook-authoring/modules/scope-selection.md`. Read it before choosing. Agent-aware SessionStart hooks are covered in `abstract:hook-authoring` under Hook Event Types.
least two of the three decision questions (audience, version control, persistence).
`~/.claude/settings.json`) is confirmed to exist or is created at the correct path.
guard); this absence is verified before the hook is deployed.
on this machine.
A plugin marketplace for Claude Code. Install only the plugins you need to run git workflows, code review, spec-driven development, and autonomous agents from inside your Claude Code session.
Explain plugin, skill, command, agent, and hook mechanics used here. Use when authoring or debugging plugins. Do not use for ops;…
States load-bearing decisions, invariants, and weak points. Use when judging a design change. Do not use for gating; use…
Rebuild the dev environment: uv, Python tiers, pins, traps. Use when onboarding or toolchain breaks. Do not use for daily…
Classify, gate, and review changes. Use when landing a PR, releasing, or amending rules. Do not use for failure triage; use…
Search and record project memory (Discussions, journal, ADRs). Use before re-investigating anything. Do not use for settled…
Bind loop 'done' to unfakeable gates. Use to harden egregore/herald loops or promote completion_integrity. Not for QA gates; use…
You MUST use this before any creative work - creating features, building components, adding functionality, modifying behavior, or…
Ask which skill or flow fits your situation. A router over the skills in this repo.