axiom-audit-swiftui-layout

Analyze SwiftUI codebases for layout anti-patterns and adaptive strategy gaps.

34|2|Updated Mar 16, 2026
One-click install
npx skills add https://github.com/DengNaichen/Stet --skill axiom-audit-swiftui-layout
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: axiom-audit-swiftui-layout
Source: https://github.com/DengNaichen/Stet/tree/main/.agents/skills/axiom-audit-swiftui-layout
Command: npx skills add https://github.com/DengNaichen/Stet --skill axiom-audit-swiftui-layout

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill identifies common SwiftUI layout anti-patterns, such as improper GeometryReader usage, deprecated device APIs, and non-adaptive constraints that cause broken UI across different device sizes and multitasking modes.

Core Features & Use Cases

  • Anti-Pattern Detection: Automatically flags critical issues like nested GeometryReaders, hardcoded breakpoints, and identity-losing conditional stacks.
  • Adaptivity Auditing: Evaluates whether the codebase correctly utilizes size classes and modern layout containers like ViewThatFits.
  • Use Case: Use this before a major release to ensure your app remains functional in iPad Split View, Stage Manager, and across various iPhone screen sizes without clipping or layout loops.

Quick Start

Run the axiom-audit-swiftui-layout skill to perform a full audit of the current repository and generate a layout health report.

Frequently Asked Questions about axiom-audit-swiftui-layout

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

FAQPage Schema
How do I detect SwiftUI layout anti-patterns in my codebase?

To detect SwiftUI layout anti-patterns, you need to audit your view hierarchies for improper GeometryReader usage, hardcoded breakpoints, and deprecated device APIs that break adaptivity across different screen sizes.

Why does my SwiftUI layout break in iPad Split View and Stage Manager?

Your SwiftUI layout breaks in multitasking environments like Split View due to non-adaptive constraints and missing size class strategies. Auditing your code for deprecated device APIs resolves these clipping issues.

What is the best way to audit SwiftUI adaptivity for multiple device sizes?

The best way to audit SwiftUI adaptivity is to evaluate whether your codebase correctly uses modern layout primitives like ViewThatFits and AnyLayout to ensure robust, state-preserving UI across orientations and multitasking modes.

How do I fix nested GeometryReader issues causing layout loops?

To fix nested GeometryReader issues and layout loops, audit your view hierarchy to identify improper usage and replace non-adaptive constraints with modern layout containers that preserve view identity.

Does this SwiftUI audit check for deprecated device APIs and conditional stacks?

Yes, a SwiftUI layout audit checks for deprecated device APIs and flags identity-losing conditional stacks to ensure your view hierarchies remain responsive without broken UI across various iPhone and iPad environments.