Skip to content
Skills Library
Programming · Analysis

menu-map

/menu-map

Use when mapping where each parameter is reached on the machine, when a control has no byte in the patch map, or before building effects or a panel from a decoded record.

Licence
MIT
Last repository change
11.11.2026

Assessment and security

86/ 100Class: good
Format25 / 25
Frontmatter with name and description, valid name, description up to 1,024 characters, name matching the folder.
Discoverability25 / 25
Description explains when to use the skill, has a reasonable length and uses third person.
Content21 / 35
At least 150 words and at most 500 lines, headings, step lists, examples or code.
Hygiene15 / 15
No placeholders such as TODO, no Windows paths, with a licence.
Riskno signals detected in the scan
Files in this package
1
Scripts
0
HTML comments
0
URLs in SKILL.md
0
Deprecation

No signals detected. Repository changed on 11.11.2026, without references to retired models or APIs.

Licence

MIT, open: use and modify while retaining author attribution.

What it does and when to use it

Use when mapping where each parameter is reached on the machine, when a control has no byte in the patch map, or before building effects or a panel from a decoded record.

Original author description

Use when mapping where each parameter is reached on the machine, when a control has no byte in the patch map, or before building effects or a panel from a decoded record.

How it works

SKILL.md has no level-two headings · 26 lines, 492 words

SKILL.md preview
---
name: menu-map
description: Use when mapping where each parameter is reached on the machine, when a control has no byte in the patch map, or before building effects or a panel from a decoded record.
---

# Map the menus (one job: every parameter joined to the page that reaches it, and every mismatch listed)

A patch map says what byte N means. A menu map says how you reach byte N from the panel, and it names what you can edit that is no byte in a patch at all. On one machine the chorus and delay TYPE selectors sat outside the patch block, and that blocked the effects work for a day.

<constraints>
Always do:
1. Write the tree from the manual's own section order, page by page, with the printed page number each page is cited from, one tree per algorithm or mode where the pages differ. This is the only part edited by hand: a script looks up everything else and regenerates the table.
2. Tag each name by its source: `[FW]` in the firmware's display pools (`names-first`), `[MAN]` printed. Page membership and page order are usually `[MAN]` alone, and the map says so.
3. Join the two with the manual's own display drawings: the page name on the top line, the parameter on the bottom. Find each half in the firmware's pools. That is the two-source check for the whole tree. Each drawing or screen picture is read by `read-a-screen-image` first, so every page in the tree has its report, its exact text and the gesture that reaches it.
4. Give every parameter its home: patch, multi or performance, global, or stored nowhere.
5. Print both mismatch lists, because they are the point of the file:
   - on a page but not in the patch map: multi and global parameters, and anything with no published index;
   - in the patch map but no page reaches it: dead, reserved, live and set by presets only, or a page still to find. A parameter list describes the control surface, not the engine: an algorithm with no knob for something usually has it, fixed.
6. Check whether every parameter that shapes the sound is in the dump. One that is not must be sent another way, and a rebuild that loads only the dump loses it.
7. Write down what changes the map. Menus are dynamic: a page hidden while its effect is off still exists. Pages re-label themselves: one byte can carry two names, by mode, so list both.
8. Read the routes as well as the pages: which press on which page opens which page, from the firmware's own page changes, with the manual as the second source. They become the build's route table (instrument-shell's `menu-is-one-route-table`), every row with its source.
9. Keep corrections in the file, and end it with what is not established.

Never do:
- Conclude a parameter does not exist, or does nothing, because no page shows it.
- Give one byte one name when a mode re-labels it.
- Edit the generated table by hand.
- Build effects or a panel before the first mismatch list is read.
</constraints>

Versions

The database has no other skills named menu-map.

Database snapshot: 13.11.2026 · package version 908d68379844 (SHA-256 digest of the entire package)

Downloads in the last 30 days: 0 · ranking

Report a problem with this skill: harmful content, incorrect descriptions or an author’s removal request.

Similar skills

  • 90v1-menu
    Use when explicitly choosing which v1tamins skill fits a task. Triggers on "which v1 skill", "v1 menu", or "/v1-menu".
  • 86read-a-screen-image
    Use when a manual, a service manual or a photo shows the machine's own screen (a play or edit page, a menu, a test-mode page, an LCD), or before building a screen, a page or a menu of the rebuild from one.
  • 100modal-toast-dialog-stinger
    Build accessible React overlays. Use for dialog, drawer, toast, command menu, focus handling, or stacking. Read README.md for the guide map.

Feedback and reports

Your message goes to Bartosz Sokoliński. An email address is needed only for a reply. See the privacy policy.