---
name: velin-utilities-prefix-fix
description: Normalize classes to velin-* in Build domain (build.normalize). Not migrate.prefix.
---
# Utilities Prefix Normalize (Build)

## Purpose
Normalizes classes to velin-* naming.

## Domain
B · category `utilities`

## Capabilities
- `build.normalize`

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

## Allowed actions
- READ
- ANALYZE
- WRITE

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

## Stop conditions
- SR-11

## Agent role / risk
Normalizer · 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).

## Domain boundary (prefix conflict)
- **This skill (B):** `build.normalize` — normalize naming in VelinStyle build/edit flows.
- **Not this skill (L):** `velin-migration-prefix-classes` / `migrate.prefix` — migration of legacy/foreign class prefixes during migrate workflows.
- Same CLI family (`velinstyle prefix`) may be used; **choose by Domain**, not by guessing.
- IDs stay stable; do not merge skills.

## Workflow
1. Confirm Domain B intent (build normalize), not Tailwind residual rewrite.
2. Normalize to `velin-*` where build policy allows.
3. Residuals / unknown mappings → STOP and hand off to Migration/Intelligence — do not invent targets (BP-T03).

## Best practices
- BP-B03, BP-R01–R04, BP-T03

## Inputs / Outputs
- Inputs: html, css
- Outputs: diff, report