---
name: velin-components-recipe
description: Apply known VelinStyle component recipes after reuse; no ad-hoc invention.
---
# Component Recipe

## Purpose
Builds reusable component recipes for recurring UI blocks.

## Domain
B · category `components`

## Capabilities
- `build.components`

## Permission
`write` · **requiresApproval: true**

## Allowed actions
- READ
- PLAN
- WRITE

## Forbidden actions
- APPLY
- ROLLBACK
- ACCEPT
- DEFER
- NOTE
- ACKNOWLEDGE
- CATALOG
- MANIFEST
- CLASSIFY
- invent-target

## Stop conditions
- SR-12

## Agent role / risk
Builder · risk `med`

## Reuse (mandatory before build)

Follow `velin-reuse-gate` (BP-R01…R04):

1. **SEARCH** existing VelinStyle skills, components/Web Components, utilities, tokens, and patterns.
2. **EXISTING?** If a fit exists, document it.
3. **COMPATIBLE?** If yes → **REUSE** (or EXTEND). If no → document the incompatibility.
4. **NEW** only with evidenced gap — never "create because needed".
5. Skipping reuse on non-greenfield work → **STOP** (SR-12).

## Workflow
1. SEARCH recipes/docs for the target pattern.
2. Follow recipe with official components (BP-C01).
3. Forms: labels required (BP-F01). Tables: headers (BP-TB01).

## Best practices
- BP-R01–R04, BP-C01, BP-F01, BP-TB01, BP-N01

## Inputs / Outputs
- Inputs: prompt, html
- Outputs: html, markdown