swiftui-skills

What this is

Source of truth

/docs

How to use

• If you are writing code: pick the relevant doc(s), summarize the applicable rules, then produce compile-ready Swift code.
• If you are reviewing code: list issues and improvements, referencing doc(s) used.
• If uncertain: ask at most 1 question, only if the answer changes architecture.

Setup check

docs/

.md

~/.agents/skills/swiftui-skills/setup.sh

Non-negotiables

• Do not invent types or APIs. If it is not in

  /docs

  , say so and offer a safe alternative.
• Prefer minimal, idiomatic SwiftUI and platform conventions.
• Include availability notes when APIs are new.

Output format

1. Selected docs (filenames)
2. Plan (3 to 6 bullets)
3. Code (full files or a single cohesive snippet)
4. Why this matches Apple docs (2 to 5 bullets)
5. Pitfalls (short)