/map
- Type:
/map - What it does: Project map — what it is, how to run it, structure, critical flows and where to touch for each thing
- In Spanish:
/mapa(when Senzu is installed with--lang es) - It is a shortcut: asking for it in plain words triggers the same thing through the router.
Usage: /map [optional area, e.g. "payments"] — the argument is optional; if none is given, it maps the whole project.
Apply code-quality §references/mapa-proyecto.md (read-only, it doesn’t change code):
- Read manifests, configuration and
.env.example(never.env), the folder structure and the entry points (routes, commands, queues, scheduled tasks, webhooks). - Follow 3-5 critical flows from start to finish, noting the file and function at each step.
- Run
node <skills-dir>/backend-audit/scripts/hotspots.mjsfor the risk areas. - Write
senzu/mapa.mdwith the reference’s structure: the essentials on the first screen and the “where to touch for…” table with the frequent tasks. - Propose linking it from
CLAUDE.mdorCLAUDE.project.mdso the agent reads it when starting.
When finished
Section titled “When finished”If the user is going to work on something specific: /plan for a multi-part feature, or /next if there is already a plan.