permission-priming

Generate pre-permission priming screens for iOS and macOS apps with SwiftUI components.

27|5|Updated Apr 18, 2026
One-click install
npx skills add https://github.com/bocan/bocan-music --skill permission-priming-bocan
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: permission-priming
Source: https://github.com/bocan/bocan-music/tree/main/.claude/skills/generators/permission-priming
Command: npx skills add https://github.com/bocan/bocan-music --skill permission-priming-bocan

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill solves the low iOS and macOS app permission grant rates caused by uncontextualized system permission prompts, which users frequently deny because they do not understand the app's need for access.

Core Features & Use Cases

  • Pre-Permission Priming Screens: Generates customizable screens that explain the benefits of granting access before showing the system permission dialog, dramatically increasing opt-in rates.
  • Full Permission Coverage: Supports all common iOS and macOS permissions including notifications, camera, photo library, location, microphone, contacts, HealthKit, and App Tracking Transparency.
  • Production-Ready SwiftUI Components: Includes reusable views, modifiers, and permission management logic for seamless integration into existing app codebases.
  • Edge Case Handling: Manages denied permissions by directing users to Settings, supports progressive location authorization, and includes special handling for App Tracking Transparency and HealthKit requirements.
  • Use Case: A photo editing app can use a priming screen before requesting photo library access to explain that the app needs access to let users edit their personal photos, leading to a higher grant rate than a cold system prompt.

Quick Start

Use the permission-priming skill to generate a pre-permission camera access screen that explains the app needs camera access to let users take profile pictures, then integrate the provided SwiftUI components into your app's camera feature flow.

Frequently Asked Questions about permission-priming

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I increase iOS app permission grant rates for camera and photo library access?

To increase iOS app permission grant rates, implement pre-permission priming screens that explain the value of access before showing the system prompt, preventing cold permission dialogs that users frequently deny.

What is a pre-permission screen in SwiftUI and when should I use it?

A pre-permission screen in SwiftUI is a customizable view shown before requesting system access, explaining why access is needed. Use it before requesting notifications, camera, location, microphone, contacts, HealthKit, or App Tracking Transparency permissions.

How do I handle denied app permissions in SwiftUI and direct users to Settings?

Handle denied app permissions in SwiftUI by implementing graceful denied permission handling with Settings deep links, directing users to update their preferences when they previously rejected system access requests.

Does this permission priming approach support App Tracking Transparency and HealthKit on macOS?

Yes, permission priming supports App Tracking Transparency and HealthKit requirements along with notifications, camera, photo library, location, microphone, and contacts permissions on both iOS and macOS platforms.

Can I customize the priming screen styles to match my app design system in SwiftUI?

Yes, you can configure priming screen styles to match your app design system using the included production-ready SwiftUI components, providing reusable views and modifiers for seamless integration into existing app codebases.

How do I manage progressive location authorization in iOS apps?

Manage progressive location authorization in iOS apps using unified permission status management, supporting progressive location authorization flows alongside special handling for App Tracking Transparency and HealthKit requirements.