← Vibe CodingCONTENT HISTORY

Update to Vibe Coding

Snapshot Sep 30, 2026 · 23:16 UTC · version 1.3.0

Collection source: not recorded for this historical snapshot.

WHAT CHANGED · RULE-BASED ANALYSIS

First saved snapshot

No earlier snapshot is available to establish a change.

Compare saved observations

Download comparison JSON
Full technical diff · 0 changed fields
Full snapshot data
{
  "description": "Audit or fix a concrete reliability, consistency, idempotency, concurrency, hot-path performance or resource-budget problem. Use current code and measurements to identify the limiting owner.",
  "included_files": [
    {
      "relative_path": "agents/openai.yaml",
      "size_in_bytes": 241
    },
    {
      "relative_path": "references/consistency-invariants-audit.md",
      "size_in_bytes": 3245
    },
    {
      "relative_path": "references/consistency-invariants-polish.md",
      "size_in_bytes": 1542
    },
    {
      "relative_path": "references/idempotency-concurrency-audit.md",
      "size_in_bytes": 1711
    },
    {
      "relative_path": "references/idempotency-concurrency-polish.md",
      "size_in_bytes": 1261
    },
    {
      "relative_path": "references/performance-audit.md",
      "size_in_bytes": 2955
    },
    {
      "relative_path": "references/performance-budget-audit.md",
      "size_in_bytes": 3185
    },
    {
      "relative_path": "references/performance-budget-polish.md",
      "size_in_bytes": 1185
    },
    {
      "relative_path": "references/performance-polish.md",
      "size_in_bytes": 1190
    },
    {
      "relative_path": "references/reliability-audit.md",
      "size_in_bytes": 3273
    },
    {
      "relative_path": "references/reliability-polish.md",
      "size_in_bytes": 2274
    },
    {
      "relative_path": "references/transactional-delivery-check.md",
      "size_in_bytes": 6054
    }
  ],
  "name": "vibe-reliability",
  "skill_md_contents": "---\nname: vibe-reliability\ndescription: \"Audit or fix a concrete reliability, consistency, idempotency, concurrency, hot-path performance or resource-budget problem. Use current code and measurements to identify the limiting owner.\"\n---\n\n# Reliability & performance\n\nRead [the shared workflow](../../references/workflow.md) once per task, then the one recipe matching the requested operation and boundary. Do not load every recipe. The user's request controls scope and whether edits are allowed.\n\n## Recipes\n\n| Recipe | Operation |\n|---|---|\n| [Transactional Delivery Check](references/transactional-delivery-check.md) | check |\n| [Consistency Invariants Audit](references/consistency-invariants-audit.md) | audit |\n| [Consistency Invariants Polish](references/consistency-invariants-polish.md) | implement |\n| [Idempotency & Concurrency Audit](references/idempotency-concurrency-audit.md) | audit |\n| [Idempotency & Concurrency Polish](references/idempotency-concurrency-polish.md) | implement |\n| [Performance Audit](references/performance-audit.md) | audit |\n| [Performance Budget Audit](references/performance-budget-audit.md) | audit |\n| [Performance Budget Polish](references/performance-budget-polish.md) | implement |\n| [Performance Polish](references/performance-polish.md) | implement |\n| [Reliability Audit](references/reliability-audit.md) | audit |\n| [Reliability Polish](references/reliability-polish.md) | implement |\n\nFor an explicit multi-stage request, follow the necessary stages without discarding requested work. For a single stage, deliver that result and stop. Use [the catalog](../../references/catalog.md) only if the requested boundary belongs elsewhere.\n\nUse Transactional Delivery Check for the database → event → consumer effect boundary. For a requested repair, use Consistency Invariants Polish with the same crash-window checks.\n"
}

SHA-256 of public snapshot: 48cc76412825eb983afc4878367bc54ec92890089a4b0ef3e64c62ef5c6938e0