devisland-settings-preferences

name	devisland-settings-preferences
description	Change DevIsland settings, preferences, UserDefaults persistence, settings windows, plugin settings, localized setting labels, default values, migration behavior, or SettingsStore/AppSettings tests. Use for SettingsStore, SettingsWindow, DisplaySettings, CaffeineSettings, PluginSettingsView, settings docs, and feature settings added by other DevIsland domains.

DevIsland Settings And Preferences

Use this when a DevIsland change adds, removes, renames, persists, displays, or documents a setting. Pair with the relevant domain skill, such as devisland-notch-ui, devisland-openpeon-cesp, devisland-caffeine-plugin, devisland-plugin-architecture, or devisland-approval-proxy.

Start

Read:

• AGENTS.md
• docs/agent/ui-customization.md for notch/display settings
• docs/agent/openpeon-cesp.md for OpenPeon settings
• docs/agent/caffeine.md for Caffeine settings
• docs/agent/plugin-architecture.md for plugin enable/disable, safemode, storage, or schema settings
• The relevant feature doc when the setting controls hook, proxy, terminal, or packaging behavior

Inspect existing patterns in:

• DevIsland/Settings/SettingsStore.swift
• DevIsland/Settings/SettingsWindow.swift
• DevIsland/Settings/DisplaySettings.swift
• DevIsland/Settings/CaffeineSettings.swift
• DevIsland/Settings/PluginSettingsView.swift
• DevIsland/Plugins/PluginSettingsStore.swift
• DevIsland/Utility/Localizable.swift
• DevIslandTests/SettingsStoreTests.swift
• DevIslandTests/PluginSettingsTests.swift

Plugin-contributed settings do not go through SettingsStore: they are declared via the plugin settings schema (PluginSettingDescriptor, PluginSettingsStore) and rendered by DevIsland/Settings/PluginSettingsView.swift. Setting changes fan out to plugins as settings.changed events.

Implementation Rules

Keep setting ownership explicit:

• Store persisted values in SettingsStore / AppSettings.
• Store plugin enablement, safemode, and plugin storage controls in plugin-specific settings, not core app settings.
• Keep defaults stable and documented.
• Use existing SwiftUI settings controls and layout patterns.
• Add localization entries when user-facing labels or menu text change.
• Avoid duplicating the same setting state in UI views.

When changing an existing key, preserve backward compatibility unless the user explicitly wants a reset or migration.

Validation

Add or update focused SettingsStoreTests for:

• Default values.
• Persistence round trips.
• Range clamping or enum decoding.
• Backward-compatible behavior for renamed or missing values.

If the setting changes visible UI or behavior, update the relevant docs/agent/* file and run:

./scripts/run-tests.sh

Use devisland-change-verification before handoff.