Duo Readiness

    1

    Static source code review for iOS apps to find and fix nonresponsive layouts, safe-area bugs, and text scaling issues.

    Free

    1 useSecurity scanned

    Works with the AI Agents you already use

    Claude CodeClaude CodeCursorCursorCodex CLICodex CLIMuseMuseDotsDots+21 more

    Duo Readiness

    Example session with this skill installed

    Run a layout review on the SwiftUI files in /Sources/UI to check for responsiveness and Dynamic Type issues.

    • Read your context and instructions
    • Compiled the duo readiness

    I have completed a static review of the SwiftUI source files in /Sources/UI. The audit focused on layout adaptability, safe area compliance, and Dynamic Type scaling.

    Responsive UI Audit Findings

    File:LineProblemImpactFocused Fix
    HomeView.swift:42Fixed frame(width: 375) on main container.Horizontal clipping on smaller devices (mini) and wasted space on Max/iPad.Remove fixed width; use .frame(maxWidth: .infinity) or GeometryReader.
    ProfileHeader.swift:88VStack with fixed spacing: 20 containing large text.Text overlap or vertical clipping when Dynamic Type is set to AX sizes.Wrap in ScrollView or use @ScaledMetric for adaptive spacing.
    OnboardingVC.swift:112Bottom button constrained to view.bottom ignoring safe area.Button overlaps the Home Indicator, making it difficult to trigger.Constrain to view.safeAreaLayoutGuide.bottomAnchor instead of the view bottom.
    LoginView.swift:65Input fields lack keyboard avoidance logic.Keyboard obscures the "Submit" button on iPhone SE and smaller devices.Embed in a ScrollView or add .ignoresSafeArea(.keyboard, edges: .bottom) logic.

    Next steps

    • Apply the .frame fix in HomeView.swift to allow the layout to fill the available container width.
    • Update OnboardingVC.swift to use safe area layout guides to ensure reachability on all device models.
    • Review references/duo_architecture_patterns.md for standard adaptive spacing implementations.

    Note: This was a static source review. The app was not built or run in a simulator.

    Connects securely to your tools. The creator never sees your data.

    About this skill

    Hardcoded dimensions and fixed offsets break iOS layouts when users resize text or switch to Split View. This skill performs a static analysis of SwiftUI and UIKit source code to identify nonresponsive UI patterns before they reach production. It scans for brittle layout assumptions, safe-area violations, and keyboard overlap issues that lead to clipped content or unreachable buttons.

    What it does

    • Identify rigid layouts by tracing hardcoded measurements and fixed-width modifiers through parent containers.
    • Audit accessibility scaling to find text views and containers that break when Dynamic Type sizes increase.
    • Check safe-area compliance ensuring controls remain reachable around notches, home indicators, and system bars.
    • Verify keyboard handling to find views that fail to shift or resize when the software keyboard appears.
    • Provide targeted remediation by suggesting minimal code changes to replace fixed constants with adaptive logic.

    How it works

    1. Source Discovery: Use rg to locate UI files, skipping dependencies and tests to focus on active app code.
    2. Pattern Analysis: Trace measurements against a checklist of common responsive layout failures.
    3. Impact Mapping: Document how specific triggers, like width changes or font scaling, cause clipping or overlaps.
    4. Issue Reporting: Deliver a list of findings mapped to specific files and lines with focused code fixes.

    Frameworks & tools

    Works with native iOS projects using SwiftUI, UIKit, and Auto Layout. It utilizes standard Unix tools like rg for high-speed source interrogation without requiring project builds or simulator access.

    Why this beats prompting it yourself

    Generic prompts often flag every GeometryReader or constant as a bug. This skill understands context, distinguishing between intentional design choices like icon sizes and brittle layout errors that actually cause UI failure.

    Use cases

    • Auditing an existing iPhone app for iPad Split View or multitasking readiness.
    • Validating new UI components against Dynamic Type and accessibility scaling.
    • Cleaning up technical debt by replacing rigid Auto Layout constraints with flexible alternatives.

    Known limitations

    Does not perform runtime validation, simulator testing, or hinge detection. Static analysis only; cannot detect issues triggered by dynamic server-side content height.

    Static analysis only. Does not run code, launch simulators, or detect runtime-only dynamic content height issues. Focuses on layout, not business logic or networking.

    How to use

    1. 1

      Connect your agent to the Agensi MCP

      Copy the prompt and paste it into Claude, ChatGPT, Cursor or any agent that supports MCP. It sets up the connection for you. Manual setup

    2. 2

      Sign in to Agensi

      Your agent shows a sign-in link. Sign in and click Allow.

    3. 3

      Ask for what you need

      Your agent loads this skill and uses it on your task. It always asks before any payment.

    Reviews

    No reviews yet

    Be one of the first to try it. Every listed skill goes through the trust checks below.

    Security scanned

    Checked by our 8-point scan before listing

    1 use

    Times used to date

    Free forever

    No account required to browse

    Trust & safety

    Security scan

    Security scan passed 19 days ago

    • Free with an Agensi account

    Requires

    GitHub
    Python
    Node.js
    Git

    Permissions

    Terminal / Shell
    Read Files
    Network Access
    Write Files

    Allowed Hosts

    raw.githubusercontent.com
    Listed19 days ago

    What's inside

    Frequently Asked Questions

    This skill scans your SwiftUI and UIKit source code to detect brittle, hardcoded layouts that fail when users resize text (Dynamic Type) or use Split View on iPad, preventing clipped content and unreachable buttons.

    No simulator or build process is required; the skill uses static analysis to interrogate your raw .swift files, making it significantly faster and easier to run than manual UI testing.

    The skill is designed for native iOS projects using SwiftUI or UIKit and is compatible with AI agents that have filesystem access and standard CLI tools like Ripgrep (rg).

    Yes, the skill provides specific line-by-line remediation suggestions, offering adaptive code alternatives to replace the rigid constants it identifies.

    Since it performs static source analysis, it cannot detect layout shifts caused by dynamic data fetched from APIs or content heights that are only calculated at runtime.

    New in Mobile Development