← 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": "Run one bounded bug-finding probe in an unvisited backend, frontend, architecture or visual area. Fix one proven defect when requested, retain visible thread history, and stop after one primary area.",
  "included_files": [
    {
      "relative_path": "agents/openai.yaml",
      "size_in_bytes": 213
    },
    {
      "relative_path": "references/instant-architecture-probe.md",
      "size_in_bytes": 8945
    },
    {
      "relative_path": "references/instant-backend-probe.md",
      "size_in_bytes": 8386
    },
    {
      "relative_path": "references/instant-bug-fix-polish.md",
      "size_in_bytes": 6924
    },
    {
      "relative_path": "references/instant-frontend-probe.md",
      "size_in_bytes": 9096
    },
    {
      "relative_path": "references/instant-ui-ux-visual-probe.md",
      "size_in_bytes": 9919
    }
  ],
  "name": "vibe-probe",
  "skill_md_contents": "---\nname: vibe-probe\ndescription: \"Run one bounded bug-finding probe in an unvisited backend, frontend, architecture or visual area. Fix one proven defect when requested, retain visible thread history, and stop after one primary area.\"\n---\n\n# Quick bug discovery\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\nTrack primary areas and outcomes from **all** visible probes in this conversation. A repeated probe chooses a new owner/boundary; rereading consumers does not make them a new primary area. Explicit user targets take precedence over novelty: revisiting a named area to finish or verify a fix is allowed. Never claim memory of unseen tasks.\n\nUse architecture for dependency direction and ownership; backend for server runtime; frontend for client state/data flow; visual for presentation and accessibility. Do not hide a state bug with CSS. Generic bug probe is the fallback when no specific surface is selected.\n\nAfter the chosen area is fixed, clean, blocked or unavailable, report that area, owner, evidence and status. “Clean” applies only to that area. If context has been lost, state the coverage limit instead of inventing a visited ledger.\n\n## Recipes\n\n| Recipe | Operation |\n|---|---|\n| [Instant Architecture Probe](references/instant-architecture-probe.md) | probe |\n| [Instant Backend Probe](references/instant-backend-probe.md) | probe |\n| [Instant Bug Fix Polish](references/instant-bug-fix-polish.md) | probe |\n| [Instant Frontend Probe](references/instant-frontend-probe.md) | probe |\n| [Instant UI-UX Visual Probe](references/instant-ui-ux-visual-probe.md) | probe |\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"
}

SHA-256 of public snapshot: 041836be4891a89622b6a2e7a24d359fef7c510f6b630e68d97f1fbe3fcb3cca