---
name: velin-design-section-rhythm
description: Apply VelinStyle section spacing/rhythm after reuse of layout patterns.
---
# Section Rhythm

## Purpose
Aligns spacing rhythm and section purpose to design rules.

## Domain
B · category `design`

## Capabilities
- `build.design`

## 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 existing section/layout patterns and spacing tokens.
2. Apply rhythm with existing utilities — do not invent spacing scales (BP-S01, BP-T01).
3. One job per section (headline + short support).

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

## Anti-patterns
- Guessing breakpoint px / rem remaps (SR-09 territory — STOP and escalate to migration skills if migrating).

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