We create launchers in /config/launcher, and a copy of the launcher under <used-file-system>/config/<sculpt-version>/launcher. The launchers will then be copied to /config/launcher when the file-system is Used and appear in the + menu under Options, where they can be started/stopped with a mouse click. For examples look for the default launchers in /config/launcher.
For example, you could edit /config/launcher/mixer to your need and copy the changed version to <used-file-system>/config/24.04/launcher/mymixer. On next Use of the file-system you will find myxmixer in /config/launcher. Btw. you can do this for all configurations in /config and overwrite the default ones upon Use. I also click together a basic scenario every Sculpt release (window manager, nic_router, fonts_fs, system_shell etc.) and copy the resulting /config/managed/deploy to <used-file-system>/config/24.04, which leads to a basic setup that is always started once you hit Use for this specific file-system.
In addition to the description by @ssumpf, you can find the launcher concept described in the “Runtime management” section of the Sculpt manual for reference.
Personally, I use to integrate a new component first using the interactive user interface, assigning all the routes. Once integrated, I copy the corresponding <start> node as found at /config/managed/deploy to a new launcher file at /config/launcher/, replacing the enclosing <start> tags by <launcher> tags and removing the name attribute (which is not needed for a launcher). Now, I can interactively remove the component from the graph and restart it by using the Options tab of the start menu. Once this way of starting and removing the component works satisfactory, I copy the new launcher file to the Sculpt partition as described by @ssumpf to keep it persistently present in my Options menu across reboots.