What problem does it solve?
Settings pages in the Warp GUI desktop app are often written by pattern-matching neighboring code, which repeatedly produces two bugs: page headings that vanish during search filtering, and unfilterable mega-widgets that match every query. This Skill encodes the correct model for PageType, SettingsWidget, search_terms, and widget gating so new settings pages behave correctly under settings search.
Core Features & Use Cases
- Page structure guidance: Explains the PageType variants (Uncategorized, Categorized, Monolith) and where page titles versus section headings must live so headings survive search filtering.
- Widget gating rules: Distinguishes build-time
if gating for static feature flags from should_render for runtime-changing conditions like auth state or user toggles.
- Search term scoping: Shows how to split mega-widgets into one widget per setting row with scoped search_terms, preserving deeplink widget ids.
- Use Case: When adding a new settings page to
app/src/settings_view, follow this Skill to pick the right PageType variant, place the title in the page-title slot, and verify filtering with the unit-test harness in mod_tests.rs.
Quick Start
Use the gui-settings-ui skill to add a new settings page to the Warp client with correct title placement, widget gating, and per-widget search terms.
