Tested hooks to catch .env edits, force pushes and server/client component mistakes. A CLAUDE.md template and three subagents for your Next.js App Router project.
Try the file-protection hook with seven offline checks. No email or checkout. Node 20+ on macOS/Linux; no dependencies. Read the setup instructions and limitations.
The free hook checks edit-style tools, not shell commands or reads; it is not a security boundary. The full workflow pack adds Bash checks, typechecking and Next.js boundary checks.
Setting up project instructions? Start with the free Next.js CLAUDE.md template.
Free Claude Code guides
Working in a Next.js App Router repo? Read a focused walkthrough before deciding whether you need the workflow pack. No signup required.
Hook troubleshooting
Separate a command that never ran from one that allowed the action. Check settings, tool matchers and input with a six-step checklist and free debugging sample.
Diagnose a hook that is not firing →Existing project
Keep your current configuration, merge hook entries, and check that the new hooks load.
Read the setup guide →File guardrails
See how edit hooks handle .env files and lockfiles, including what these checks cannot protect.
Read the file protection guide →App Router boundaries
Work through missing use client directives and server-only imports before they reach a build.
Read the component guide →Completion checks
Run a typecheck before completion. Try an offline Stop-hook harness and distinguish a passing check from a skipped or failed one.
Check types before calling it done →Shell command guardrails
Test a Bash hook against command strings without executing them. See why pattern checks still need permissions, review and backups.
Explore Bash checks and their limits →AI agent fleet governance
Autonomy tiers, QA gates, role templates and a failure-class catalogue. Choose the guide ($39) or the guide with a runnable Python scaffold ($79).
Explore the Playbook and free sample →