Skills DirectorySkills Directory
SkillsLearnSecurityCategoriesDocsCommunityBlog
Sign InSubmit Skill
Skills Directory

Security-tested agent skills for Claude, coding agents, and AI workflows.

Directory

  • Browse Skills
  • All Skills A–Z
  • Claude Skills
  • Claude Code Skills
  • Agent Skills
  • Categories
  • Authors
  • Submit a Skill

Learn

  • Learn Hub
  • Install Claude Skills
  • Write SKILL.md
  • Skills vs MCP
  • Directories Compared

Security

  • Security
  • Methodology
  • Secure Claude Skills
  • Security Badges

Company

  • About
  • Community
  • Blog
  • API Docs
  • Advertise

2026 Skills Directory. All rights reserved.

ProTermsPrivacyRefunds
Back to skills

Ipad Layout Audit

ASecurity

Detects hardcoded iPhone-sized widths, missing iPad orientation keys, and absent size-class adaptation that cause layout failures on iPad reviewers' devices under guidelines 2.1 and 2.4.1.

18 stars
0 votes
0 copies
1 views
Added 9/20/2026
ai-agentspythonswiftbashreactperformance

Works with

cli

Security Analysis

A100/100

Scanned 9/20/2026

Install to Claude Code

$npx -y skills add cruisediary/apple-app-review-skills --skill ipad-layout-audit --agent claude-code

Installs into .claude/skills of the current project.

Are you the author of Ipad Layout Audit?

Add the live security badge to your README — it updates automatically with every re-scan.

