---
name: velin-dev-component-wire
description: Wire existing VelinStyle components/WCs into a page after reuse search.
---
# Component Wire

## Purpose
Wires selected components with predictable APIs and semantics.

## Domain
B · category `development`

## Capabilities
- `build.wire`

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

## Allowed actions
- READ
- WRITE

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

## Stop conditions
- SR-11
- 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 component registry / WCs / recipes.
2. If compatible → REUSE and wire (BP-C01, BP-C02).
3. If incompatible → document delta; do not silently fork APIs.
4. Legacy `*-wc` replacement is Domain L (`migrate.legacy-wc`), not this skill.

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

## Inputs / Outputs
- Inputs: html, docs
- Outputs: html, diff