Start a fresh conversation. Replace the highlighted placeholders.
Use memory-safety-patterns to review [code or design] for memory-safety risks involving [resources], and provide actionable ownership, RAII, or resource-management changes plus verification guidance; ask before proceeding if safety boundaries or success criteria are unclear.
Required inputs
[code or design]
[resources]
User-approved starter prompt based on a pinned source version; check current skill requirements before running. Task evidence ↗
SKILL.md
name: memory-safety-patternsdescription: "Cross-language patterns for memory-safe programming including RAII, ownership, smart pointers, and resource management."risk: safesource: communitydate_added: "2026-02-27"
Memory Safety Patterns
Cross-language patterns for memory-safe programming including RAII, ownership, smart pointers, and resource management.
Use this skill when
Writing memory-safe systems code
Managing resources (files, sockets, memory)
Preventing use-after-free and leaks
Implementing RAII patterns
Choosing between languages for safety
Debugging memory issues
Do not use this skill when
The task is unrelated to memory safety patterns
You need a different domain or tool outside this scope
Instructions
Clarify goals, constraints, and required inputs.
Apply relevant best practices and validate outcomes.
Provide actionable steps and verification.
If detailed examples are required, open resources/implementation-playbook.md.
Resources
resources/implementation-playbook.md for detailed patterns and examples.
Limitations
Use this skill only when the task clearly matches the scope described above.
Do not treat the output as a substitute for environment-specific validation, testing, or expert review.
Stop and ask for clarification if required inputs, permissions, safety boundaries, or success criteria are missing.