enforce-mode

enforce-mode

Automatic quality rules for Claude Code. Like a spell-checker, but for engineering best practices.

When you use Claude Code to write software, enforce-mode runs quietly in the background and nudges Claude toward good engineering habits — researching before coding, testing before shipping, never committing secrets, and following security best practices for your project type.

Think of it as a safety net that reminds Claude of the right thing to do at the right moment.

---

What Does It Do?

Without enforce-mode, Claude Code might:

• Write code without checking whether a library is up to date
• Skip tests and say "it should work"
• Accidentally commit an API key or password
• Miss security best practices

With enforce-mode, Claude is guided to:

• Research an API before using it
• Run tests and show the output
• Keep secrets out of commits
• Follow security patterns matched to your project type
• Earn a Ground Truth Confidence (GTC) score on every response

---

Installation

enforce-mode installs as a Claude Code plugin. Pick one of the two options below.

Option 1 — Plugin install (recommended)

Run these two commands inside Claude Code:

/plugin marketplace add Rutvik552k/enforce-mode
/plugin install enforce-mode@enforce-mode

The first command tells Claude Code where to find the plugin (this GitHub repo). The second installs it. After that it activates automatically on every session — no further setup.

Keep it up to date: open /plugin → Marketplaces tab → select enforce-mode → enable auto-update.

Option 2 — Manual install (no plugin system)

Use this if you prefer to wire the hooks into your ~/.claude/settings.json directly. You only need Node.js installed (the hooks are plain Node, zero dependencies).

Mac / Linux:

git clone https://github.com/Rutvik552k/enforce-mode.git
cd enforce-mode
bash hooks/install.sh

Windows (PowerShell):

git clone https://github.com/Rutvik552k/enforce-mode.git
cd enforce-mode
powershell -ExecutionPolicy Bypass -File hooks\install.ps1

The installer copies the hook scripts to ~/.claude/hooks/, the rules to ~/.claude/rules/, and registers everything in ~/.claude/settings.json. It is idempotent — safe to run again — and backs up your existing settings.json before changing it. Re-run with --force to reinstall.

To remove a manual install later, run /enforce-uninstall (or node hooks/enforce-uninstall.js), which removes only what the installer added.

---

How to Use

Once installed, enforce-mode runs automatically. No configuration needed.

Switch enforcement level

/enforce solo    # Light rules — solo prototyping
/enforce team    # Stricter — team projects
/enforce prod    # Full security stack — production code
/enforce off     # Turn it off

Or just say it in chat:

"stop enforce"   # turns it off
"normal mode"    # turns it off

The level you pick is remembered across sessions — set it once.

What each level does

Level	Best for	What it adds
solo	Personal projects, learning	Core rules: research before coding, test before shipping, no secrets
team	Shared codebases	+ documentation, parallel tasks, dependency tracking
prod	Production systems	+ full security audit, performance checks, monitoring rules

Set a project anchor (optional)

/enforce-init "<your goal>"

This detects your tech stack, captures your requirements, and writes a small managed block into your project's CLAUDE.md (between <!-- enforce-anchor:start/end --> markers — your own content is left untouched). Claude re-reads this anchor to stay on the goal as work progresses. When the goal, stack, or task list changes, the anchor is kept in sync.

---

What It Catches (Examples)