analyzing-api-layer

To generate API documentation, this Skill scans your repository to extract endpoints, contracts, auth configurations, and error patterns, writing authoritative machine-readable docs under docs/unwind/layers/api.

Yes, you can preserve external OpenAPI and GraphQL specifications during migrations by surfacing them as authoritative sources, ensuring your API contracts remain intact and accurately documented.

You can document REST and GraphQL API contracts incrementally because the Skill supports structured outputs and incremental writes, enabling gradual documentation updates across multiple file types.

The best way to extract API auth configurations and error patterns is to analyze the API layer directly, which pulls these elements from the codebase to produce a complete per-domain documentation set.

Yes, the API layer analysis tool works with AsyncAPI and TSRest contracts by preserving and surfacing these external API specifications as authoritative sources within your documentation.