A small AI chat app: vercel/chatbot
An AI chat app on Next.js with 139 code files, about the size of a first project, for teams building AI products.
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.
Every code file is charted, and the map found four groups: AI conversations, documents and code, chat history and sharing, 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.
AI conversations holds five working features, from choosing a model to streaming replies. The open issues on the composer and streaming show as in flight, and two real risks sit on top: /clear only hides messages, and interrupted replies never resume.
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.
Three product areas sit on one shared platform (sign-in, rate limits, storage), so most imports point down to it.
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 this 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: louislam/uptime-kuma (self-hosted service), junegunn/fzf (command-line tool).