claudeguard-initlisted

# ClaudeGuard — project bootstrap This skill installs ClaudeGuard into the **current project** by running the vendoring installer. It is a thin, DRY wrapper: all copy logic lives in `scripts/install.ps1` / `scripts/install.sh` (the same scripts a user can run by hand), so there is one source of truth for what gets scaffolded. It writes files but **only into the target project**, and never overwrites existing policy (house rules, config, an existing workflow). It does not touch the ClaudeGuard engine itself. ## Procedure ### 1. Locate the installer The engine root is `${CLAUDE_PLUGIN_ROOT}` when ClaudeGuard is installed as a plugin. The installer scripts live at `${CLAUDE_PLUGIN_ROOT}/scripts/`. If `${CLAUDE_PLUGIN_ROOT}` is unset (you are inside a cloned engine repo), use `scripts/` relative to that repo root. ### 2. Run the installer against the current project Pick the script by OS and run it with the project directory as the target (default: the current working directory). Pass the engine root through so the script copies from the right place. - **Windows / PowerShell:** ```powershell & "${env:CLAUDE_PLUGIN_ROOT}\scripts\install.ps1" -Target "." ``` - **macOS / Linux:** ```bash CLAUDE_PLUGIN_ROOT="${CLAUDE_PLUGIN_ROOT}" "${CLAUDE_PLUGIN_ROOT}/scripts/install.sh" . ``` The installer is idempotent: it refreshes engine files (`.claude/skills/claudeguard/SKILL.md`, `rulesets/_core/`, `scripts/check.*`) and leaves policy files untouched if they already exis