---
name: velin-docs-component-guide
description: Document existing VelinStyle components; prefer reuse of docs patterns.
---
# Component Guide Docs

## Purpose
Writes component-focused documentation with quality checklists.

## Domain
B, R · category `documentation`

## Capabilities
- `build.docs`

## 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
Documenter · 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 component docs/guides.
2. Document real APIs/tokens — no fictional props.
3. Point agents to reuse-gate for implementation.

## Best practices
- BP-R01, BP-C02

## Inputs / Outputs
- Inputs: markdown, docs
- Outputs: markdown