config-pattern

Adding a configuration parameter requires updating four locations: BobConfig.py with the parameter definition, config_manager.py GET and SAVE methods to expose it, HTML templates to render the UI control, and JavaScript to populate and submit the value. This Skill automates that 6-step pattern, ensuring type hints, defaults, and ranges stay consistent across the stack.

Configuration parameters follow type-specific patterns defined in this Skill. Boolean parameters use toggle controls, integers and floats use input validation with ranges, and strings use text fields. Each type requires matching definitions in BobConfig.py, backend config_manager methods, HTML templates, and JavaScript handlers to ensure end-to-end consistency.

Yes. This Skill applies to configuring thresholds, timeouts, and settings across audio, vision, performance, and other domains in BobTheSkull. The unified pattern ensures that new parameters in any subsystem are automatically exposed through the web UI and kept in sync with the backend configuration stack.

Synchronizing configuration parameters between BobConfig.py, config_manager.py, HTML templates, and JavaScript prevents drift, reduces errors, and ensures the web UI always reflects the actual backend state. Manual updates across four locations are error-prone; this Skill automates the synchronization pattern to guarantee consistency.

This Skill eliminates manual work by automating the pattern. Following its defined steps ensures that when you add a parameter to BobConfig.py and config_manager.py, the HTML templates and JavaScript are updated consistently. The pattern removes the repetitive task of keeping UI and backend in sync.