axiom-uikit

Debug UIKit and SwiftUI interoperability with Auto Layout and lifecycle patterns.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This skill resolves the friction between UIKit and SwiftUI, providing a systematic approach to bridging complex UI components, debugging elusive Auto Layout constraint conflicts, and managing legacy UIKit animation and Combine pipelines.

Core Features & Use Cases

  • UIKit-SwiftUI Bridging: Safely wrap UIKit views in SwiftUI or embed SwiftUI in UIKit using the Coordinator pattern.
  • Layout Debugging: Systematically resolve "Unable to simultaneously satisfy constraints" errors using symbolic breakpoints and view hierarchy inspection.
  • Modernization: Migrate legacy UIKit apps to support scene lifecycles, resizable windows, and modern TextKit 2 architectures.
  • Use Case: When a SwiftUI view needs to integrate a complex PencilKit canvas or a legacy TextKit 1 editor, this skill provides the exact bridging patterns and lifecycle management required to prevent memory leaks and layout jank.

Quick Start

Use the axiom-uikit skill to debug a constraint conflict in my view controller.

Frequently Asked Questions about axiom-uikit

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

FAQPage Schema
How do I resolve unable to simultaneously satisfy constraints errors in UIKit Auto Layout?

Resolve Auto Layout constraint conflicts by systematically using symbolic breakpoints and view hierarchy inspection to identify and eliminate duplicate or conflicting constraints in your view controller.

What is the best way to wrap a complex UIKit view in SwiftUI without causing memory leaks?

Wrap UIKit views in SwiftUI safely by using the Coordinator pattern to manage delegates and ensure proper lifecycle management, preventing memory leaks and layout jank during integration.

How do I migrate legacy UIKit pipelines from Combine to async/await?

Migrate UIKit Combine pipelines to async/await by applying systematic interoperability patterns that bridge reactive streams into modern asynchronous functions for production iOS applications.

Does this approach support bridging a legacy TextKit 1 editor into a modern SwiftUI interface?

Yes, bridging supports legacy TextKit 1 editors by providing exact integration patterns and lifecycle management required to embed complex UIKit text components into SwiftUI.

Why does my SwiftUI view jank when embedding a PencilKit canvas using UIKit bridging?

Layout jank occurs when bridging PencilKit without proper lifecycle management; applying the correct UIKit-SwiftUI Coordinator pattern ensures synchronized animation state and smooth rendering.

Can I modernize a legacy UIKit app to support scene lifecycles and resizable windows?

Modernize legacy UIKit apps by migrating to scene-based lifecycles and configuring resizable windows while adhering to established architectural standards for production compatibility.