Update to Vibe Coding

{
  "description": "Audit or implement a selected product requirement, UI behavior, user journey, onboarding, form, or data table; verify acceptance and metric alignment against an existing repository.",
  "included_files": [
    {
      "relative_path": "agents/openai.yaml",
      "size_in_bytes": 199
    },
    {
      "relative_path": "references/form-data-ui-audit.md",
      "size_in_bytes": 1687
    },
    {
      "relative_path": "references/form-data-ui-polish.md",
      "size_in_bytes": 1231
    },
    {
      "relative_path": "references/onboarding-activation-audit.md",
      "size_in_bytes": 2655
    },
    {
      "relative_path": "references/onboarding-activation-polish.md",
      "size_in_bytes": 2462
    },
    {
      "relative_path": "references/product-acceptance-check.md",
      "size_in_bytes": 1141
    },
    {
      "relative_path": "references/product-decision-metrics-check.md",
      "size_in_bytes": 1178
    },
    {
      "relative_path": "references/product-requirements-audit.md",
      "size_in_bytes": 1558
    },
    {
      "relative_path": "references/product-requirements-polish.md",
      "size_in_bytes": 1954
    },
    {
      "relative_path": "references/product-ui-audit.md",
      "size_in_bytes": 1720
    },
    {
      "relative_path": "references/product-ui-polish.md",
      "size_in_bytes": 1174
    },
    {
      "relative_path": "references/ux-flow-audit.md",
      "size_in_bytes": 2991
    },
    {
      "relative_path": "references/ux-flow-polish.md",
      "size_in_bytes": 2329
    }
  ],
  "name": "vibe-product",
  "skill_md_contents": "---\nname: vibe-product\ndescription: \"Audit or implement a selected product requirement, UI behavior, user journey, onboarding, form, or data table; verify acceptance and metric alignment against an existing repository.\"\n---\n\n# Product & UX\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| [Form & Data UI Audit](references/form-data-ui-audit.md) | audit |\n| [Form & Data UI Polish](references/form-data-ui-polish.md) | implement |\n| [Onboarding Activation Audit](references/onboarding-activation-audit.md) | audit |\n| [Onboarding Activation Polish](references/onboarding-activation-polish.md) | implement |\n| [Product Acceptance Check](references/product-acceptance-check.md) | check |\n| [Product Decision & Metrics Check](references/product-decision-metrics-check.md) | check |\n| [Product Requirements Audit](references/product-requirements-audit.md) | audit |\n| [Product Requirements Polish](references/product-requirements-polish.md) | implement |\n| [Product UI Audit](references/product-ui-audit.md) | audit |\n| [Product UI Polish](references/product-ui-polish.md) | implement |\n| [UX Flow Audit](references/ux-flow-audit.md) | audit |\n| [UX Flow Polish](references/ux-flow-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"
}