---
name: velin-utilities-layout-apply
description: Apply existing VelinStyle layout utilities/patterns; no breakpoint guessing.
---
# Layout Utilities

## Purpose
Applies utility classes for layout and responsive structure.

## Domain
B · category `utilities`

## Capabilities
- `build.layout`

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

## Agent role / risk
Builder · 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 layout patterns/utilities already shipped.
2. Apply layout tokens/utilities (BP-S01). Do not invent breakpoint px maps.
3. If migrating Tailwind layout residuals → Domain L/M, not silent remap here.

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

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