Skip to content

Legends Guides

How to use the Legends tooling: install the CLI, generate documentation for a legacy repository with GitHub Copilot, review what comes out, publish it to this portal, and query it conversationally in Legends Chat or from GitHub Copilot through Holocron.

If you have never run doc gen before, read Install / update the CLI and then Quick start in order. Everything else is reference material you come back to.

How the pieces fit together

Legends has four moving parts:

Piece What it is Where it lives
legends CLI A .NET global tool. Installs doc gen tooling into a repo and searches published documentation. NuGet package Legends.CLI
Doc gen tooling Copilot agents, prompts, skills, and templates written into .github/ and .saifdocgen/ by legends init. The repository being documented
This portal Aggregates the generated markdown from every documented repository into one searchable site. saif-corp/legends
Holocron MCP A remote MCP server that gives GitHub Copilot agents holocron_* tools over the published documentation. Registered in your Copilot hosts by legends agent init

The normal lifecycle is: install the CLI, run legends init in the legacy repo, run the SAIF Doc Gen Copilot agent, review, merge to the repo's default branch, register the repo here, then publish.

Once documentation is published, Legends Chat answers questions from it in natural language — it reads the same corpus this portal publishes, so a repository has to get through the lifecycle above before the chat app knows anything about it.

Holocron MCP brings the same corpus into GitHub Copilot, so agents can search it and answer from it, with citations, without you leaving the editor.