skills.rest
tvh25082004
tvh25082004COMMUNITY
Explore all skills by this author →
WebsiteGitHub

ipad-layout-audit

Detects hardcoded iPhone widths and missing iPad orientation keys in iOS projects.

Updated Aug 14, 2026
Search Tags:#swift#ios#auto layout#ipad#app store review#layout audit#guideline 2.1
One-click install
npx skills add https://github.com/tvh25082004/Badminton --skill ipad-layout-audit-tvh25082004
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: ipad-layout-audit
Source: https://github.com/tvh25082004/Badminton/tree/main/.claude/skills/apple-app-review/layout/ipad-layout-audit
Command: npx skills add https://github.com/tvh25082004/Badminton --skill ipad-layout-audit-tvh25082004

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve? Universal iOS apps get rejected under App Store guidelines 2.1 and 2.4.1 when layouts break on iPad reviewers' devices due to hardcoded iPhone-sized widths, missing iPad orientation keys, or absent size-class adaptation. ## Core Features & Use Cases - Hardcoded Width Detection: Greps Swift sources for literal frame widths like 375, 390, and 414 that overflow on iPad viewports. - Info.plist Validation: Checks for the UISupportedInterfaceOrientations~ipad key that Apple requires for proper iPad support. - Adaptation Analysis: Verifies userInterfaceIdiom .pad branches and horizontalSizeClass usage for size-class-aware layouts. - Use Case: Before submitting a universal app, run the audit to get a prioritized findings list (CRITICAL/HIGH/MEDIUM) with file paths, line numbers, and exact fixes. ## Quick Start Audit my iOS project for iPad layout issues that could cause App Store rejection under guidelines 2.1 and 2.4.1.

Frequently Asked Questions about ipad-layout-audit

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

FAQPage Schema
How do I check my iOS app for iPad layout issues before App Store submission?▼

Run a layout audit that greps Swift files for hardcoded widths like 375 or 390, checks Info.plist for UISupportedInterfaceOrientations~ipad, and verifies size-class handling. Findings are reported by severity with file paths and line numbers.

Why was my app rejected under App Store guideline 2.1 on iPad?▼

Guideline 2.1 rejections on iPad commonly come from fixed UIStackView widths or hardcoded CGRect frames matching iPhone screen widths like 375 pt, which overflow or truncate content on the larger iPad viewport.

Does this audit work with SwiftUI and UIKit projects?▼

Yes, it scans Swift sources for both UIKit patterns like frame.width literals and SwiftUI patterns like .frame(width:) with numeric values. It also works on Objective-C, React Native, and Flutter projects.

What Info.plist key is required for iPad orientation support?▼

The UISupportedInterfaceOrientations~ipad key must be present in Info.plist. Without it, Apple treats the app as iPhone-only on iPad, which the audit flags as a critical finding.

Can I use UIScreen.main.bounds.width for adaptive iPad layouts?▼

No, UIScreen.main is deprecated since iOS 16 and should not be used as a fixed layout value. Replace hardcoded widths with Auto Layout constraints or scene-based view.bounds.width instead.

Related Skills

Explore More Software Engineering Skills→
cruisediarycruisediary
13

permission-scope-audit

Detect over-broad iOS/macOS permission requests in Swift and Objective-C sources.

Community
Intermediate
cruisediarycruisediary
13

ipad-layout-audit

Detect iPad layout regressions from hardcoded iPhone widths and missing size-class adaptations.

Community
Intermediate
harshav167harshav167

app-store-review

Audit iOS App Store submission readiness for metadata, privacy, IAP, and ATT compliance.

Community
Intermediate
rshankrasrshankras
696

run-device

Builds, installs, and launches iOS apps on physical devices via xcodebuild and devicectl.

Community
Intermediate