agentleFS
parhambparhamb/design-skills/ux-settings/SKILL.md

ux-settings

Skill21 starsChanged 5 months agoMITView on GitHub

Settings screen UX: settings organization and grouping, theme switching, font size, in-app language, notification granularity, cache clearing, and data usage controls. Use when designing or reviewing a settings screen, preferences panel, or any configuration UI.

1 other project uses a version of this.

Adopted by

Most recently taken up by

The file

We split this skill into the rules it gives an agent

2 rules. About 0 are common, 2 are distinctive, and 0 are very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈2

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 0

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    Live preview: When the user changes a visual setting like theme or font size, show the result immediately without requiring them to leave …

    line 75
  2. Distinctive:

    When applying this checklist to a screen, flow, or codebase:

    line 90

≈ “Common” is an estimate: at least 1 in 5 of the 350,495 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

Settings UX

Settings is where users go when the defaults do not fit their life. A well-designed settings screen increases retention. An overwhelming or buried one drives frustration.


Checklist

ItemGuidance
Logical groupingGrouped by theme: Account, Notifications, Appearance, Privacy, About.
Theme switchingOffers System (auto), Light, and Dark options. A three-way segmented control works well.
Font sizeRespects the OS setting by default. Offers an in-app override for accessibility needs.
In-app languageUser can change the app language from within Settings, independent of the OS language.
Notification granularityOne toggle per notification type. Not just "All on / All off." See ux-notifications.
Data usage controlsAuto-download on Wi-Fi only by default. User controls media quality (low, standard, high).
Clear cacheUser can clear the app cache and see storage usage from within Settings.
Section accessSettings serves as secondary navigation. Does not duplicate the main navigation.
Search in settingsApps with 20 or more settings items offer a search bar inside settings.
Destructive actions at the bottomDelete account, sign out, and similar actions appear at the bottom of the list.

Standard Settings Structure

Settings
├── Account / Profile
│   ├── Edit profile
│   ├── Change email or phone
│   └── Password and security
├── Notifications
│   ├── [Type 1] on/off
│   ├── [Type 2] on/off
│   └── Notification schedule
├── Appearance
│   ├── Theme (System / Light / Dark)
│   ├── Font size
│   └── Language
├── Privacy
│   ├── Data and permissions
│   ├── Download my data
│   └── Connected apps
├── Storage
│   ├── Storage usage
│   └── Clear cache
├── About
│   ├── Version number
│   ├── Privacy policy
│   ├── Terms of service
│   └── Open-source licenses
└── Danger zone
    ├── Sign out
    └── Delete account

Patterns

Immediate save: Settings apply instantly without a "Save" button. The exception is a form with multiple related fields where confirmation is needed, such as changing an email address.

Live preview: When the user changes a visual setting like theme or font size, show the result immediately without requiring them to leave the Settings screen.

Contextual reset: Each settings section offers a "Reset to defaults" option rather than only a global reset that affects everything at once.

Platform conventions: On iOS, use a navigation list with the .insetGrouped style and disclosure chevrons. On Android, use PreferenceFragmentCompat with Material You styling. On web, a left sidebar works well for complex settings, tabs for simpler apps.


How to Review

When applying this checklist to a screen, flow, or codebase:

  1. Go through every checklist item and mark it Pass, Fail, or N/A — never skip items silently.
  2. Cite specific evidence for each finding: the screen, component, file, or line it applies to.
  3. Tag each failure with a severity: Blocker (breaks the experience), Major (hurts usability), or Minor (polish).
  4. End the review with the top 3 recommended fixes, ranked by user impact.

Related Skills

  • ux-notifications — per-type notification controls in depth
  • ux-user-account — account section content and deletion flows
  • ux-general — version number, dark mode sync, and OS language sync

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.