From Script Piles to a Reusable Snippet Library

Snippet Collections Rot Fast Without Rules

Most developers collect snippets over years, then stop trusting them because context is missing. A snippet library needs metadata, not just code blocks.

Step 1: Define a snippet contract

snippet:
  id: hide-desktop-macos
  language: applescript
  purpose: hide desktop icons temporarily
  tested_on: macos-14

Step 2: Include executable smoke checks

#!/usr/bin/env bash
set -euo pipefail

osascript snippets/hide-desktop.scpt --help >/dev/null || true

Step 3: Version snippets like product code

Track compatibility notes and deprecate stale snippets explicitly.

Pitfalls

• No runtime/platform metadata.
• No review date for stale automation scripts.
• Copy-paste snippets with hidden side effects.

Verification

• Each snippet has purpose + compatibility metadata.
• Automated smoke checks run in CI.
• Deprecated snippets are clearly marked and excluded from recommendations.