map-components

Repository context

The current repository is the subject. Collect its root with an individual Bash call, git rev-parse --show-toplevel. A failure (not a repository, git unavailable) is an unknown value; ${CLAUDE_PROJECT_DIR} is the root either way.

Purpose

Answer "what are the modules inside this one deployable, and which way do the arrows point" from build declarations, not from recall. The scope is one container. Charting every deployable is /architecture:map-containers. The landscape of repositories is /architecture:map-landscape.

Resolve home and dialect

Read ${CLAUDE_PLUGIN_ROOT}/reference/config.md first. Run bash "${CLAUDE_PLUGIN_ROOT}/lib/resolve-convention-home.sh" --root "${CLAUDE_PROJECT_DIR}" and follow the exit code. Exit 0 means read <home>/architecture/README.md for architecture_dir and the optional component_layers. Exit 1, 2, and 3 mean there is no declared home.

--out <dir> wins for this run alone. Then a declared topic-doc value. Then one question. architecture_dir has no default: an undeclared, unconfirmed home, including every non-interactive run, stops and points at /architecture:setup. component_layers has no default. Absent, --group-by layer cannot run.

This skill does not read landscape_dialect and does not add a dialect key. The diagram dialect is diagram_dialect.system from the authoring-formats topic doc. Resolve it by restating this ladder, then running the resolver rather than parsing the topic doc yourself. The ladder is a resolution order, not a task list:

1. Anchor at the repository root: `${CLAUDE_PROJECT_DIR}` when set, otherwise
   `git rev-parse --show-toplevel`. Never a CWD-relative read.
2. Resolve the convention home `<home>` with the bundled resolver above. Never hand-parse the root
   file.
3. The printed home is repo-relative: join it to the root, then pass
   `<root>/<home>/authoring-formats/README.md` to the resolver.
4. Layer order is one layer deep: an explicit `--dialect` argument, then the team convention doc.
   There is no personal overlay.
5. `diagram_dialect.system` has NO default. Allowed values are `likec4` and `c4-plantuml`. When it
   is unset, write `components.md` with the prose and tables and draw no diagram block.
6. Degrade soft, and say so. No pointer, no doc, no key, or an unrecognized value (mermaid
   included, which the convention refuses) each resolve to emitting no view. The resolver names
   the cause on stderr. Do not hard-fail and do not ask the operator to create the surface
   mid-task.
7. Report provenance: the key, the value, and the layer (`argument`, `team convention doc <path>`,
   or `unset (no C4 view emitted)`).