guardrails

# Guardrails Verification gates that block the agent from proceeding until checks pass. The agent already knows what linting, testing, type checking, and security scanning are. This skill doesn't re-teach those concepts. Instead, it specifies: - **When** each check runs in the agent lifecycle (hooks that block progress) - **What to do when stuck** (diagnostic escalation instead of retrying) - **What not to touch** (config protection, high-risk action gating) - **How to accumulate knowledge** (lessons learned, agent tool library) These are the behaviors a coding agent wouldn't exhibit without being told. Everything else — which linter to use, how to structure a unit test — the agent already knows from training and discovers from the project's existing config. **Bundled resources:** `references/tool-building.md` contains the diagnostic tool and notation catalogs with worked examples. `references/language-defaults.md` is a lookup table for tool selection by ecosystem. Read these when directed, not proactively. --- ## Scope Not every check applies to every project. The common base applies everywhere: lint, format, types, SAST, dependency audit, secrets scan, dead/duplicate code detection, coverage, unit tests (tool lookup: `references/language-defaults.md`). Beyond that, add layers by project type: - **Backend / API:** integration tests. Usually: property-based, contract, performance. - **Frontend:** integration tests. Usually: screenshot, E2E, accessibility. - **Full-sta...