skills/vibe-product/SKILL.md

---
name: vibe-product
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."
---

# Product & UX

Read [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.

## Recipes

| Recipe | Operation |
|---|---|
| [Form & Data UI Audit](references/form-data-ui-audit.md) | audit |
| [Form & Data UI Polish](references/form-data-ui-polish.md) | implement |
| [Onboarding Activation Audit](references/onboarding-activation-audit.md) | audit |
| [Onboarding Activation Polish](references/onboarding-activation-polish.md) | implement |
| [Product Acceptance Check](references/product-acceptance-check.md) | check |
| [Product Decision & Metrics Check](references/product-decision-metrics-check.md) | check |
| [Product Requirements Audit](references/product-requirements-audit.md) | audit |
| [Product Requirements Polish](references/product-requirements-polish.md) | implement |
| [Product UI Audit](references/product-ui-audit.md) | audit |
| [Product UI Polish](references/product-ui-polish.md) | implement |
| [UX Flow Audit](references/ux-flow-audit.md) | audit |
| [UX Flow Polish](references/ux-flow-polish.md) | implement |

For 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.