services-architecture-atlas

You generate microservices architecture documentation automatically by orchestrating multiple specialized analysis skills to produce program-level catalogs and per-service docs. This process adheres to Blueprint Standard v1.3.2 and ensures all claims are backed by file:line evidence to prevent hallucinations.

An evidence-first approach for code analysis ensures all architecture blueprint claims are backed by file:line evidence. This mechanism prevents hallucinations by requiring concrete codebase proof for every service inventory, API catalog, event catalog, and dependency map generated.

Yes, you can use this for an architecture review to generate an up-to-date, detailed atlas of your entire microservices platform. It produces comprehensive per-service documentation and dependency maps, making it ideal for onboarding new engineers or conducting reviews.

You create a service inventory and dependency map by running this Skill to analyze your codebase and generate program-level catalogs. It outputs detailed service inventories, API catalogs, and event catalogs, complete with ASCII diagrams for visualizing dependencies.

Yes, the generated architecture documentation includes ASCII diagrams to visualize service dependencies and structures. Alongside these diagrams, it produces program-level catalogs and per-service documentation adhering to Blueprint Standard v1.3.2 with zero hallucination.

The best way to document microservices without hallucinating API catalogs is to use an evidence-first approach that backs every claim with file:line evidence. This Skill orchestrates specialized analysis to ensure zero-hallucination documentation adhering to Blueprint Standard v1.3.2.