Vibe Coding

View saved version →

---
name: vibe
description: "Use Vibe Coding when the user explicitly invokes the plugin without choosing a specialized skill, asks what it can do, or requests help choosing a workflow. Route by requested outcome and domain; do not trigger for every coding task."
---

# Vibe Coding

Choose the smallest suitable workflow from the user's requested outcome. Use [the shared workflow](../../references/workflow.md) once, then read the selected skill and recipe. Normal implementation should go directly to its target; do not force a preliminary map, audit or plan.

| Request | Start here |
|---|---|
| Explain or map the repository | [Map](../vibe-map/SKILL.md) |
| Shape a task, combine findings, plan several slices | [Task](../vibe-task/SKILL.md) |
| Review a patch or fix review defects | [Review](../vibe-review/SKILL.md) |
| Find and fix one new bug | [Probe](../vibe-probe/SKILL.md) |
| Check tests or release readiness | [Quality](../vibe-quality/SKILL.md) |
| MCP protocol, tool contracts or transport authorization | [MCP](../vibe-mcp/SKILL.md) |
| SSR, hydration, serialized data or server actions | [Web rendering](../vibe-web/SKILL.md) |
| Serverless invocation lifetime, duplicate triggers or edge limits | [Serverless](../vibe-serverless/SKILL.md) |
| Named domain, framework or infrastructure | [Domain catalog](../../references/catalog.md) |
| Check stale maps or maintain this package | [Workflow](../vibe-workflow/SKILL.md) |

Infer audit/implementation/check from the user's verbs and available context. Ask only for missing information that changes the result. If asked to audit and fix, continue to the authorized correction and verification. An audit-only request ends with findings. Do not spawn tasks, delegate or promise background work simply because a recipe mentions orchestration.

The optional [cycles](../../references/cycles.md) explain handoffs for genuinely multi-stage work. They are not a required ritual for every task.

Referenced files: 1

View saved version →

---
name: vibe-ai
description: "Frame, audit or improve an existing AI feature, RAG pipeline, OCR flow, agent tools, ML pipeline, evaluation, model serving or AI governance. Select the actual model/data/tool boundary."
---

