---
name: velin-docs-generate-api
description: Generate API docs from real VelinStyle metadata; no invented APIs.
---
# Generate API Docs

## Purpose
Generates API Markdown and verifies documentation footprint.

## Domain
B · 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. Use CLI/meta sources of truth.
2. Do not invent component APIs or migration mappings.
3. Output markdown matching declared formats.

## Anti-patterns
- Documenting unsafe rewrite Apply as a normal build step.

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