new-setting

Guide JellyRock Roku contributors through the 8-step process for adding new settings.

37|2|Updated Jun 28, 2025
One-click install
npx skills add https://github.com/jellyrock/jellyrock --skill new-setting
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: new-setting
Source: https://github.com/jellyrock/jellyrock/tree/main/.claude/skills/new-setting
Command: npx skills add https://github.com/jellyrock/jellyrock --skill new-setting

SYSTEM DOCUMENTATION & REQUIREMENTS

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.

Frequently Asked Questions about new-setting

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I add a new setting to a Roku app without breaking existing configurations?

Adding a new Roku app setting requires a canonical multi-step workflow to register default values, wire the settings class, integrate the UI, add test coverage, and regenerate documentation to prevent broken implementations.

What steps are required to implement a toggle or dropdown setting in JellyRock?

Implementing JellyRock settings involves 8 required steps, including editing the central settings file for default values, wiring the user settings class, surfacing the UI, and writing registry tests to ensure complete coverage.

Why do my Roku app settings fail CI checks after adding a new configuration?

Roku app settings fail CI checks when the implementation is incomplete, such as missing default value registration in the central settings file, failing to wire the settings class, or skipping required documentation regeneration.

Where should default values be stored when adding app settings to JellyRock?

Default values for JellyRock app settings must be stored in the central settings file, not written directly to the registry, to maintain consistency and prevent common configuration pitfalls.

When should I use a migration workflow instead of adding a new setting?

A migration workflow should be used instead of the new setting workflow when renaming existing settings, as the new setting process is strictly for adding new toggle, dropdown, or numeric preferences.