Update to Vibe Coding

{
  "description": "Audit, fix or verify client query caches, optimistic mutations, event sequence gaps, WebSocket/SSE reconnect, persisted state and rendering cost in realtime UIs.",
  "included_files": [
    {
      "relative_path": "agents/openai.yaml",
      "size_in_bytes": 222
    },
    {
      "relative_path": "references/realtime-frontend-audit.md",
      "size_in_bytes": 3248
    },
    {
      "relative_path": "references/realtime-frontend-polish.md",
      "size_in_bytes": 1813
    },
    {
      "relative_path": "references/realtime-interface-profiling-recovery-check.md",
      "size_in_bytes": 1078
    }
  ],
  "name": "vibe-realtime",
  "skill_md_contents": "---\nname: vibe-realtime\ndescription: \"Audit, fix or verify client query caches, optimistic mutations, event sequence gaps, WebSocket/SSE reconnect, persisted state and rendering cost in realtime UIs.\"\n---\n\n# Realtime interfaces\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| [Realtime Frontend Audit](references/realtime-frontend-audit.md) | audit |\n| [Realtime Frontend Polish](references/realtime-frontend-polish.md) | implement |\n| [Realtime Interface Profiling & Recovery Check](references/realtime-interface-profiling-recovery-check.md) | check |\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\nShared cache invalidation belongs to [Cache](../vibe-cache/SKILL.md); initial server rendering and hydration belong to [Web](../vibe-web/SKILL.md). This skill owns client state reconciliation and reconnect.\n"
}