axiom-swiftui-debugging

Diagnose SwiftUI view update, preview crash, and layout issues with decision trees.

1|Updated Feb 8, 2026

Search Tags:#debugging #layout #preview #diagnostics #swiftui #debug-tools #observable-patterns

Ready to run

npx skills add https://github.com/foxtrottwist/ClaudeAgentConfig --skill axiom-swiftui-debugging-foxtrottwist

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: axiom-swiftui-debugging
Source: https://github.com/foxtrottwist/ClaudeAgentConfig/tree/main/xcode-agent/skills/axiom-swiftui-debugging
Command: npx skills add https://github.com/foxtrottwist/ClaudeAgentConfig --skill axiom-swiftui-debugging-foxtrottwist

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Debugging SwiftUI updates, preview crashes, and layout issues can be time-consuming and error-prone. This skill provides diagnostic decision trees and best practices to help you quickly identify root causes under pressure.

Core Features & Use Cases

Diagnostic trees for "View Not Updating", "Preview Crashes", and "Layout Issues" to guide systematic debugging.
Guidance on using Self._printChanges() to understand what triggers a view update.
Cross-reference suggestions with related skills like axiom-swiftui-performance and axiom-swift-concurrency for deeper analysis.

Quick Start

Provide a minimal reproducer, then apply the diagnostic trees to identify whether the issue is a view update, a preview crash, or a layout problem.

Frequently Asked Questions about axiom-swiftui-debugging

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

FAQPage Schema

How do I debug SwiftUI views that are not updating?▼

To debug SwiftUI views that are not updating, you should use Self._printChanges() to identify what triggers the view update, then apply structured diagnostic decision trees to isolate the root cause and enforce safe observable patterns.

Why does my SwiftUI preview crash and how can I diagnose it?▼

Your SwiftUI preview crashes can be diagnosed by walking through a structured diagnostic decision tree that identifies whether the failure is a view update issue, a layout problem, or an observable pattern error, providing actionable remediation steps.

How does Self._printChanges() work for SwiftUI view update diagnostics?▼

Self._printChanges() works for SwiftUI view update diagnostics by logging the specific state changes that trigger a view re-render, allowing you to trace observable patterns and understand why unexpected view updates occur during development.

What is the best way to troubleshoot unexpected SwiftUI layout problems?▼

The best way to troubleshoot unexpected SwiftUI layout problems is to provide a minimal reproducer and follow a structured diagnostic tree to systematically isolate whether the issue stems from view update logic or layout configuration.

Can I use this SwiftUI diagnostic approach without any external dependencies?▼

Yes, you can use this SwiftUI diagnostic approach without external dependencies, as it requires no additional packages and relies on built-in tools like Self._printChanges() alongside structured decision trees for identifying view update and layout issues.

What should I do when SwiftUI debugging does not reveal the root cause of a view update issue?▼

When SwiftUI debugging does not reveal the root cause of a view update issue, you should cross-reference related performance and concurrency analysis skills to conduct deeper investigation into observable patterns and state management.