bld-settings-professionallisted

# bld-settings-professional — two orders for the same name BLD ships every command in one of two naming schemes. Same skills, same behaviour, different thing to type. | Mode | Shape | Example | For | |---|---|---|---| | **friendly** (default) | `bld-<type>-<skill>` | `/bld-sprint-init` | Learning the set. Typing `/bld-` groups everything by type, so the list teaches you the taxonomy. | | **pro** | `bld-<skill>-<type>` | `/bld-init-sprint` | Knowing the set. You already know the category, so leading with it buries the word you are reaching for. | Neither is better. Friendly is the default because a first-timer facing 24 unfamiliar commands benefits from the grouping, and a pro can switch in one command. ## The one thing that actually matters **The folder name is cosmetic. The `name:` in the frontmatter is what you type.** Renaming a folder alone changes nothing about the command, and this is the single easiest way to leave the package in a state where the docs and the commands disagree. The script handles both together, which is why this skill runs a script instead of doing it by hand. ## How to run it > **`python` is the Windows spelling.** macOS and most Linux distros ship it as > `python3` only. If these fail with `command not found`, that is why: run > `python3 --version || python --version || py --version` and use the one that > answered. ```bash python skills/bld-settings-professional/scripts/switch-mode.py status # read-only, changes nothing python skills/b