A command-line tool: junegunn/fzf
The fuzzy finder most developers have in their shell: what the map looks like for a command-line tool in Go, with no web UI.
Map the repo
Inside the repo, run /myorg:init or $myorg:init. It maps the code, installs the git hooks that keep the map current, and builds the semantic map once: what the code does, in plain words, citing the files it explains. Run /myorg:semantic refresh --chart to chart the rest. See Getting started.
What “charted” means
Every code file is mapped from the start. Charted is the share the semantic map has read and explained. Open the map in your browser with /myorg:hq or $myorg:hq: the globe lights up area by area as charting goes, and turns violet when everything is charted. Under it, HQ says in one sentence what the code shows the project is.
All 65 code files are charted. The map found six groups a terminal user would recognize: the interactive finder, search and ranking, scripting and automation, shell and editor integration, terminals and platforms, and the platform under them.
Features
HQ groups what the code does into features, and features into a few groups an outsider would recognize. Open a group to see each feature's state, with open issues placed on the features they touch.
The interactive finder holds the screen, keys and preview, and the requests people actually make, built-in themes and better preview scrolling, show up as needed features beside what already works.
The map, by system
The Map tab's Architecture view draws the same groups as systems, with the imports between them. Switch to By folder for the directory layout.
fzf is mostly one Go package, so only three groups stand as separate systems here: search and ranking, the platform, and the terminal layer that builds on it. Switch to By folder to see the rest.
What needs you
The Guide tab says what to do next and why, then lists every command in your agent's syntax.
With the map charted, the Guide's first suggestion is to write down a convention, since the repo has no team rules yet.
Make it yours
The map is a draft for you to correct. Rename or regroup with /myorg:semantic curate, write down the conventions your reviewers repeat with /myorg:codify, and give the project a one-line mission with /myorg:anchor goal. We left this repo without one: a goal is its maintainers' to set, not ours. Every command is in the commands reference.
More examples: vercel/chatbot (AI web app), louislam/uptime-kuma (self-hosted service).