# AI, RAG & ML

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 |
|---|---|
| [AI Evaluation Audit](references/ai-evaluation-audit.md) | audit |
| [AI Evaluation Polish](references/ai-evaluation-polish.md) | implement |
| [AI Feature Audit](references/ai-feature-audit.md) | audit |
| [AI Feature Polish](references/ai-feature-polish.md) | implement |
| [AI ML Problem Framing](references/ai-ml-problem-framing.md) | plan |
| [AI Safety & Governance Audit](references/ai-safety-governance-audit.md) | audit |
| [AI Safety & Governance Polish](references/ai-safety-governance-polish.md) | implement |
| [LLM Agent Tools Audit](references/llm-agent-tools-audit.md) | audit |
| [LLM Agent Tools Polish](references/llm-agent-tools-polish.md) | implement |
| [ML Pipeline Audit](references/ml-pipeline-audit.md) | audit |
| [ML Pipeline Polish](references/ml-pipeline-polish.md) | implement |
| [Model Serving & Monitoring Audit](references/model-serving-monitoring-audit.md) | audit |
| [Model Serving & Monitoring Polish](references/model-serving-monitoring-polish.md) | implement |
| [OCR Document AI Audit](references/ocr-document-ai-audit.md) | audit |
| [OCR Document AI Polish](references/ocr-document-ai-polish.md) | implement |
| [RAG Audit](references/rag-audit.md) | audit |
| [RAG Polish](references/rag-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.

Use [MCP](../vibe-mcp/SKILL.md) for protocol/transport conformance and [Harness](../vibe-harness/SKILL.md) for durable execution/checkpoint recovery. This skill owns model decisions, grounding and tool-selection quality.

For a verification-only request, apply the relevant audit recipe to the stated acceptance criteria and report the measured result and gaps. Verification alone does not authorize implementation; a separate check recipe is not required.

Referenced files: 18

View saved version →

---
name: vibe-backend
description: "Audit or fix API contracts and conversational bot flows in an existing repository, including validation, state transitions, callbacks, permissions, and direct consumers."
---

# APIs & bots

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 |
|---|---|
| [API Contract Evolution Audit](references/api-contract-evolution-audit.md) | audit |
| [API Contract Evolution Polish](references/api-contract-evolution-polish.md) | implement |
| [API Contract Compatibility Check](references/api-contract-compatibility-check.md) | check |
| [API Audit](references/api-audit.md) | audit |
| [API Polish](references/api-polish.md) | implement |
| [Bot Audit](references/bot-audit.md) | audit |
| [Bot Polish](references/bot-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.

For an old/new schema or generated-client compatibility boundary, select the API Contract Evolution recipes. A general endpoint behavior audit still uses API Audit.

Referenced files: 8

View saved version →

---
name: vibe-cache
description: "Audit, fix or verify cache keys, invalidation, TTL, stale reads and coherency across authoritative writes and readers. Focus on cache correctness rather than Redis queue semantics."
---

# Caching & freshness

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 |
|---|---|
| [Cache Coherency Check](references/cache-coherency-check.md) | check |
| [Cache Invalidation Audit](references/cache-invalidation-audit.md) | audit |
| [Cache Invalidation Polish](references/cache-invalidation-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.

Client optimistic state and reconnect belong to [Realtime](../vibe-realtime/SKILL.md); server rendering and serialized responses belong to [Web](../vibe-web/SKILL.md). This skill owns shared cache identity, invalidation and freshness.

Referenced files: 4

View saved version →

---
name: vibe-celery
description: "Audit, fix or verify Celery task publication, acknowledgements, retries, time limits, prefetch, schedules and warm/cold shutdown against the actual broker and pool."
---

# Celery

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 |
|---|---|
| [Celery Delivery & Shutdown Check](references/celery-delivery-shutdown-check.md) | check |
| [Celery Workers Audit](references/celery-workers-audit.md) | audit |
| [Celery Workers Polish](references/celery-workers-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.

Referenced files: 4

View saved version →

---
name: vibe-clickhouse
description: "Audit, fix or verify ClickHouse table engines, partition/order keys, ingestion deduplication, query pruning, merges, replication and workload limits."
---

# ClickHouse

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 |
|---|---|
| [ClickHouse Audit](references/clickhouse-audit.md) | audit |
| [ClickHouse Ingestion & Query Load Check](references/clickhouse-ingestion-query-load-check.md) | check |
| [ClickHouse Polish](references/clickhouse-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.

Referenced files: 4

View saved version →

---
name: vibe-compatibility
description: "Audit, implement or verify a compatibility boundary through authorized reference behavior, file/protocol reconstruction, differential comparison and golden masters."
---

# Compatibility & protocols

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 |
|---|---|
| [Compatibility Golden Master Check](references/compatibility-golden-master-check.md) | check |
| [Reverse Engineering Audit](references/reverse-engineering-audit.md) | audit |
| [Reverse Engineering Polish](references/reverse-engineering-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.

Referenced files: 4

View saved version →

---
name: vibe-content
description: "Audit or edit repository-owned product copy, notification templates, localization, or public SEO/GEO metadata. Ground claims and calls to action in implemented capabilities."
---

# Copy, localization & SEO

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 |
|---|---|
| [Localization Audit](references/localization-audit.md) | audit |
| [Localization Polish](references/localization-polish.md) | implement |
| [Notification Content Audit](references/notification-content-audit.md) | audit |
| [Notification Content Polish](references/notification-content-polish.md) | implement |
| [Product & Landing Copy Audit](references/product-landing-copy-audit.md) | audit |
| [Product & Landing Copy Polish](references/product-landing-copy-polish.md) | implement |
| [SEO GEO Audit](references/seo-geo-audit.md) | audit |
| [SEO GEO Polish](references/seo-geo-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.

Referenced files: 9

View saved version →

---
name: vibe-design
description: "Audit or fix an existing design system or accessible interaction: tokens, shared components, keyboard, focus, semantics and responsive states. Use for design implementation work grounded in code and rendered evidence."
---

# Design & accessibility

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 |
|---|---|
| [Accessibility Audit](references/accessibility-audit.md) | audit |
| [Accessibility Polish](references/accessibility-polish.md) | implement |
| [Design System Audit](references/design-system-audit.md) | audit |
| [Design System Polish](references/design-system-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.

Referenced files: 5

View saved version →

---
name: vibe-desktop
description: "Audit, fix or verify browser extensions or desktop applications: IPC/messaging, permission boundaries, local storage, reload/update, native integration and packaging."
---

# Desktop & extensions

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 |
|---|---|
| [Browser Extension Audit](references/browser-extension-audit.md) | audit |
| [Browser Extension Polish](references/browser-extension-polish.md) | implement |
| [Desktop App Audit](references/desktop-app-audit.md) | audit |
| [Desktop App Polish](references/desktop-app-polish.md) | implement |
| [Local Client Runtime Security Check](references/local-client-runtime-security-check.md) | check |

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.

Referenced files: 6

View saved version →

---
name: vibe-docs
description: "Generate evidence-backed README or design documentation, synchronize stale docs, or plan and implement a scoped migration/refactor. Preserve source ownership and existing compatibility."
---

# Documentation & refactoring

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 |
|---|---|
| [DESIGN GEN](references/design-gen.md) | document |
| [Documentation Sync Audit](references/documentation-sync-audit.md) | audit |
| [Documentation Sync Polish](references/documentation-sync-polish.md) | implement |
| [Migration & Refactor Plan](references/migration-refactor-plan.md) | plan |
| [README GEN](references/readme-gen.md) | document |
| [Refactor Boundary Audit](references/refactor-boundary-audit.md) | audit |
| [Refactor Boundary Polish](references/refactor-boundary-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.

Referenced files: 8

View saved version →

---
name: vibe-domain
description: "Audit, fix or verify repository business contracts: authentication and OAuth/OIDC sessions, RBAC/ABAC, tenant isolation, billing, data models, pipelines, notebook productionization, experiments and product analytics."
---

# Permissions, data & business rules

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.

For OAuth/OIDC verification, select the session check. For a requested authentication fix, use Auth Permissions Polish and apply the relevant protocol checks during verification.

## Recipes

| Recipe | Operation |
|---|---|
| [Auth Permissions Audit](references/auth-permissions-audit.md) | audit |
| [Auth Permissions Polish](references/auth-permissions-polish.md) | implement |
| [Billing Entitlements Audit](references/billing-entitlements-audit.md) | audit |
| [Billing Entitlements Polish](references/billing-entitlements-polish.md) | implement |
| [Data Model Audit](references/data-model-audit.md) | audit |
| [Data Model Polish](references/data-model-polish.md) | implement |
| [Data Pipeline & Quality Audit](references/data-pipeline-quality-audit.md) | audit |
| [Data Pipeline & Quality Polish](references/data-pipeline-quality-polish.md) | implement |
| [Experiment Design Audit](references/experiment-design-audit.md) | audit |
| [Experiment Design Polish](references/experiment-design-polish.md) | implement |
| [Multi Tenant Isolation Audit](references/multi-tenant-isolation-audit.md) | audit |
| [Multi Tenant Isolation Polish](references/multi-tenant-isolation-polish.md) | implement |
| [OAuth OIDC Session Check](references/oauth-oidc-session-check.md) | check |
| [Notebook Productionization Audit](references/notebook-productionization-audit.md) | audit |
| [Notebook Productionization Polish](references/notebook-productionization-polish.md) | implement |
| [Product Analytics Audit](references/product-analytics-audit.md) | audit |
| [Product Analytics Polish](references/product-analytics-polish.md) | implement |
| [RBAC ABAC Matrix Check](references/rbac-abac-matrix-check.md) | check |
| [RBAC ABAC Policy Audit](references/rbac-abac-policy-audit.md) | audit |
| [RBAC ABAC Policy Polish](references/rbac-abac-policy-polish.md) | implement |
| [Tenant Isolation Check](references/tenant-isolation-check.md) | check |

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.

For provider requests, signed webhooks and external payment reconciliation, use [Payments](../vibe-payments/SKILL.md). Local plan/role/entitlement policy remains here.

Referenced files: 22

View saved version →

---
name: vibe-flags
description: "Audit, fix or verify feature flag defaults, targeting, backend/UI enforcement, exposure events, kill switches and removal ownership."
---

# Feature flags & rollouts

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 |
|---|---|
| [Feature Flag Exposure & Rollback Check](references/feature-flag-exposure-rollback-check.md) | check |
| [Feature Flags Rollout Audit](references/feature-flags-rollout-audit.md) | audit |
| [Feature Flags Rollout Polish](references/feature-flags-rollout-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.

Referenced files: 4

View saved version →

---
name: vibe-go-rust
description: "Audit, fix or verify Go goroutine or Rust async task ownership, cancellation, pools, backpressure, errors and ordered service shutdown."
---

# Go & Rust services

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 |
|---|---|
| [Go Rust Concurrency & Shutdown Check](references/go-rust-concurrency-shutdown-check.md) | check |
| [Go Rust Microservices Audit](references/go-rust-microservices-audit.md) | audit |
| [Go Rust Microservices Polish](references/go-rust-microservices-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.

Referenced files: 4

View saved version →

---
name: vibe-harness
description: "Audit, fix or verify agent harness state machines, checkpoint/resume, bounded fan-out, cancellation, durable side effects and replay. This concerns application orchestration code, not creating assistant tasks."
---

# Agent execution

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 |
|---|---|
| [Agent Harness Audit](references/agent-harness-audit.md) | audit |
| [Agent Harness Polish](references/agent-harness-polish.md) | implement |
| [Agent Harness Replay & Failure Check](references/agent-harness-replay-failure-check.md) | check |

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.

Model selection, grounding and tool-choice quality belong to [AI](../vibe-ai/SKILL.md); wire protocol/tool discovery belongs to [MCP](../vibe-mcp/SKILL.md). This skill owns durable run state and side-effect recovery.

Referenced files: 4

View saved version →

---
name: vibe-integrations
description: "Audit, fix or verify outbound clients, deadlines, retries, trusted proxies, TLS, webhooks and server WebSocket/SSE lifecycle under bounded failure scenarios."
---

# Integrations & networking

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 |
|---|---|
| [Backend Integrations Audit](references/backend-integrations-audit.md) | audit |
| [Backend Integrations Polish](references/backend-integrations-polish.md) | implement |
| [Network Integration Failure Check](references/network-integration-failure-check.md) | check |

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.

Referenced files: 4

View saved version →

---
name: vibe-kafka
description: "Audit, fix or verify Kafka/Redpanda ordering, producer guarantees, consumer offsets, rebalances, schema compatibility, retry and replay boundaries."
---

# Kafka & Redpanda

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 |
|---|---|
| [Kafka Redpanda Audit](references/kafka-redpanda-audit.md) | audit |
| [Kafka Redpanda Polish](references/kafka-redpanda-polish.md) | implement |
| [Kafka Redpanda Rebalance & Failure Check](references/kafka-redpanda-rebalance-failure-check.md) | check |

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.

Referenced files: 4

View saved version →

---
name: vibe-kubernetes
description: "Audit, fix or verify Kubernetes workload rendering, rollout, probes, scheduling, storage, network policy and graceful shutdown for the actual target environment."
---

# Kubernetes

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 |
|---|---|
| [Kubernetes Platform Audit](references/kubernetes-platform-audit.md) | audit |
| [Kubernetes Platform Polish](references/kubernetes-platform-polish.md) | implement |
| [Kubernetes Rollout & Failure Check](references/kubernetes-rollout-failure-check.md) | check |

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.

Referenced files: 4

View saved version →

---
name: vibe-map
description: "Create or refresh evidence-backed repository maps of product capabilities, navigation, owners, data, runtime, permissions, tests, and releases. Use for understanding a codebase or explicitly requested maps."
---

# Project mapping

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 |
|---|---|
| [AI Navigation Map](references/ai-navigation-map.md) | map |
| [API Navigation Map](references/api-navigation-map.md) | map |
| [Auth Entitlements Map](references/auth-entitlements-map.md) | map |
| [Bot Navigation Map](references/bot-navigation-map.md) | map |
| [Domain Data Map](references/domain-data-map.md) | map |
| [Integration Map](references/integration-map.md) | map |
| [Ownership & Invariant Map](references/ownership-invariant-map.md) | map |
| [Product Capability Map](references/product-capability-map.md) | map |
| [Product Journey Map](references/product-journey-map.md) | map |
| [Product Metrics Events Map](references/product-metrics-events-map.md) | map |
| [Product Requirements Map](references/product-requirements-map.md) | map |
| [Project Atlas Map](references/project-atlas-map.md) | map |
| [RBAC ABAC Policy Map](references/rbac-abac-policy-map.md) | map |
| [Risk & Release Map](references/risk-release-map.md) | map |
| [Runtime Flow Map](references/runtime-flow-map.md) | map |
| [SaaS Navigation Map](references/saas-navigation-map.md) | map |
| [Test Coverage Map](references/test-coverage-map.md) | map |
| [Traceability Map](references/traceability-map.md) | map |

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.

Referenced files: 19

View saved version →

---
name: vibe-mcp
description: "Audit, fix or verify an MCP server or client: protocol-version compatibility, tool schemas/results, transport, discovery and authorization. Use for MCP integration defects; general agent planning and RAG belong to vibe-ai."
---

# MCP servers & clients

Read [the shared workflow](../../references/workflow.md) once, then the recipe matching the user's operation. The target is an existing MCP implementation or an explicitly requested MCP contract, not installation of arbitrary servers.

| Request | Recipe |
|---|---|
| Inspect a server/client contract without edits | [MCP Server Audit](references/mcp-server-audit.md) |
| Fix or implement a named contract | [MCP Server Polish](references/mcp-server-polish.md) |
| Verify protocol, tool results or authorization | [MCP Protocol & Authorization Check](references/mcp-protocol-auth-check.md) |

The recipes share [version and trust boundaries](../../references/mcp-contract.md). Select the repository's supported SDK/protocol version before applying a rule. Do not treat an optional feature or a newer specification as an automatic migration requirement. An audit-and-fix request includes the correction and meaningful verification.

Durable application execution belongs to [Harness](../vibe-harness/SKILL.md); model tool-choice quality belongs to [AI](../vibe-ai/SKILL.md). Keep protocol compliance separate from those concerns.

Referenced files: 4

View saved version →

---
name: vibe-mobile
description: "Audit, fix or verify mobile navigation, offline/sync, secure storage, platform permissions, deep links and release configuration for the changed feature."
---

# Mobile apps

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 |
|---|---|
| [Mobile App Audit](references/mobile-app-audit.md) | audit |
| [Mobile App Polish](references/mobile-app-polish.md) | implement |
| [Mobile Release & Offline Check](references/mobile-release-offline-check.md) | check |

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.

Referenced files: 4

View saved version →

---
name: vibe-nosql
description: "Audit, fix or verify engine-specific NoSQL keys, conditional writes, atomicity, indexes, hot partitions, TTL, change streams and failover."
---

# NoSQL

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 |
|---|---|
| [NoSQL Consistency & Hot Partition Check](references/nosql-consistency-hot-partition-check.md) | check |
| [NoSQL Databases Audit](references/nosql-databases-audit.md) | audit |
| [NoSQL Databases Polish](references/nosql-databases-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.

Referenced files: 4

View saved version →

---
name: vibe-notifications
description: "Audit, fix or verify notification eligibility, consent, templates, queues, provider status, retry deduplication and delivery recovery. Code work is not authorization to contact real recipients."
---

# Notification delivery

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 |
|---|---|
| [Notification Delivery Audit](references/notification-delivery-audit.md) | audit |
| [Notification Delivery Polish](references/notification-delivery-polish.md) | implement |
| [Notification Failure & Idempotency Check](references/notification-failure-idempotency-check.md) | check |

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.

Referenced files: 4

View saved version →

---
name: vibe-observability
description: "Audit, fix or verify Prometheus, Grafana or VictoriaLogs signal semantics, alert rules, dashboards, correlation, tenant scope and cardinality costs in a repository."
---

# Metrics, logs & alerts

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 |
|---|---|
| [Observability Semantics & Cost Check](references/observability-semantics-cost-check.md) | check |
| [Observability Stack Audit](references/observability-stack-audit.md) | audit |
| [Observability Stack Polish](references/observability-stack-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.

Referenced files: 4

View saved version →

---
name: vibe-ops
description: "Audit or fix runtime configuration, background jobs and CI/CD in a repository. Bootstrap deployment files only for a requested and evidenced deployment target; do not choose a provider by default."
---

# Infrastructure & background jobs

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 |
|---|---|
| [Incident Triage Audit](references/incident-triage-audit.md) | audit |
| [Incident Remediation Polish](references/incident-remediation-polish.md) | implement |
| [Incident Recovery Check](references/incident-recovery-check.md) | check |
| [Background Jobs Audit](references/background-jobs-audit.md) | audit |
| [Background Jobs Polish](references/background-jobs-polish.md) | implement |
| [Deploy Bootstrap](references/deploy-bootstrap.md) | implement |
| [Infra Ops Audit](references/infra-ops-audit.md) | audit |
| [Infra Ops Polish](references/infra-ops-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.

For an observed outage or regression, use incident triage, remediation or recovery check according to the requested action. Alert semantics belong to [Observability](../vibe-observability/SKILL.md); restore/rollback machinery to [Recovery](../vibe-recovery/SKILL.md).

Referenced files: 9

View saved version →

---
name: vibe-payments
description: "Audit, fix or verify payment provider adapters, signed webhooks, idempotency, event ordering, reconciliation and entitlement consistency. Use sandbox fixtures for payment scenarios."
---

# Payments

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 |
|---|---|
| [Payments Provider Audit](references/payments-provider-audit.md) | audit |
| [Payments Provider Polish](references/payments-provider-polish.md) | implement |
| [Payments Webhook & Reconciliation Check](references/payments-webhook-reconciliation-check.md) | check |

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.

For a local plan/role/entitlement policy without a provider-runtime defect, use [Domain](../vibe-domain/SKILL.md). Follow the actual failing owner when both boundaries participate.

Referenced files: 4

View saved version →

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

# Quick bug discovery

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.

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

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

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

## Recipes

| Recipe | Operation |
|---|---|
| [Instant Architecture Probe](references/instant-architecture-probe.md) | probe |
| [Instant Backend Probe](references/instant-backend-probe.md) | probe |
| [Instant Bug Fix Polish](references/instant-bug-fix-polish.md) | probe |
| [Instant Frontend Probe](references/instant-frontend-probe.md) | probe |
| [Instant UI-UX Visual Probe](references/instant-ui-ux-visual-probe.md) | probe |

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.

Referenced files: 6

View saved version →

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

Referenced files: 13

View saved version →

---
name: vibe-quality
description: "Audit test coverage or release readiness, improve an existing test harness, or verify visual regressions. For review of a concrete diff use vibe-review."
---

# Quality & readiness

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.

This covers verification quality and release assessment. It does not grant release/deployment permission. A visual result needs rendered evidence; code inspection alone is not visual verification.

## Recipes

| Recipe | Operation |
|---|---|
| [Release Readiness Audit](references/release-readiness-audit.md) | audit |
| [Test Coverage Audit](references/test-coverage-audit.md) | audit |
| [Test Harness Polish](references/test-harness-polish.md) | implement |
| [Visual Regression Check](references/visual-regression-check.md) | check |

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.

Referenced files: 5

View saved version →

---
name: vibe-rabbitmq
description: "Audit, fix or verify RabbitMQ topology, confirms, routing, acknowledgements, prefetch, dead lettering, connection ownership and redelivery recovery."
---

# RabbitMQ

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 |
|---|---|
| [RabbitMQ Audit](references/rabbitmq-audit.md) | audit |
| [RabbitMQ Polish](references/rabbitmq-polish.md) | implement |
| [RabbitMQ Redelivery & Recovery Check](references/rabbitmq-redelivery-recovery-check.md) | check |

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.

Referenced files: 4

View saved version →

---
name: vibe-realtime
description: "Audit, fix or verify client query caches, optimistic mutations, event sequence gaps, WebSocket/SSE reconnect, persisted state and rendering cost in realtime UIs."
---

# Realtime interfaces

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 |
|---|---|
| [Realtime Frontend Audit](references/realtime-frontend-audit.md) | audit |
| [Realtime Frontend Polish](references/realtime-frontend-polish.md) | implement |
| [Realtime Interface Profiling & Recovery Check](references/realtime-interface-profiling-recovery-check.md) | check |

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.

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

Referenced files: 4

View saved version →

---
name: vibe-recovery
description: "Audit, fix or verify artifact provenance, release promotion, rollback compatibility, backup integrity and disaster recovery. Restore and failure drills require an appropriate authorized environment."
---

# Delivery & recovery

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 |
|---|---|
| [Release Artifact Trust Check](references/release-artifact-trust-check.md) | check |
| [Delivery Recovery Audit](references/delivery-recovery-audit.md) | audit |
| [Delivery Recovery Polish](references/delivery-recovery-polish.md) | implement |
| [Delivery Restore & Rollback Check](references/delivery-restore-rollback-check.md) | check |

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.

Use Release Artifact Trust Check for source/build/published-byte identity. Repair of CI trust or dependency execution belongs to [Security](../vibe-security/SKILL.md).

Referenced files: 5

View saved version →

---
name: vibe-redis
description: "Audit, fix or verify Redis Streams, BullMQ or ARQ job identity, locks, acknowledgements, retention, backpressure and recovery. Respect the selected framework delivery semantics."
---

# Redis & queues

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 |
|---|---|
| [Redis Job Queues Audit](references/redis-job-queues-audit.md) | audit |
| [Redis Job Queues Polish](references/redis-job-queues-polish.md) | implement |
| [Redis Queue Load & Recovery Check](references/redis-queue-load-recovery-check.md) | check |

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.

Referenced files: 4

View saved version →

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

# Reliability & performance

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 |
|---|---|
| [Transactional Delivery Check](references/transactional-delivery-check.md) | check |
| [Consistency Invariants Audit](references/consistency-invariants-audit.md) | audit |
| [Consistency Invariants Polish](references/consistency-invariants-polish.md) | implement |
| [Idempotency & Concurrency Audit](references/idempotency-concurrency-audit.md) | audit |
| [Idempotency & Concurrency Polish](references/idempotency-concurrency-polish.md) | implement |
| [Performance Audit](references/performance-audit.md) | audit |
| [Performance Budget Audit](references/performance-budget-audit.md) | audit |
| [Performance Budget Polish](references/performance-budget-polish.md) | implement |
| [Performance Polish](references/performance-polish.md) | implement |
| [Reliability Audit](references/reliability-audit.md) | audit |
| [Reliability Polish](references/reliability-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.

Use Transactional Delivery Check for the database → event → consumer effect boundary. For a requested repair, use Consistency Invariants Polish with the same crash-window checks.

Referenced files: 12

View saved version →

---
name: vibe-review
description: "Review an explicit patch, PR, branch or working-tree delta and its direct contract dependencies. Default to findings only; fix review defects when requested. Use for patch review, not whole-repository audits."
---

# Change review

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 |
|---|---|
| [Patch Checking](references/patch-checking.md) | review |

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.

Referenced files: 2

View saved version →

---
name: vibe-search
description: "Audit, fix or verify document indexing, search ACLs, freshness, ranking/filter behavior, reindexing and failure recovery against product expectations."
---

# Search indexes

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 |
|---|---|
| [Search Index Audit](references/search-index-audit.md) | audit |
| [Search Index Polish](references/search-index-polish.md) | implement |
| [Search Recall & Freshness Check](references/search-recall-freshness-check.md) | check |

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.

Referenced files: 4

View saved version →

---
name: vibe-security
description: "Audit, fix or verify a requested application security, abuse-defense, privacy/data-rights or audit-log boundary using reachable evidence. Do not run a broad security audit for ordinary edits."
---

# Security & privacy

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 |
|---|---|
| [Build Supply Chain Audit](references/build-supply-chain-audit.md) | audit |
| [Build Supply Chain Polish](references/build-supply-chain-polish.md) | implement |
| [Audit Logging Compliance Audit](references/audit-logging-compliance-audit.md) | audit |
| [Audit Logging Compliance Polish](references/audit-logging-compliance-polish.md) | implement |
| [Audit Trail Integrity Check](references/audit-trail-integrity-check.md) | check |
| [Privacy Data Rights Audit](references/privacy-data-rights-audit.md) | audit |
| [Privacy Data Rights Check](references/privacy-data-rights-check.md) | check |
| [Privacy Data Rights Polish](references/privacy-data-rights-polish.md) | implement |
| [Security Abuse Defense Check](references/security-abuse-defense-check.md) | check |
| [Security Audit](references/security-audit.md) | audit |
| [Security Polish](references/security-polish.md) | implement |
| [System Security Hardening Audit](references/system-security-hardening-audit.md) | audit |
| [System Security Hardening Polish](references/system-security-hardening-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.

Build Supply Chain owns untrusted inputs, dependency execution and CI privileges. Verification of an already built artifact belongs to [Recovery](../vibe-recovery/SKILL.md).

Referenced files: 14

View saved version →

---
name: vibe-serverless
description: "Audit, fix or verify serverless and edge invocation lifetime, duplicate events, environment reuse and provider runtime limits. Use for existing Lambda/Workers or similar runtime defects; SSR/hydration belongs to vibe-web."
---

# Serverless & edge

Read [the shared workflow](../../references/workflow.md) once, then the recipe matching the operation. Establish the provider, trigger and runtime configuration before selecting checks.

| Request | Recipe |
|---|---|
| Inspect invocation and side-effect ownership | [Serverless Runtime Audit](references/serverless-runtime-audit.md) |
| Repair an evidenced runtime boundary | [Serverless Runtime Polish](references/serverless-runtime-polish.md) |
| Verify completion, reuse or redelivery | [Serverless Invocation Check](references/serverless-invocation-check.md) |

Use [runtime boundaries](../../references/serverless-runtime.md) for the actual provider. Rendering/serialization belongs to [Web](../vibe-web/SKILL.md), provisioning plans to [Terraform](../vibe-terraform/SKILL.md). Do not create a cloud deployment to inspect existing code.

Referenced files: 4

View saved version →

---
name: vibe-sql
description: "Audit, fix or verify SQL queries, indexes, locks, transactions, migration compatibility, connection pools, replica consistency and failover against the selected engine."
---

# SQL & connections

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 |
|---|---|
| [SQL Databases Audit](references/sql-databases-audit.md) | audit |
| [SQL Databases Polish](references/sql-databases-polish.md) | implement |
| [SQL Load Lock & Failover Check](references/sql-load-lock-failover-check.md) | check |

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.

Referenced files: 4

View saved version →

---
name: vibe-storage
description: "Audit, fix or verify object storage authorization, key/version identity, multipart uploads, checksums, presigned URLs, lifecycle and restore."
---

# Object storage

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 |
|---|---|
| [Object Storage Audit](references/object-storage-audit.md) | audit |
| [Object Storage Integrity & Recovery Check](references/object-storage-integrity-recovery-check.md) | check |
| [Object Storage Polish](references/object-storage-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.

Referenced files: 4

View saved version →

---
name: vibe-task
description: "Shape implementation tasks, validate scope, reconcile findings, decompose large objectives, or close an iteration. Use for requested planning and synthesis, not as a mandatory step before every edit."
---

# Tasks & synthesis

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 |
|---|---|
| [Evolution & Improvement](references/evolution-improvement.md) | plan |
| [Iteration Closure](references/iteration-closure.md) | closure |
| [Map Synthesis](references/map-synthesis.md) | plan |
| [Synthesis](references/synthesis.md) | plan |
| [Task Shaping](references/task-shaping.md) | plan |
| [Validation & Clarification](references/validation-clarification.md) | plan |
| [Workstream Decomposition](references/workstream-decomposition.md) | plan |

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.

Referenced files: 8

View saved version →

---
name: vibe-temporal
description: "Audit, fix or verify Temporal workflow determinism, Activities, signal/update handling, history bounds, replay and worker version compatibility."
---

# Temporal

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 |
|---|---|
| [Temporal Replay & Versioning Check](references/temporal-replay-versioning-check.md) | check |
| [Temporal Workflows Audit](references/temporal-workflows-audit.md) | audit |
| [Temporal Workflows Polish](references/temporal-workflows-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.

Referenced files: 4

View saved version →

---
name: vibe-terraform
description: "Audit, fix or verify Terraform module contracts, exact plans, state identity, drift, moved/import refactors and recovery. Preparing changes does not itself authorize applying them."
---

# Terraform

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 |
|---|---|
| [Terraform Delivery Audit](references/terraform-delivery-audit.md) | audit |
| [Terraform Delivery Polish](references/terraform-delivery-polish.md) | implement |
| [Terraform Plan & State Check](references/terraform-plan-state-check.md) | check |

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.

Referenced files: 4

View saved version →

---
name: vibe-vectors
description: "Audit, fix or verify vector embedding/schema compatibility, tenant filters, upserts/deletes, ANN recall, reindex migration and degraded retrieval."
---

# Vector databases

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 |
|---|---|
| [Vector Databases Audit](references/vector-databases-audit.md) | audit |
| [Vector Databases Polish](references/vector-databases-polish.md) | implement |
| [Vector Recall & Degradation Check](references/vector-recall-degradation-check.md) | check |

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.

Referenced files: 4

View saved version →

---
name: vibe-web
description: "Audit, fix or verify web server/client boundaries: SSR, hydration, serialized data, route caches, server actions and navigation in an existing framework. Use for rendering/runtime defects; product UX and visual design have separate skills."
---

# Web rendering & server boundaries

Read [the shared workflow](../../references/workflow.md) once, then the recipe matching the requested operation. Identify the installed framework/router and rendering mode; do not assume React or Next.js solely because a task concerns a web app.

| Request | Recipe |
|---|---|
| Inspect rendering, serialization or navigation | [Web Rendering Audit](references/web-rendering-audit.md) |
| Fix the named rendering or server boundary | [Web Rendering Polish](references/web-rendering-polish.md) |
| Verify initial render, private data or a server mutation | [Web Server/Client Boundary Check](references/web-boundary-check.md) |

Use the shared [rendering boundaries](../../references/web-rendering.md) for the selected framework path. UI acceptance belongs to [Product](../vibe-product/SKILL.md); an explicit patch review belongs to [Review](../vibe-review/SKILL.md). Follow necessary contract edges without turning the task into a framework migration or redesign.

Invocation lifetime and provider execution limits belong to [Serverless](../vibe-serverless/SKILL.md); optimistic client reconciliation belongs to [Realtime](../vibe-realtime/SKILL.md). Use [Cache](../vibe-cache/SKILL.md) for shared invalidation independent of rendering.

Referenced files: 4

View saved version →

---
name: vibe-workflow
description: "Normalize evidence, check or refresh stale repository maps, maintain this Vibe Coding plugin, or perform a scoped audit/fix/check when no specialized domain recipe fits."
---

# Workflow checks & maintenance

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 |
|---|---|
| [Behavior Check](references/behavior-check.md) | check |
| [Evidence Normalization](references/evidence-normalization.md) | plan |
| [Map Refresh Polish](references/map-refresh-polish.md) | implement |
| [Map Staleness Check](references/map-staleness-check.md) | check |
| [Prompt Skill Sync Audit](references/prompt-skill-sync-audit.md) | audit |
| [Prompt Skill Sync Polish](references/prompt-skill-sync-polish.md) | implement |
| [Scoped Audit](references/scoped-audit.md) | audit |
| [Scoped Polish](references/scoped-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.

Referenced files: 9