See also
The command palette is an interactive list bound to Ctrl+Shift+P whose purpose is to execute commands. The command palette is fed entries with commands files. Usually, commands that don’t warrant creating a key binding of their own are good candidates for inclusion in a .sublime-commands file.
Commands files use JSON and have the .sublime-commands extension.
Here’s an excerpt from Packages/Default/Default.sublime-commands:
[
{ "caption": "Project: Save As", "command": "save_project_as" },
{ "caption": "Project: Close", "command": "close_project" },
{ "caption": "Project: Add Folder", "command": "prompt_add_folder" },
{ "caption": "Preferences: Default File Settings", "command": "open_file", "args": {"file": "${packages}/Default/Base File.sublime-settings"} },
{ "caption": "Preferences: User File Settings", "command": "open_file", "args": {"file": "${packages}/User/Base File.sublime-settings"} },
{ "caption": "Preferences: Default Global Settings", "command": "open_file", "args": {"file": "${packages}/Default/Global.sublime-settings"} },
{ "caption": "Preferences: User Global Settings", "command": "open_file", "args": {"file": "${packages}/User/Global.sublime-settings"} },
{ "caption": "Preferences: Browse Packages", "command": "open_dir", "args": {"dir": "$packages"} }
]
The command palette filters entries by context, so whenever you open it, you won’t always see all the commands defined in every .sublime-commands file.