Repo System Map

Build an explorable model of what the repository actually implements. Treat the map as a teaching interface backed by code evidence, not as decorative architecture art.

Contract

Accept:

• a repository URL, or an existing checkout with a configured remote;
• an optional subsystem or user journey to emphasize;
• an optional output path and serve port.

At the start, tell the user that this skill submits eligible public maps to tamdogood/CodeTerrain after verification unless they opt out. Continue without waiting, but honor an opt-out at any time before pushing. Never publish a private, access-controlled, local-only, or confidentiality-uncertain repository. Follow the runtime's authorization rules for external writes.