setup-checklist

To configure Claude Code governance, use a guided setup checklist that applies best-practice settings, rules, and hooks across global or project scope. This ensures required files like settings.json and CLAUDE.md are present while explaining the rationale for each configuration choice.

Yes, you can audit your Claude Code configuration by running an audit mode that compares your current files against a machine-readable checklist. It reports missing or misaligned settings and offers targeted fixes one issue at a time, including warnings for deprecated environment variables.

Setting up Claude Code security hooks involves installing a guard script that blocks access to sensitive resources like .env files, SSH keys, and credentials. This sandboxing approach ensures security-minded defaults are enforced during project setup.

Yes, Claude Code setup supports both global machine configuration and per-project hygiene. You can choose between interactive global setup or project-specific setup with optional coding-governance rules applied locally.

Your Claude Code audit warns about deprecated Opus 4.6 environment variables because they are obsolete and no longer recommended. The audit mode detects these misaligned settings and offers targeted fixes to update your configuration.

The best way to add coding-governance rules is to run a project setup mode that applies governance configurations to your existing Claude Code environment. This guides you through enabling sandboxing, installing guard hooks, and aligning settings.json with best practices.