Implement Memory Safety Patterns

Memory Safety Patterns is a skill covering cross-language patterns for memory-safe programming, including RAII (Resource Acquisition Is Initialization), ownership, smart pointers, and resource management. It works by clarifying the goals, constraints, and required inputs of the memory-management problem at hand, applying the relevant best practice, and providing actionable steps with verification; when a deeper worked example is needed it opens a separate resources/implementation-playbook.md for detailed patterns.

Use it when writing memory-safe systems code, managing resources such as files, sockets, or memory, preventing use-after-free bugs and leaks, implementing RAII patterns, choosing between languages on the basis of safety guarantees, or debugging a memory issue. It is not for tasks unrelated to memory safety, or for a different domain or tool outside this scope - and it explicitly stops to ask for clarification if required inputs, permissions, safety boundaries, or success criteria are missing, rather than guessing.

Input is the memory-management problem or resource-handling task at hand, including the target language(s) when a safety comparison is being made. Output is concrete, actionable steps with verification guidance, not a substitute for environment-specific validation, testing, or expert review.

Systems programmers and developers who need cross-language guidance on RAII, ownership, smart pointers, and resource management to prevent use-after-free bugs and leaks, or who are choosing between languages based on memory-safety guarantees.