Skip to content
cccskills
FreePublished on GitHub

safe-area-compliance

Detects unsafe safe-area overrides and hardcoded inset values that hide content behind the Dynamic Island, notch, or home indicator, violating Apple's Human Interface Guidelines for adaptive layout.

The English summary is being prepared. Showing the original description.

Run score Not tested

See how to install

Files included (1)

  • SKILL.md5.5 KB

SKILL.md (original)

Review the instructions the agent will receive before you install.

Skill: Safe Area Compliance

<!-- SEO: safe area insets Dynamic Island home indicator notch UIKit SwiftUI ignoresSafeArea edgesIgnoringSafeArea HIG adaptive layout -->

Purpose

Detects unsafe safe-area overrides and hardcoded inset values that hide content behind the Dynamic Island, notch, or home indicator, violating Apple's Human Interface Guidelines for adaptive layout.

Apple Guideline

  • Primary: HIG — Adaptivity and Layout (Apple Human Interface Guidelines)
  • Related: 2.1
  • Reference: references/hig/adaptive-layout.md

Real-World Rejection Cases

  • Case: Content hidden behind Dynamic Island on iPhone 14 Pro and later Source: Apple Developer Forums Root cause: View used .edgesIgnoringSafeArea(.all) without compensating insets, pushing interactive controls into the Dynamic Island cutout area.

  • Case: Bottom navigation buttons unreachable behind home indicator Source: App Store Connect rejection feedback Root cause: Tab bar and custom buttons were positioned at y = screenHeight - 49 — correct for notchless iPhones but obscured by the home indicator on Face ID devices.

  • Case: Developer hardcoded top: 44 inset — broke on devices with different safe areas Source: Apple Developer Forums Root cause: The status-bar height is not a fixed constant; devices with Dynamic Island, notch, or no notch all have different top safe-area values.

Trigger

Invoke on any iOS project that targets iPhone or iPad to verify safe-area insets are respected.

Inputs

NameTypeDefaultDescription
project_rootpathcwdiOS/macOS project root
shared_contextobjectnilPre-collected context from appstore-full-audit Phase 1

Actions

Phase 1: Context Collection

Skip this phase if shared_context is provided.

  1. Glob **/*.swift — collect Swift source files.
  2. Glob **/*.m — collect Objective-C source files.
  3. Glob **/*.storyboard and **/*.xib — note Interface Builder files for manual safe-area review.

Phase 2: Checks

  1. Full safe-area suppression (SwiftUI) Grep pattern \.edgesIgnoringSafeArea\(\.all\) in **/*.swift Every match → 🟠 HIGH. Suppressing all safe-area insets risks content being clipped by hardware features on any device.

  2. Zero-inset layout (UIKit) Grep pattern UIEdgeInsets\.zero in **/*.swift and **/*.m Review each match for proximity to layout constraint setup. When used to zero out system-defined safe-area insets → 🟠 HIGH.

  3. Hardcoded safe-area constants Grep pattern top:\s*44|bottom:\s*34|bottom:\s*83 in **/*.swift and **/*.m Every match → 🟠 HIGH. These magic numbers match specific device safe-area heights and will be wrong on other hardware.

  4. Unscoped ignoresSafeArea (SwiftUI) Grep pattern ignoresSafeArea\(\) in **/*.swift Flag calls that do not include .keyboard as the region argument → 🟡 MEDIUM. Scoping to .keyboard is the safe pattern; bare ignoresSafeArea() suppresses all regions.

Phase 3: Output

Collect all findings from Phase 2 and build the prioritised findings list below. Include file paths and line numbers. Omit tiers with no findings.

Output Format

## Safe Area Compliance — Findings

### 🔴 CRITICAL — Guaranteed rejection
- [ ] TODO: <exact actionable step> — `file:line` — HIG Adaptivity

### 🟠 HIGH — Very likely rejection
- [ ] TODO: <exact actionable step> — `file:line` — HIG Adaptivity

### 🟡 MEDIUM — Possible rejection
- [ ] TODO: <exact actionable step> — `file:line`

