System Reference
How Wield works under the hood — the hooks that guard your session, the shared rules skills load at runtime, and how it all resolves.
System Reference
Beyond skills and agents, Wield ships a thin layer of infrastructure: hooks that guard your context and git state, and rules that several skills and agents load at runtime. This section documents both.
Hooks
Privacy and scout guards, plus session and uncommitted-change reminders — fail-open and silent without Node.
Rules
Shared engineering conventions: development rules, workflow, orchestration, and skill routing.
Configuration
The optional .wield.json reference and every supported key.
How it resolves
Wield's bundled scripts, hooks, and rules resolve wherever the plugin is
installed. Claude Code provides ${CLAUDE_PLUGIN_ROOT}; the shared hook wiring
falls back to Codex's PLUGIN_ROOT. You don't hard-code paths; skills and agents
load the shared rules at runtime.
The two guard hooks run through node-hook-runner.sh, which skips silently if
Node.js isn't installed. Wield never errors because Node is missing — it just
runs without the guards until Node is available.