agentleFS
moasqmoasq/ios-dev-agent/.agents/skills/notifications/SKILL.md

notifications

Skill4 starsChanged 6 months agoMITView on GitHub

Use when implementing notification features. Covers UNUserNotificationCenter permission flow, scheduling, badge count, foreground handling.

9 other projects use a version of this.

Adopted by

Most recently taken up by

Used with

Projects with it also use release.

Other files people use alongside this one.

Files found in the same public projects as a version of this one, more often than they turn up anywhere else. Each project counts once, large collections count for less, and this file's own repository is left out.
  • MicrosoftSkill

    release

    Use ONLY when the user explicitly asks to cut/publish a Huabu desktop release or tag a version. Performs an outward action — bumps the version in apps/desktop/package.json, commits + annotated-tags vX.Y.Z, and pushes the branch + tag. That tag push auto-builds the macOS/Windows installers and publishes a GitHub Release. Provides `status`, `bump`, `tag-push`, and a one-command `run` (bump → tag-push).

    Also in 3 projects that use this

The file

We split this skill into the rules it gives an agent

1 rule. 0 are common, 1 is distinctive, and 0 are very specific to this project.

  • 0

    Common

    Most of the 8 edited versions we read keep these.

  • 1

    Distinctive

    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:

    Use this guide when implementing or modifying notification features.

    line 8

“Common” is measured: kept by at least 6 in 10 of the 8 edited versions of this file we could read. “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

Local Notifications

Use this guide when implementing or modifying notification features.

Framework

UserNotifications — UNUserNotificationCenter.current()

Permission States (CRITICAL — handle ALL four)

  1. Not Determined — Call .requestAuthorization(options: [.alert, .badge, .sound]). System shows dialog.
  2. Authorized — Schedule notifications normally.
  3. Denied — App CANNOT re-request. Must redirect user to System Settings.
  4. Provisional — Quiet notifications. Treat as authorized.

Permission Is System-Controlled

  • Once denied, the app has NO way to re-request — only the user can re-enable in System Settings.
  • To open Settings: UIApplication.shared.open(URL(string: UIApplication.openSettingsURLString)!)

UI Rules for Notification Status

  • .notDetermined — Show "Enable Notifications" button that calls requestAuthorization. After dialog, re-check and update UI.
  • .authorized / .provisional — Show enabled state (bell icon). Read-only — user disables in Settings.
  • .denied — Show "bell.slash" icon + "Open Settings" button. Show helper text explaining system control.
  • NEVER use a writable Toggle for notification permission — the app cannot grant/revoke it. Use buttons with state-specific actions.

Re-Check on Foreground (CRITICAL)

Any view displaying notification status MUST re-check when app returns to foreground:

.onReceive(NotificationCenter.default.publisher(for: UIApplication.willEnterForegroundNotification)) { _ in
    Task {
        let settings = await UNUserNotificationCenter.current().notificationSettings()
        isEnabled = (settings.authorizationStatus == .authorized || settings.authorizationStatus == .provisional)
    }
}

Scheduling

let content = UNMutableNotificationContent()
content.title = "Reminder"
content.body = "Time to check in"
content.sound = .default

// Time-based
let trigger = UNTimeIntervalNotificationTrigger(timeInterval: 3600, repeats: false)

// Calendar-based (daily at specific time)
var dateComponents = DateComponents()
dateComponents.hour = 20
dateComponents.minute = 0
let trigger = UNCalendarNotificationTrigger(dateMatching: dateComponents, repeats: true)

let request = UNNotificationRequest(identifier: "reminder", content: content, trigger: trigger)
try await UNUserNotificationCenter.current().add(request)

Badge Count

  • Set: UNMutableNotificationContent().badge = NSNumber(value: count)
  • Clear on app open: UIApplication.shared.applicationIconBadgeNumber = 0

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.