axiom audit resize

Security Community

Skill notes

Tool Use Is Mandatory

Run every Glob, Grep, and Read this prompt lists. Do not reason from training data instead of scanning. Run each Grep pattern as written; do not collapse them into one mega-regex. If your grep lacks PCRE classes (\s, \w), translate them to POSIX ([[:space:]], [[:alnum:]_.]) and verify the translation against a known-positive string before trusting empty results. Run the Read verifications each section calls for.

Files to Exclude

Skip: *Tests.swift, *Previews.swift, */Pods/*, */Carthage/*, */.build/*, */DerivedData/*, */scratch/*, */docs/*, */.claude/*, */.claude-plugin/*

Output

Write a brief Windowing Model Map (8-10 lines) summarizing: Lifecycle: SwiftUI-lifecycle / scene-based / app-delegate-only / mixed Multi-window: declared / single-scene Geometry sources: scene-relative vs UIScreen.main counts Orientation dependence: none / preference-level / layout-deriving

Phase 2: Detect Known Anti-Patterns

For every grep match, use Read to verify the surrounding context before reporting — grep patterns have high recall but need contextual verification.

1. App-Delegate-Only Lifecycle (CRITICAL — launch-blocking)

Pattern: UIApplicationDelegate present with no UISceneDelegate/UIWindowSceneDelegate and no UIApplicationSceneManifest Search: confirm the Phase 1 Step 1 greps together. A SwiftUI-lifecycle app (@main on an App struct) passes automatically — including one whose UIApplicationDelegate enters via @UIApplicationDelegateAdaptor; only flag when the app delegate is the whole lifecycle Issue: Built against the 27 SDK, an app with only an app delegate no longer launches — the scene-based life cycle is mandatory, not opt-in

Fluxly profile Runtime and permissions are inferred by Fluxly static checks, not author declarations or runtime test results.
Domain
Security
Author-declared agents
No explicit declaration found; this is not inferred or tested compatibility
Static check
94 / 100 · heuristic scan, not runtime safety proof
Runtime evidence
Not run; no isolated runtime test evidence is currently recorded
Author / version / license
@CharlesWiltgen · MIT
Token usage
Lean
Setup complexity
Guided setup
External API key
Not required
Operating systems
macOS · Windows
Runtime requirements
No explicit requirements detected
Detected file/system behavior
  • Read-only
  • Write / modify
Network behavior
Local-only
Install commands
None (reference only)

Heads up: Tool permissions are not declared; actual access depends on the runtime.

01
Phase 1: Map the App's Windowing Model

Phase 1: Map the App's Windowing Model

02
Step 1: Scene Lifecycle Adoption

Step 1: Scene Lifecycle Adoption

03
Step 2: Geometry Sources

Step 2: Geometry Sources

04
Step 3: Rendering and Input Surfaces

Step 3: Rendering and Input Surfaces

05
Phase 2: Detect Known Anti-Patterns

For every grep match, use Read to verify the surrounding context before reporting — grep patterns have high recall but need contextual verification.

06
Phase 3: Reason About Resize Completeness

Using the Windowing Model Map and your domain knowledge, check for what's *missing* — not just what's wrong. Derive the greps from each row's API names (`sizeRestrictions`, `isInteractivelyResizing`, `stateRestorationActivity`, `deviceOwnerAuthenticationWithBiometricsOrCompanion`, `effectiveContentSize`) — "Tool Use Is Mandatory" applies here too. Question · What it detects · Why it matters Is there a `minimumSize` on `sizeRestrictions` anywhere? · No usable floor · Users can shrink the window below the point where the UI works; the supported replacement for the old full-screen opt-out

07
Phase 4: Cross-Reference Findings

Bump severity for these combinations. When the SDK or deployment target is not determinable from the repo, apply the 27-SDK compound anyway (it is this audit's premise) and report target-dependent compounds as conditional: Finding A · + Finding B · = Compound · Severity App-delegate-only lifecycle · Building against 27 SDK · App does not launch · CRITICAL UIScreen.main for layout · No scene-geometry usage anywhere · Whole layout model assumes full-screen · CRITICAL

08
Phase 5: Resize Readiness Score

Scoring: RESIZE-READY: Scene lifecycle adopted, 0 CRITICAL issues, geometry read from scenes/bounds, rendering surfaces resize-aware, custom input Mirroring-compatible PARTIAL: Scene lifecycle adopted but geometry/orientation/rendering findings remain — works full-screen, degrades when resized FIXED-CANVAS: Any CRITICAL issue — the app assumes a canvas it no longer controls (or won't launch on the 27 SDK at all)

Discussion

Powered by GitHub Discussions. Sign in with GitHub to comment, react, or subscribe.