---
name: velin-reuse-gate
description: Before build/migration/intelligence/rewrite: search existing VelinStyle skills, components, utilities, tokens, and patterns; recommend reuse or extend; allow NEW only when gap is evidenced.
---

# Reuse Gate

## Purpose
Before build/migration/intelligence/rewrite: search existing VelinStyle skills, components, utilities, tokens, and patterns; recommend reuse or extend; allow NEW only when gap is evidenced.

## Domain
B · category `ai-workflows`

## Capabilities
- `reuse.gate`

## Permission
`plan-only`

## Allowed actions
- READ
- ANALYZE
- RECOMMEND
- PLAN

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

## Stop conditions
- SR-11
- SR-12

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

## When to use
Any non-greenfield request to build, migrate, classify, or rewrite.

## Workflow
1. SEARCH existing skills/components/utilities/tokens/patterns (**including project structure** via docs/dx-doctor/migration-scan signals).
2. **Component inventory browse:** list compatible official components before recommending NEW (covers former NEW-SKILL browse candidate).
3. Check COMPATIBILITY with intent.
4. Prefer REUSE or EXTEND.
5. Allow NEW only with evidenced gap.
6. If reuse skipped without greenfield intent → STOP (SR-12).

## CLI bridge
None (registry/docs search). Optional: `velinstyle skills` / docs / doctor.

## Rules
- Never auto-create components when a VelinStyle solution fits (BP-R01–R04).
- Never skip to Apply/Rewrite.
- Never invent migration targets while searching.

## Anti-Patterns
- Creating duplicate skills.
- Ignoring existing packs/graphs.

## Best practices
- BP-R01, BP-R02, BP-R03, BP-R04, BP-C01

## Output
checklist, report