new-setting

What problem does it solve?

Adding a new user or global setting to the JellyRock Roku app requires following a strict multi-step canonical recipe, and missing any step (such as adding the default value to the central settings file, wiring the setting into the user settings class, or regenerating documentation) leads to broken settings, inconsistent user experience, or failing CI checks.

Core Features & Use Cases

• End-to-end guided workflow: Walks through all 8 required steps for adding new toggle, dropdown, or numeric settings to JellyRock, with exact file paths for each edit.
• Built-in validation and guardrails: Stops at each step to verify changes are correct, warns about common pitfalls like writing defaults to the registry instead of the central settings file, and clarifies when to use alternative skills like /new-migration for setting renames.
• Use Case: A JellyRock contributor adding a new "auto-skip intros" toggle setting can follow the guided steps to ensure the setting is properly registered, wired into the user settings system, surfaced in the UI, tested, and documented without missing any required steps.

Quick Start

Use the new-setting skill to add a new "default subtitle language" dropdown setting to JellyRock, following each guided step to edit the correct files, write registry tests, and regenerate the settings documentation.