map-system

Map a repository to domain vocabulary and generate HTML or Markdown system maps.

4|Updated Mar 21, 2026
One-click install
npx skills add https://github.com/leocosta/octopus --skill map-system-leocosta
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: map-system
Source: https://github.com/leocosta/octopus/tree/main/skills/map-system
Command: npx skills add https://github.com/leocosta/octopus --skill map-system-leocosta

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Map-system maps a repository to a higher-level domain vocabulary. It provides two modes to understand and communicate structure: simplified for a quick orientation and complete for an in-depth, themed HTML deck.

Core Features & Use Cases

  • Supports both simplified and complete modes for flexible depth.
  • Generates a self-contained HTML deck (or Markdown) describing project architecture and business context.
  • Useful for onboarding new engineers, architecture reviews, and cross-team planning.

Quick Start

Invoke map-system to generate a complete HTML system deck for the current repository and save it to docs/system-map.

Frequently Asked Questions about map-system

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I generate architecture documentation for my repository for onboarding?

Create a system map for onboarding by running map-system in complete mode, which generates a themed HTML deck saved to docs/system-map. This deck describes project architecture and business context for new engineers.

What's the best way to create a quick orientation map for a codebase?

Create a quick orientation map using the simplified mode, which provides a fast high-level overview of your repository mapped to domain vocabulary without generating an exhaustive deck.

Can I save the system map output as Markdown instead of HTML?

Yes, the system map output can be saved as either HTML or Markdown. The tool implements CLI options like --mode, --save/--no-save, and --output, writing architecture documentation directly to the docs/system-map directory.

Does the generated architecture deck work for cross-team planning and reviews?

Yes, the generated architecture deck supports cross-team planning and architecture reviews. The complete mode creates a self-contained HTML deck mapping the repository to domain vocabulary, effectively communicating project structure and business context.

How do I control the depth and file output when mapping a repository?

Control depth and file output when mapping a repository using CLI options like --mode to select simplified or complete depth, and --save/--no-save combined with --output to determine whether HTML or Markdown results are written to docs/system-map.