Security grade badge for Ipad Layout Audit
[![Security: A — Skills Directory](https://www.skillsdirectory.com/api/skills/cruisediary-ipad-layout-audit/badge)](https://www.skillsdirectory.com/skills/cruisediary-ipad-layout-audit)

More formats (shields.io, HTML) on the badges page.

Download with Pro
Files
SKILL.md
---
name: ipad-layout-audit
description: "Detects hardcoded iPhone-sized widths, missing iPad orientation keys, and absent size-class adaptation that cause layout failures on iPad reviewers' devices under guidelines 2.1 and 2.4.1."
---

# Skill: iPad Layout Audit
<!-- SEO: iPad layout compliance audit fixed widths adaptive constraints UIStackView SwiftUI guideline 2.1 2.4.1 -->

## Purpose
Detects hardcoded iPhone-sized widths, missing iPad orientation keys, and absent size-class adaptation that cause layout failures on iPad reviewers' devices under guidelines 2.1 and 2.4.1.

## Apple Guideline
- **Primary:** 2.1 — App Completeness
- **Related:** 2.4.1
- **Reference:** `references/guidelines/2-performance.md`

## Real-World Rejection Cases
- **Case:** Fixed UIStackView widths causing overflow on iPad Air
  **Source:** https://help.adalo.com/publishing-apps/publishing-to-the-apple-app-store/submit-your-build-to-the-app-store/app-rejected-apple-guideline-2.1-ipad-support
  **Root cause:** Stack views constrained to 375 pt — the iPhone SE/8 screen width — overflowed or misaligned on the wider iPad viewport.

- **Case:** Text truncation from hardcoded frame sizes matching iPhone widths
  **Source:** Apple Developer Forums
  **Root cause:** `CGRect` frames initialised with literal width `375` or `390` clipped label content on iPad's larger canvas.

- **Case:** App reviewer uses iPad Air — layout must work on the larger viewport
  **Source:** Apple Developer Forums
  **Root cause:** Developers tested only on iPhone simulators; iPad Air review exposed missing adaptive constraints and broken navigation hierarchies.

## Trigger
Invoke when submitting a universal app (iPhone + iPad) or when the `UISupportedInterfaceOrientations~ipad` key is present in Info.plist.

## Inputs
| Name | Type | Default | Description |
|------|------|---------|-------------|
| `project_root` | path | cwd | iOS/macOS project root |
| `shared_context` | object | nil | Pre-collected context from appstore-full-audit Phase 1 |

## Actions

### Phase 1: Context Collection
*Skip this phase if `shared_context` is provided.*

1. `Glob` `**/Info.plist` — locate all Info.plist files in the project.
2. `Glob` `**/*.swift` — collect all Swift source files for pattern scanning.
3. `Glob` `**/*.storyboard` and `**/*.xib` — note any Interface Builder files (manual review may be needed).

### Phase 2: Checks

1. **Hardcoded iPhone widths (UIKit)**
   `Grep` pattern `frame\.width.*375|frame\.width.*390|frame\.size\.width.*375` in `**/*.swift`
   Flag every match as 🔴 CRITICAL — these values are iPhone screen widths and will produce broken layouts on iPad.

2. **Fixed SwiftUI frame widths**
   `Grep` pattern `\.frame\(width:` in `**/*.swift`
   Review each match: a numeric literal (e.g., `.frame(width: 375)`) is a defect; a named constant or relative value may be acceptable. Flag numeric literals as 🟠 HIGH.

3. **iPad idiom branch coverage**
   `Grep` pattern `UIDevice\.current\.userInterfaceIdiom` in `**/*.swift`
   If found, verify the branch also handles `.pad` (not only `.phone`). Missing `.pad` branch → 🟠 HIGH. If the pattern is absent entirely and the app declares iPad support, flag as 🟡 MEDIUM.

4. **iPad orientation key in Info.plist**
   `Read` each Info.plist found in Phase 1.
   Check for the key `UISupportedInterfaceOrientations~ipad`. Absence → 🔴 CRITICAL (Apple treats the app as iPhone-only on iPad).

5. **Size-class adaptation**
   `Grep` pattern `traitCollection\.horizontalSizeClass` in `**/*.swift`
   Absence in a universal app → 🟡 MEDIUM (app may not adapt to regular-width iPad environment).

### Phase 3: Output
Collect all findings from Phase 2 and build the prioritised findings list below. Include file paths and line numbers from Grep output. If no issues are found in a priority tier, omit that tier's section.

## Output Format

```
## iPad Layout Audit — Findings

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

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

### 🟡 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:

```bash
# Find hardcoded iPhone widths (375=iPhone SE/8, 390=iPhone 14)
!grep -rn "375\|390\|frame\.width" . --include="*.swift" | grep -v "//\|Test"

# Check iPad orientation support in Info.plist
!find . -name "Info.plist" -not -path "*/Pods/*" | head -1 | xargs plutil -convert json -o - | python3 -c "import sys,json; d=json.load(sys.stdin); print('iPad orientations:', d.get('UISupportedInterfaceOrientations~ipad', 'MISSING'))"

# Check size class handling
!grep -rn "horizontalSizeClass\|verticalSizeClass\|userInterfaceIdiom" . --include="*.swift"
```

## Swift Anti-Pattern Reference
`examples/swift/LayoutPatterns.swift`

## Detection Steps

1. **Find target files**
   - Glob: `**/*.swift`, `**/*.m`, `**/Info.plist`, `**/*.storyboard`, `**/*.xib`

2. **Search for rejection patterns**
   - Grep `\.frame.*width.*375\|\.frame.*width.*390\|\.frame.*width.*414` — hardcoded iPhone widths
   - Grep `UIScreen.main.bounds.width` used as fixed layout value (not adaptive)
   - Grep `UIUserInterfaceIdiom.*pad\|userInterfaceIdiom == \.pad\|isPad` — iPad branch (correct)
   - Read `Info.plist` → check `UISupportedInterfaceOrientations~ipad` key exists

3. **Determine verdict**
   - Hardcoded `375`/`390`/`414` width found → 🟠 HIGH (Guideline 2.4.1)
   - `UISupportedInterfaceOrientations~ipad` missing from Info.plist → 🟠 HIGH
   - No iPad idiom branches in layout code → 🟡 MEDIUM
   - Adaptive layout used throughout → 🟢 pass

4. **Report**
   - File path + line of hardcoded width
   - Missing Info.plist key
   - Fix: Replace hardcoded widths with Auto Layout constraints or `view.bounds.width` (scene-based); `UIScreen.main` is deprecated since iOS 16 — do not use it as a replacement; add `UISupportedInterfaceOrientations~ipad` to Info.plist

Attribution

cruisediarycruisediary
View sourceMore from cruisediary →
SSkills DirectorySkills Directory

Your tool, in front of Claude Code builders.

3 founder slots · $299/mo · GSC-verified traffic · sponsors can never buy grades.

See placements

Is this your skill, or is something wrong with this listing? Request removal or report an issue. Author removals are honored within 72 hours.

Comments (0)

No comments yet. Be the first to comment!

SSkills DirectorySkills Directory

Your tool, in front of Claude Code builders.

3 founder slots · $299/mo · GSC-verified traffic · sponsors can never buy grades.

See placements

Related Skills

Caveman

Ultra-compressed communication mode that cuts output tokens while keeping technical accuracy. Levels: lite, full, ultra and the wenyan variants. Use for /caveman, "caveman mode", "talk like caveman", "be brief" or "less tokens".

1074701 votes

Hyperplan

Adversarial multi-agent planning skill. Self-orchestrates 5 hostile category members (unspecified-low, unspecified-high, deep, ultrabrain, artistry) via team-mode for ruthless cross-critique debate, distills only the defensible insights, then MANDATORILY hands the distilled insight bundle to the `plan` agent for executable plan formalization. Use when planning needs maximum rigor and surfacing of weak assumptions, blind spots, and over-engineering. Triggers: 'hyperplan', 'hpp', '/hyperplan', ...

694381 votes

Mcp Code Execution

Routes multi-tool workflows through MCP servers for large datasets and pipelines. Use when Bash tool overhead is limiting throughput on data-heavy tasks.

3351 votes

catchup

Recovers the conversation and failed tool calls of a previous Codex, Claude Code, Antigravity, Cline, Copilot CLI, Cursor, DeepSeek Harness, Kimi, OpenCode, Pi Agent, or ZCode session. Use when the user says "catch up", "what did the last session do", "get me up to speed", "I switched agents", asks to recover/summarize a previous session before continuing, or asks to diagnose or report a catchup failure. Do NOT use for the current conversation, git history, or any non-agent log.

691 votes

math-skill

A comprehensive mathematical reasoning skill for AI assistants — handles arithmetic to research-level problems with rigorous step-by-step reasoning, systematic verification, and transparent uncertainty handling

381 votes
View all in ai-agents →