### 🟢 LOW — Best practice
- [ ] TODO: <exact actionable step>

Tools Used

Glob, Grep, Read

Constraints

  • Read-only. No file edits.
  • No network calls.
  • Skip Phase 1 if shared_context is provided by orchestrating agent.
  • Works on Swift, Objective-C, React Native, Flutter projects.

Quick Commands

Run these in your project root to check manually:

# Check for unsafe safe area overrides
!grep -rn "edgesIgnoringSafeArea\|ignoresSafeArea\|UIEdgeInsets\.zero" . --include="*.swift"

# Check for hardcoded inset values (44=nav bar, 34=home indicator)
!grep -rn "top:.*44\|bottom:.*34\|bottom:.*83" . --include="*.swift"

Swift Anti-Pattern Reference

examples/swift/LayoutPatterns.swift

Detection Steps

  1. Find target files

    • Glob: **/*.swift, **/*.m, **/*.storyboard, **/*.xib
  2. Search for rejection patterns

    • Grep edgesForExtendedLayout = \[\] — disables safe area extension
    • Grep UIEdgeInsets(top: 0\|UIEdgeInsets(top: 20\|UIEdgeInsets(top: 44 — hardcoded status bar height
    • Grep frame\.origin\.y = 0\|frame\.origin\.y = 20\|frame\.origin\.y = 44 — hardcoded Y origin
    • Grep safeAreaInsets\|safeAreaLayoutGuide — correct safe area handling (absence is the problem)
  3. Determine verdict

    • Hardcoded top: 20 or top: 44 insets → 🟠 HIGH (content hidden behind Dynamic Island)
    • edgesForExtendedLayout = [] without safe area compensation → 🟠 HIGH
    • safeAreaLayoutGuide used throughout → 🟢 pass
  4. Report

    • File path + line of hardcoded inset
    • Fix: Replace hardcoded insets with view.safeAreaInsets.top; use safeAreaLayoutGuide anchors in Auto Layout

Reviews

No reviews yet. Tell others what you thought.

Comments

No login needed. Share how it worked for you, ask a question, or note where it did not run.

No comments yet. Be the first to write one.

Comments are published right away. Do not include personal information such as email addresses or phone numbers. Up to 2 URLs.

0 / 1,000 characters

This form is protected by reCAPTCHA, and the Google Privacy Policy and Terms of Service apply.

More skills from this repository

Detects missing or insufficient in-app account deletion functionality required since June 30, 2022 under Guideline 5.1.1(v) for all apps that support account creation.

The English summary is being prepared. Showing the original description.

cruisediary/apple-app-review-skills19Updated May 2, 2026

Detects feature patterns that require a higher age rating than commonly submitted, enforcing Guideline 2.3.6 which requires age ratings to accurately reflect the app's content and social features.

The English summary is being prepared. Showing the original description.

cruisediary/apple-app-review-skills19Updated May 2, 2026

Detects apps that send user data to third-party AI systems without explicit in-app consent and disclosure, enforcing Guideline 5.1.2(i).

The English summary is being prepared. Showing the original description.

cruisediary/apple-app-review-skills19Updated May 2, 2026

Detects placeholder content, stub UI, hardcoded test credentials, and non-production endpoints that signal an incomplete app to reviewers under Guideline 2.1.

The English summary is being prepared. Showing the original description.

cruisediary/apple-app-review-skills19Updated May 2, 2026

Detects app name violations including names exceeding 30 characters, beta labels, Apple trademark terms, and version numbers in the display name, enforcing Guideline 2.3.7.

The English summary is being prepared. Showing the original description.

cruisediary/apple-app-review-skills19Updated May 2, 2026

App Store rejection prevention for iOS/macOS apps. Covers privacy, UGC, IAP, metadata, layout, and quality checks based on real Apple rejection cases.

The English summary is being prepared. Showing the original description.

cruisediary/apple-app-review-skills19Updated May 2, 2026

See all skills by cruisediary

Report a problem with this skill