Results for “guarddog”

AI safety and responsible AI practices

Post-execution skill crystallization and learning engine updates for WinDAGs. Runs after successful execution to update Thompson sampling parameters, track method quality, detect monster-barring, log near-miss events, and signal Kuhnian crises. Activate on "curator", "learning update", "skill crystallization", "Thompson sampling", "monster-barring", "near-miss", "Kuhnian crisis", "post-execution learning". NOT for pre-execution risk scanning (use windags-premortem), retrospective analysis (use windags-looking-back), or DAG construction (use windags-architect).

Datadog CLI for searching logs, querying metrics, tracing requests, and managing dashboards. Use this when debugging production issues or working with Datadog observability.

Derive owner/operator dogfood scenarios from product evidence and active-use cadence, then produce adoption instructions and manual evaluation checks

Prevents destructive operations on production systems and restricts file edits to a specific directory when running agents autonomously.

Search the web using DuckDuckGo and return top results

Keeps AI coding agents tightly scoped by enforcing minimal changes, simplest solutions, and asking before expanding scope or adding dependencies.

Provides production-grade NestJS architecture patterns for modules, controllers, providers, DTO validation, guards, interceptors, config, and testing.

Full safety mode: destructive command warnings + directory-scoped edits. Combines /careful (warns before rm -rf, DROP TABLE, force-push, etc.) with /freeze (blocks edits outside a specified directory). Use for maximum safety when touching prod or debugging live systems. Use when asked to "guard mode", "full safety", "lock it down", or "maximum safety". (gstack)

Builds security-focused full-stack web applications by implementing integrated frontend and backend components with layered security at every level, covering the complete stack from database to UI.

Validate monorepo lane specs before dispatch and verify integrated changes stay inside declared lane boundaries