---
name: velin-utilities-token-map
description: Map usage to existing VelinStyle tokens; never invent targets by similarity.
---
# Token Map (Build/Review)

## Purpose
Documents how utility usage maps to token taxonomy.

## Domain
B, R · category `utilities`

## Capabilities
- `build.theme`
- `review.contract`

## Permission
`review-only`

## Allowed actions
- READ
- ANALYZE
- RECOMMEND

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

## Stop conditions
- SR-11

## Agent role / risk
Documenter · risk `low`

## 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 token catalogs / themes.
2. Only map to **documented existing** tokens (BP-T01).
3. Similar name ≠ allowed target (BP-T03). Example: do not invent a target for ambiguous utilities.
4. Migration residuals belong in Intelligence/Rewrite — not auto-filled here.

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

## Inputs / Outputs
- Inputs: tokens, css
- Outputs: markdown, report