Index of every page on this site: llms.txt
All skills
rshankras avatar

/settings-screen

@f958982
Run it yourself

Generates a complete settings screen for iOS/macOS apps with common sections. Use when user wants to add settings, preferences, or configuration UI.

Use this Skill: https://skilld.dev/gh/rshankras/claude-code-apple-skills/settings-screen

Nothing lands on disk. Nothing to clean up.

Fork this Skill

Edit a local copy. It keeps the author and licence.

SKILL.md

≈41 tokens for metadata: the name and description. ≈1.5k when used: this file. ≈2.6k more on demand in 1 file.

Description uses 2.1% of example budget

Before choosing a Skill, your Agent reads its name and description. All available Skills share that space.

  • A shorter description leaves more room for other Skills. This entry exceeds our 1% size suggestion.

In our Claude Code example, all Skill names and descriptions share 8,000 characters. This Skill uses ≈166 characters, or 2.1%.

The 1% threshold is a size suggestion. Longer descriptions can still fit.

Your model, settings, and other Skills decide how much text your Agent can read.

Example settings and source

The example uses a 200k-token context and default Claude Code settings. The count includes the name, description, separators, and when_to_use when present. Codex also counts local file paths.

Skit's source and limits: Codex 0.160.1, Claude Code 2.1.292.

Settings Screen Generator

Generates a production-ready settings screen with modular sections for iOS and macOS apps.

When This Skill Activates

  • User asks to "add settings" or "create settings screen"
  • User mentions "preferences", "app settings", or "configuration UI"
  • User wants to add dark mode toggle, notifications settings, or about screen

Pre-Generation Checks (CRITICAL)

1. Project Context Detection

Before generating, ALWAYS check:

# Find existing settings implementations
rg -l "SettingsView|PreferencesView|SettingsScreen" --type swift

# Check deployment target
cat Package.swift | grep -i "platform"
# Or check project.pbxproj for deployment target

# Detect architecture pattern
rg -l "Observable|ObservableObject|@EnvironmentObject" --type swift | head -5

# Check platform (iOS vs macOS)
rg "UIKit|UIApplication" --type swift | head -1  # iOS
rg "AppKit|NSApplication" --type swift | head -1  # macOS

2. Conflict Detection

If existing settings implementation found:

  • Ask user: Extend existing, replace, or create separate?
  • Check for naming conflicts with existing files

Configuration Questions

Ask user via AskUserQuestion:

  1. Which sections do you need?

    • Account (sign out, delete account)
    • Appearance (dark mode, app icon)
    • Notifications (push settings)
    • About (version, developer info)
    • Legal (terms, privacy)
  2. Platform?

    • iOS (NavigationStack)
    • macOS (Settings scene / NavigationSplitView)
    • Both (adaptive)
  3. Additional features?

    • App icon selector
    • Language selector
    • Data export
    • Cache clearing

Generation Process

Step 1: Create Core Files

Generate these files (customize based on answers):

Sources/Settings/
├── SettingsView.swift              # Main container
├── AppSettings.swift               # @AppStorage wrapper
├── Components/
│   └── SettingsRow.swift           # Reusable row component
└── Sections/
    ├── AppearanceSettingsView.swift
    ├── AccountSettingsView.swift
    ├── NotificationsSettingsView.swift
    ├── AboutSettingsView.swift
    └── LegalSettingsView.swift

Step 2: Read Templates

Read templates from this skill:

  • templates/SettingsView.swift
  • templates/AppSettings.swift
  • templates/SettingsRow.swift
  • templates/AppearanceSettingsView.swift
  • templates/AccountSettingsView.swift
  • templates/NotificationsSettingsView.swift
  • templates/AboutSettingsView.swift
  • templates/LegalSettingsView.swift

Step 3: Customize for Project

Adapt templates to match:

  • Project naming conventions
  • Existing architecture patterns
  • Selected sections only
  • Platform-specific code

Step 4: Integration

iOS Integration:

// In any view
NavigationLink("Settings") {
    SettingsView()
}

// Or as sheet
.sheet(isPresented: $showSettings) {
    NavigationStack {
        SettingsView()
    }
}

macOS Integration:

// In App.swift
@main
struct MyApp: App {
    var body: some Scene {
        WindowGroup {
            ContentView()
        }

        Settings {
            SettingsView()
        }
    }
}

Platform-Specific Considerations

iOS

  • Use NavigationStack with List
  • Use Form for grouped appearance
  • Link to Settings app for notifications: UIApplication.openSettingsURLString

macOS

  • Use Settings scene for standard preferences window
  • Consider TabView for multiple sections
  • Use Form with appropriate styling
  • Support keyboard shortcut (⌘,)

Cross-Platform

  • Use conditional compilation for platform-specific features
  • Abstract platform differences in AppSettings

Generated Code Patterns

AppStorage Wrapper

@Observable
final class AppSettings {
    static let shared = AppSettings()

    @AppStorage("appearance") var appearance: Appearance = .system
    @AppStorage("notificationsEnabled") var notificationsEnabled = true

    enum Appearance: String, CaseIterable {
        case system, light, dark
    }
}

Settings Row Component

struct SettingsRow<Content: View>: View {
    let icon: String
    let iconColor: Color
    let title: String
    let content: () -> Content

    var body: some View {
        HStack {
            Image(systemName: icon)
                .foregroundStyle(iconColor)
                .frame(width: 28)
            Text(title)
            Spacer()
            content()
        }
    }
}

Verification Checklist

After generation, verify:

  • Settings accessible from main UI
  • All selected sections present
  • AppStorage persists between launches
  • Dark mode toggle works correctly
  • Links to external URLs work (privacy, terms)
  • Platform-appropriate navigation
  • Accessibility labels present
  • VoiceOver navigation works

Common Customizations

Adding Custom Sections

// In SettingsView
Section("Custom") {
    NavigationLink("My Feature") {
        MyFeatureSettingsView()
    }
}

Conditional Features

#if DEBUG
Section("Debug") {
    DebugSettingsView()
}
#endif

Subscription Integration

if !subscriptionStatus.hasAccess {
    Section {
        Button("Upgrade to Pro") {
            showPaywall = true
        }
    }
}

Related Skills

  • paywall-generator - For subscription upgrade prompts in settings
  • auth-flow - For account management integration
  • review-prompt - Trigger review from settings (sparingly)

References

Source: SKILL.md on GitHub

skilld matched fixed text patterns in SKILL.md and file names. Patterns miss obfuscated code.

skilld run checks every file with the same patterns. It asks for approval before it loads a Skill with a behavior marked Needs approval.

No alerts3mo3 checks · Risk SAFE
  • Gen Agent Trust Hub3mo

    The skill is a legitimate development utility for generating SwiftUI settings screens for iOS and macOS applications. It provides well-structured templates and uses project introspection to ensure compatibility with existing codebases without introducing security risks.

  • Socket3mo

    No alerts

  • Snyk3mo

    Risk: LOW · No issues

Signed by skilld at f958982. This ties the file your Agent reads to that commit on GitHub. It does not review the instructions.

Last checked against GitHub last week.

Activeupdated 4 months ago
What it can do
Reads files Edits files Runs commands
last_verified
2026-07-16
review_by
2027-06-22
All 7 allowed tools
ReadWriteEditGlobGrepBashAskUserQuestion

README badge

README badge for rshankras/claude-code-apple-skills/settings-screen