hooks

An introduction to the claude-howto tutorial repo on GitHub, which helps users get started from zero with Claude Code's advanced features — subagents, hooks, skills, and MCP servers — through 10 modules, visual Mermaid diagrams, and ready-to-use templates.

The author developed an open-source tool called scar-cli to measure whether AI agents actually follow injected rules, reporting 737 rule firings with zero violations in their own repositories and inviting community testing.

This article explains the React hooks useMemo and useCallback, detailing their purpose for optimizing component re-renders and providing use cases for better performance.

An in-depth look at Arch Linux's alpm-install-scriptlet files and alpm-hooks, how they work, how they are used across package repositories, and guidance for when to use each.

A blog post about encoding referential stability as a TypeScript type using phantom brands, so React props can enforce that arrays, callbacks, and objects are stable across renders.

A blog post describing a minimal CI system using Git hooks and nq, a lightweight job queue, for personal git repositories.

An open-source reference library containing production-tested Claude Code infrastructure from 6 months of real-world use, including auto-activating skills, hooks, and modular patterns for TypeScript microservices projects.

Anthropic's Applied AI team shares a mental model for Claude Code: CLAUDE.md as memory, hooks as reflexes, and MCP as senses — a framework for how advanced teams use the tool.

PrajwalTomar shares a 4-loop setup for Claude Code that enforces test suite execution on every change, prevents marking work done while tests fail, uses a separate model to confirm completion, and writes repeated mistakes to a rules file.

Share two ways to use Claude Hooks: passively observe and record tool call logs, and actively intervene to implement a learning mode state machine. Emphasize that Hooks as hard constraints are more reliable than prompts.

This article introduces six ways to use Hooks in Claude Code, including permission pop-ups, startup schedule announcements, summary cards, automatic file organization, sedentary reminders, and long task notifications, demonstrating how event-driven automation can improve the efficiency of AI workflows.

A detailed guide on using Claude Code effectively, including setup, CLAUDE.md configuration, four-layer architecture, hooks, and daily workflow patterns.

Sai Rahul highlights Claude Code's Hooks feature that automates test running after edits, blocks destructive bash commands, logs spending, sends Slack alerts, and rewrites bad output automatically.

A comprehensive guide explaining Claude Code Hooks, which are programmable checkpoints that run before actions to enforce rules and block or allow tool calls, offering more reliable control than CLAUDE.md guidance.

A blog post advocating for package managers to support global hooks as a more secure and flexible alternative to current package security measures like registries or shell wrappers.

A blog post examining Pluggy, a Python library for building plugin systems originally from pytest, including how it works and how to use it with a toy HTML conversion tool.

Anthropic quietly released the official plugin claude-code-setup, which scans your project and recommends configurations such as Hooks, Skills, MCP servers, etc., upgrading Claude Code into a complete AI development environment.

Claude Fable 5 has been released, enabling autonomous operation with sub-agents, hooks, and persistent memory, building on foundations demonstrated a year ago with Claude Code.

This article introduces the five-layer safety guardrail configuration of Claude Code, including OS sandbox, native permission rules, PreToolUse Hook, engineering rules, and remote access control. It also provides a deny/ask/allow configuration and command classification list to ensure the Agent operates autonomously within secure boundaries.

A Twitter thread clarifies the distinct roles of Skills, Subagents, MCP, and Hooks in AI agent design, arguing that confusing them leads to inefficient and costly systems.