swiftui-hardening

Reproduce and harden macOS SwiftUI runtime, layout, hosting, list/table, state-restoration, stale-cache, focus, and hover failures that unit tests do not catch.

Jump to install

Repository: rcarmo/swift-app-template
Last source activity: August 22, 2026 at 17:24
Detected SKILL.md language: English
Stars: 3
Forks: 0

Install options

The review-first prompt is selected by default. You can switch to a direct command or download a local copy.

Install with Codex or Claude Copy this prompt, paste it into Codex, Claude, or another assistant, and let it review the skill page and install it for you.

A direct command skips the review prompt. Inspect the source before running it.

npx skills add https://github.com/rcarmo/swift-app-template --skill swiftui-hardening

The command stays on one line. Scroll horizontally to inspect it before copying.

Prefer a local copy? Download the files currently available to SkillsMP.

Review the source files

Read SKILL.md and any companion files shown by SkillsMP before deciding whether to install.

File Explorer

3 files

SKILL.md

Source instructions · Read-only preview

Back to search Back to installation

SwiftUI hardening

Read references/runtime-hardening.md. Use for crashes, layout breakage, frozen/stale UI, hover/list defects, restoration surprises, hosting issues, or any “works in tests but fails live” report.

Workflow

Reproduce on the exact macOS minor version, hardware class, window size/state, input method, and hosting context.

Reduce to the smallest view/state transition while preserving the failure.

Classify it: structural identity/transition, layout proposal/priority, observation/cache, list/table/scroll container, storage/restoration, focus/hover, or AppKit/SwiftUI hosting mismatch.

Replace brittle composition with the simplest system-native invariant.

Add a deterministic logic regression test where possible and a documented live-run scenario where not.

Run repeated state changes, window resize/full-screen/tile changes, navigation and modal cycles, appearance, accessibility, focus, and lowest-supported-macOS checks.

Record the failure mode and fix in a feature note if it is non-obvious.

Guardrails

A passing unit suite is not a passing app; live-run non-trivial view changes.

Do not turn one observed framework bug into a universal rule without macOS-version and hosting evidence.

Prefer stable view identity and dimensional/modifier changes when structural insertion/removal destabilizes hosted layouts.

Rebuild snapshot-derived caches from the canonical source after mutations.

Treat @SceneStorage/restoration defaults as persisted user state requiring migration.

Hover-only actions must not reflow rows and need keyboard/menu alternatives.

Output

Report the macOS/hardware/window/input matrix, minimal trigger, classification, evidence, fix, regression protection, live-run results, and uncertainty about OS-specific behaviour.