What problem does it solve? Editing settings or profile-editor preference rows in the Husi composeApp/ codebase without its conventions produces rows with missing backgrounds, divider lines, unmasked icons, and obsolete lazy-list platform hooks that break the native Android-style grouped look. ## Core Features & Use Cases - Row Import Rules: Mandates importing preference rows from fr.husi.compose wrappers (which apply PreferenceItemSurface) instead of upstream me.zhanghai.compose.preference composables. - Segmented Group Layout: Defines preferenceGroup structure, PreferenceGroupDefaults spacing/radius values, and rules for conditional sections via AnimatedVisibility with correct item arrangement. - Icon Masking and Semantics: Requires MaskedIcon with IconMaskColors for every row and semantic IconMaskShapes (risk, credential, route) for security-relevant settings. - Use Case: When adding a new DNS settings toggle to a Husi settings sub-page, use this Skill to place a SwitchPreference inside the existing preferenceGroup, give it a MaskedIcon, and run the prescribed ripgrep checks to confirm no upstream imports or dividers were introduced. ## Quick Start Use the husi-preference-ui skill to add a new masked SwitchPreference row to the general settings group in composeApp following the project conventions.