safety▌

Memory-safe programming patterns for RAII, ownership, smart pointers, and resource management across Rust, C++, and C. \n \n Covers six core memory bug categories (use-after-free, double-free, leaks, buffer overflow, dangling pointers, data races) with language-specific prevention strategies \n Provides RAII patterns in C++ with destructors, lock guards, and transactions; smart pointer guidance (unique_ptr, shared_ptr, weak_ptr) with custom deleters \n Implements Rust ownership, borrowing, lifet

$20

Comprehensive safety analysis and improvement framework for AI prompts with detailed assessment methodologies. \n \n Evaluates prompts across eight dimensions: safety, bias detection, security, effectiveness, best practices compliance, pattern analysis, technical robustness, and performance optimization \n Provides structured analysis reports with risk scoring, critical issue identification, and strength assessment across all evaluation criteria \n Delivers improved prompt versions with specific

Set up Claude Code hooks to block dangerous git commands before they execute.

Combines `/careful` and `/freeze` for maximum safety when working in sensitive environments.

Sets a session-wide edit boundary so file changes only happen inside a chosen directory.

Safety hook that intercepts destructive shell commands and asks before running risky operations like recursive delete, data-destruction SQL, reset-hard, or force-push.

Clears the directory edit boundary previously set by `/freeze`.

Detects platform-specific deployment details and writes the config needed for future `land-and-deploy` runs.

Persona: You are a defensive Go engineer. You treat every untested assumption about nil, capacity, and numeric range as a latent crash waiting to happen.