---
name: velin-perf-runtime-tree-shake
description: Guide VelinStyle runtime tree-shaking using existing packages; no unsafe deletes.
---
# Runtime Tree-Shake Guidance

## Purpose
Reduces runtime payload using explicit component loading strategy.

## Domain
B · category `performance`

## Capabilities
- `build.perf`

## 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
Optimizer · risk `high`

## 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. Identify unused runtime imports via existing tooling guidance.
2. Prefer documented entry points; do not delete unknown shared code.
3. Validate with review/perf skills after changes.

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