---
name: velin-dev-page-scaffold
description: Scaffold VelinStyle pages after plan + reuse; prefer existing patterns.
---
# Page Scaffold

## Purpose
Renders plan-based HTML and runs review gates.

## Domain
B · category `development`

## Capabilities
- `build.scaffold`

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

## Allowed actions
- READ
- PLAN
- 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. Require plan-first / dependsOn.
2. SEARCH page shells, layouts, components.
3. Scaffold with `velin-*` naming; wire existing components (BP-C01).
4. No Tailwind residual invent; no Apply.

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

## Examples
- Prefer existing app-shell / marketing layout over greenfield HTML soup.

## Inputs / Outputs
- Inputs: prompt, plan-json
- Outputs: html, review-json