@leejungkiin/awkit 1.1.0 → 1.1.2

package/skills/memory-sync/SKILL.md

@@ -224,6 +224,34 @@ Template saved to session:
   }
 ```
 
+### W7: Brainstorm / Analysis Artifact Persist (MỚI)
+**Điều kiện:** Brainstorm-agent hoặc AI tạo brainstorm/analysis artifact
+```
+Patterns detect:
+- BRIEF.md tạo xong (qua brainstorm-agent)
+- Analysis document tạo (pricing, market, competitor...)
+- Brainstorm document tạo (feature ideas, architecture exploration...)
+
+Action (SILENT):
+1. POST metadata vào Symphony Notes API (type: brainstorm hoặc analysis)
+2. content = summary ngắn 2-3 dòng ONLY
+3. filePath = absolute path đến file artifact
+4. conversationId = conversation ID hiện tại
+5. projectId = project đang active
+
+curl -X POST http://localhost:3100/api/notes -H 'Content-Type: application/json' -d '{
+  "projectId": "<project-id>",
+  "type": "brainstorm",
+  "title": "<artifact-title>",
+  "content": "<summary-2-3-lines>",
+  "filePath": "<path-to-file>",
+  "conversationId": "<conversation-id>",
+  "metadata": { "tags": [...], "created_by": "memory-sync" }
+}'
+
+⚠️ Nếu Symphony server offline → skip silently, không block workflow
+```
+
 ---
 
 ## 🔄 MEMORY SYNC PROTOCOL
@@ -304,7 +332,7 @@ NEVER:
 ```
 Runs BEFORE: awf-session-restore (cung cấp data)
 Runs AFTER:  awf-auto-save (fallback nếu memory-sync bỏ sót)
-Works WITH:  beads-manager (link memory entries với Bead IDs)
+Works WITH:  symphony-orchestrator (link memory entries với Symphony task IDs)
 Works WITH:  orchestrator (nhận resolved_target → query focused hơn)
 Enhances:    awf-error-translator (thêm historical context)
 SEPARATE FROM: brainstorm-agent (hoàn toàn độc lập — brainstorm-agent xử lý ý tưởng)

package/skills/nm-memory-sync/SKILL.md

@@ -89,7 +89,7 @@ allowed-tools:
 **Links:** `SUPERSEDES` → old pattern if exists
 
 ### W4: Task Complete → `workflow` type
-**Condition:** Task marked done trong Beads
+**Condition:** Task marked done trong Symphony
 **Capture:** What was done + approach taken
 **Store:** `nmem_remember(content, type="workflow", priority=5)`
 
@@ -178,7 +178,7 @@ If `nmem` is not available, falls back to flat-file behavior:
 
 ## Integration
 
-- Works alongside `beads-manager` for task lifecycle hooks
+- Works alongside `symphony-orchestrator` for task lifecycle hooks
 - Reads `.project-identity` for project-scoped memory filtering
 - Feeds data to `nm-memory-audit` for quality checks
 - Activated before `orchestrator` dispatches (priority 2.5 in skill chain)

package/skills/orchestrator/SKILL.md

@@ -1,184 +1,58 @@
 ---
 name: orchestrator
-description: >-
-  Intelligent dispatcher — analyzes context, injects project brain, then
-  delegates to the right skill or workflow. Always runs first.
-invocation-type: auto
-version: 2.1.0
-trigger: always
-priority: 1
+description: Intelligent dispatcher — analyzes context and delegates to the right skill or workflow
 ---
 
-# Orchestrator Skill v2.1 — Project-Aware + Self-Evolving
+# Orchestrator Skill
 
-> **Role:** First-layer processor. Chạy trước MỌI skill khác.
-> **v2.0:** Project Brain Lookup — inject project context trước khi route.
-> **v2.1:** Self-Evolution Pattern — tự ghi learnings sau mỗi session.
+## Purpose
+Route user requests to the correct workflow or skill based on context analysis.
 
----
-
-## Execution Order (MANDATORY)
+## Routing Logic
 
+### 1. Slash Command Detection
 ```
-Step 1: Project Brain Lookup    ← chạy đầu tiên
-Step 2: Intent Detection
-Step 3: Route to skill/workflow
-Step 4: Self-Evolution          ← ghi learnings nếu có
+User input starts with `/` → Load workflow file directly
+  /plan     → workflows/lifecycle/plan.md
+  /code     → workflows/lifecycle/code.md
+  /debug    → workflows/lifecycle/debug.md
+  ...etc (see GEMINI.md § 2)
 ```
 
----
-
-## Step 1: Project Brain Lookup (LUÔN CHẠY)
-
-### 1.1 — Đọc `.project-identity`
-
+### 2. Intent Detection (No slash command)
 ```yaml
-check: Có file .project-identity trong project dir không?
-
-IF EXISTS:
-  read: .project-identity
-  extract:
-    - projectName
-    - stage
-    - architecture (clean_architecture, mvvm)
-    - tech stack (swift, react, node, etc.)
-
-SET: project_context = { name, stage, arch, stack }
-```
-
-### 1.2 — Đọc `CODEBASE.md`
-
-```yaml
-check: Có file CODEBASE.md trong project dir không?
-
-IF EXISTS:
-  read: CODEBASE.md
-  extract:
-    - layer_map: { layer_name → files[] }
-    - feature_areas: { feature → directory }
-    - naming_conventions
-
-RULES:
-  → KHÔNG scan raw directory nếu CODEBASE.md tồn tại
-  → KHÔNG hỏi user về file location — tự suy luận từ codebase_map
-```
-
-### 1.3 — Resolve Target từ Request
-
-```yaml
-resolve_target(user_request, codebase_map):
-  1. Layer match: "crash khi login" → AuthenticationViewModel
-  2. Feature match: "water tracking" → Features/Water/
-  3. Service match: "camera chậm" → CameraViewModel
-  4. Fallback: list top 3 candidates từ CODEBASE.md
-```
-
-### 1.4 — Brief Confirm Output (LUÔN HIỂN THỊ)
-
-```
-Format:
-  "📚 [ProjectName] | [Stage] | [Architecture]
-   🗺️  Targeting: [resolved file/layer]"
-
-Nếu file được nhắc KHÔNG có trong CODEBASE.md:
-  → Footer: "⚠️ CODEBASE.md có thể outdated — dùng /codebase-sync"
-```
-
----
-
-## Step 2: Intent Detection
+code_intent:
+  keywords: ["implement", "build", "create", "add", "code", "fix", "viết", "tạo"]
+  action: Suggest `/code` or `/codeExpert`
 
-```yaml
 debug_intent:
-  keywords: ["error", "bug", "crash", "fix", "lỗi", "sửa", "fail", "không chạy"]
-  action: Execute debug flow với target đã resolve từ Step 1
-
-code_intent:
-  keywords: ["implement", "build", "create", "add", "code", "viết", "tạo", "thêm"]
-  action: Execute code flow tại target layer/file đã biết
+  keywords: ["error", "bug", "crash", "fix", "lỗi", "sửa", "fail"]
+  action: Suggest `/debug` or `/debugExpert`
 
 plan_intent:
   keywords: ["plan", "design", "architect", "how to", "strategy", "thiết kế"]
-  action: Route to /plan với project context injected
+  action: Suggest `/plan` or `/planExpert`
 
 context_intent:
-  keywords: ["remember", "save", "continue", "where was I", "nhớ", "tiếp", "recap"]
-  action: Route to /recap hoặc /save-brain
+  keywords: ["remember", "save", "continue", "where was I", "nhớ", "tiếp"]
+  action: Suggest `/recap` or `/save-brain`
 
 ads_intent:
   keywords: ["ads", "campaign", "CPI", "ROAS", "quảng cáo"]
-  action: Route to /ads-audit hoặc /adsExpert
-
-image_intent:
-  trigger: User gửi ảnh chụp màn hình
-  + debug keywords: Route to visual-debug với CODEBASE context
-  + design keywords: Route to design-to-ui
-  + error screenshot: Route to debug flow
+  action: Suggest `/ads-audit` or `/adsExpert`
 ```
 
----
-
-## Step 3: Routing
-
-### With Project Context (khi đã có CODEBASE.md)
-
+### 3. Skill Pack Check
 ```
-→ Không suggest workflow, THỰC HIỆN LUÔN
-→ Đi thẳng đến file/layer đã resolve
-→ Không hỏi "file này ở đâu?" — đã biết từ CODEBASE.md
+If user request involves iOS-specific → Check if mobile-ios pack enabled
+If not enabled → Suggest: "awf enable-pack mobile-ios"
 ```
 
-### Slash Command Detection
-
-```yaml
-/plan        → workflows/lifecycle/plan.md
-/planExpert  → workflows/lifecycle/planExpert.md
-/code        → workflows/lifecycle/code.md
-/codeExpert  → workflows/lifecycle/codeExpert.md
-/debug       → workflows/lifecycle/debug.md
-/debugExpert → workflows/lifecycle/debugExpert.md
-/codebase-sync → workflows/context/codebase-sync.md
-# ...etc (see GEMINI.md)
-```
-
-### Fallback
-
+### 4. Fallback
 ```
-No intent match → Ask clarifying question (max 2 lần)
-Still unclear   → Suggest /help
+No match → Ask clarifying question (max 2 times)
+Still unclear → Suggest `/help`
 ```
 
----
-
-## Step 4: Self-Evolution Protocol
-
-After each session, if a routing decision was suboptimal or a new intent was discovered:
-
-1. **Record** the finding in the Learnings section below
-2. **Update** routing rules in Step 2 if a new keyword pattern should be added
-3. **Cross-check** skill catalog (`skills/CATALOG.md`) to ensure new skills are routable
-
-> This ensures the orchestrator improves its routing accuracy over time.
-
-## Learnings
-
-_Findings from past sessions are recorded here. Add new entries as bullet points._
-
-- v2.0: Added project brain lookup — significantly reduces unnecessary questions about file locations.
-- v2.1: Added self-evolution pattern — skill now self-improves by recording routing insights.
-- `invocation-type` field added to help distinguish auto vs manual skills in routing decisions.
-
----
-
-## Integration
-
-```yaml
-runs_before: awf-session-restore, memory-sync, all workflows
-provides_to: [project_context, resolved_target, intent]
-receives_from: user_request, active_document
-```
-
----
-
-*orchestrator v2.1 — Project-Aware + Self-Evolving Dispatcher*
-*Created by Kien AI*
+## Auto-Activation
+This skill is always active. It runs as the first layer before any other processing.

package/skills/skills/nm-memory-sync/SKILL.md

@@ -89,7 +89,7 @@ allowed-tools:
 **Links:** `SUPERSEDES` → old pattern if exists
 
 ### W4: Task Complete → `workflow` type
-**Condition:** Task marked done trong Beads
+**Condition:** Task marked done trong Symphony
 **Capture:** What was done + approach taken
 **Store:** `nmem_remember(content, type="workflow", priority=5)`
 
@@ -178,7 +178,7 @@ If `nmem` is not available, falls back to flat-file behavior:
 
 ## Integration
 
-- Works alongside `beads-manager` for task lifecycle hooks
+- Works alongside `symphony-orchestrator` for task lifecycle hooks
 - Reads `.project-identity` for project-scoped memory filtering
 - Feeds data to `nm-memory-audit` for quality checks
 - Activated before `orchestrator` dispatches (priority 2.5 in skill chain)

package/skills/smali-to-kotlin/SKILL.md

@@ -429,7 +429,7 @@ triggers_from:
 delegates_to:
   - "/test" — after parity check
   - "/deploy" — when rebuild is complete
-  - beads-manager — auto-track progress per step
+  - symphony-orchestrator — auto-track progress per step
 
 works_with:
   - memory-sync — saves decisions, patterns, solutions

package/skills/smali-to-swift/SKILL.md

@@ -663,7 +663,7 @@ triggers_from:
 delegates_to:
   - "/test" — after parity check
   - "/deploy" — when rebuild is complete
-  - beads-manager — auto-track progress per step
+  - symphony-orchestrator — auto-track progress per step
 
 works_with:
   - memory-sync — saves decisions, patterns, solutions

package/skills/swiftui-pro/SKILL.md

@@ -0,0 +1,108 @@
+---
+name: swiftui-pro
+description: Comprehensively reviews SwiftUI code for best practices on modern APIs, maintainability, and performance. Use when reading, writing, or reviewing SwiftUI projects.
+license: MIT
+metadata:
+  author: Paul Hudson
+  version: "1.0"
+---
+
+Review Swift and SwiftUI code for correctness, modern API usage, and adherence to project conventions. Report only genuine problems - do not nitpick or invent issues.
+
+Review process:
+
+1. Check for deprecated API using `references/api.md`.
+1. Check that views, modifiers, and animations have been written optimally using `references/views.md`.
+1. Validate that data flow is configured correctly using `references/data.md`.
+1. Ensure navigation is updated and performant using `references/navigation.md`.
+1. Ensure the code uses designs that are accessible and compliant with Apple’s Human Interface Guidelines using `references/design.md`.
+1. Validate accessibility compliance including Dynamic Type, VoiceOver, and Reduce Motion using `references/accessibility.md`.
+1. Ensure the code is able to run efficiently using `references/performance.md`.
+1. Quick validation of Swift code using `references/swift.md`.
+1. Final code hygiene check using `references/hygiene.md`.
+
+If doing a partial review, load only the relevant reference files.
+
+
+## Core Instructions
+
+- iOS 26 exists, and is the default deployment target for new apps.
+- Target Swift 6.2 or later, using modern Swift concurrency.
+- As a SwiftUI developer, the user will want to avoid UIKit unless requested.
+- Do not introduce third-party frameworks without asking first.
+- Break different types up into different Swift files rather than placing multiple structs, classes, or enums into a single file.
+- Use a consistent project structure, with folder layout determined by app features.
+
+
+## Output Format
+
+Organize findings by file. For each issue:
+
+1. State the file and relevant line(s).
+2. Name the rule being violated (e.g., "Use `foregroundStyle()` instead of `foregroundColor()`").
+3. Show a brief before/after code fix.
+
+Skip files with no issues. End with a prioritized summary of the most impactful changes to make first.
+
+Example output:
+
+### ContentView.swift
+
+**Line 12: Use `foregroundStyle()` instead of `foregroundColor()`.**
+
+```swift
+// Before
+Text("Hello").foregroundColor(.red)
+
+// After
+Text("Hello").foregroundStyle(.red)
+```
+
+**Line 24: Icon-only button is bad for VoiceOver - add a text label.**
+
+```swift
+// Before
+Button(action: addUser) {
+    Image(systemName: "plus")
+}
+
+// After
+Button("Add User", systemImage: "plus", action: addUser)
+```
+
+**Line 31: Avoid `Binding(get:set:)` in view body - use `@State` with `onChange()` instead.**
+
+```swift
+// Before
+TextField("Username", text: Binding(
+    get: { model.username },
+    set: { model.username = $0; model.save() }
+))
+
+// After
+TextField("Username", text: $model.username)
+    .onChange(of: model.username) {
+        model.save()
+    }
+```
+
+### Summary
+
+1. **Accessibility (high):** The add button on line 24 is invisible to VoiceOver.
+2. **Deprecated API (medium):** `foregroundColor()` on line 12 should be `foregroundStyle()`.
+3. **Data flow (medium):** The manual binding on line 31 is fragile and harder to maintain.
+
+End of example.
+
+
+## References
+
+- `references/accessibility.md` - Dynamic Type, VoiceOver, Reduce Motion, and other accessibility requirements.
+- `references/api.md` - updating code for modern API, and the deprecated code it replaces.
+- `references/design.md` - guidance for building accessible apps that meet Apple’s Human Interface Guidelines.
+- `references/hygiene.md` - making code compile cleanly and be maintainable in the long term.
+- `references/navigation.md` - navigation using `NavigationStack`/`NavigationSplitView`, plus alerts, confirmation dialogs, and sheets.
+- `references/performance.md` - optimizing SwiftUI code for maximum performance.
+- `references/data.md` - data flow, shared state, and property wrappers.
+- `references/swift.md` - tips on writing modern Swift code, including using Swift Concurrency effectively.
+- `references/views.md` - view structure, composition, and animation.

package/skills/swiftui-pro/agents/openai.yaml

@@ -0,0 +1,10 @@
+interface:
+  display_name: "SwiftUI Pro"
+  short_description: "Reviews SwiftUI code for modern best practices."
+  icon_small: "./assets/swiftui-pro-icon.svg"
+  icon_large: "./assets/swiftui-pro-icon.png"
+  brand_color: "#006AFD"
+  default_prompt: "Use $swiftui-pro to review my project."
+
+policy:
+  allow_implicit_invocation: true

package/skills/swiftui-pro/assets/swiftui-pro-icon.svg

@@ -0,0 +1,29 @@
+<?xml version="1.0" encoding="UTF-8"?>
+<svg xmlns="http://www.w3.org/2000/svg" width="227.72" height="227.72" xmlns:xlink="http://www.w3.org/1999/xlink" version="1.1" viewBox="0 0 227.72 227.72">
+  <defs>
+    <style>
+      .st0 {
+        fill: none;
+        stroke: url(#linear-gradient1);
+        stroke-miterlimit: 10;
+        stroke-width: 6px;
+      }
+
+      .st1 {
+        fill: url(#linear-gradient);
+        fill-rule: evenodd;
+      }
+    </style>
+    <linearGradient id="linear-gradient" x1="58.405" y1="206.955" x2="178.785" y2="86.575" gradientTransform="translate(0 260) scale(1 -1)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#00d9ff"/>
+      <stop offset="1" stop-color="#006efd"/>
+    </linearGradient>
+    <linearGradient id="linear-gradient1" x1="33.349" y1="218.651" x2="194.371" y2="57.629" gradientTransform="translate(0 252) scale(1 -1)" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#00eeaf"/>
+      <stop offset="0" stop-color="#00d8ff"/>
+      <stop offset="1" stop-color="#006ffd"/>
+    </linearGradient>
+  </defs>
+  <path class="st1" d="M165.43,131.08c3.87-8.17,16.03-46.62-38.6-85.38,7.61,7.03,40.19,39.2,26.05,75.5-34.2-25.27-87.91-66.75-87.91-66.75,0,0,63.69,60.57,83.58,79.15,19.9,18.59,26.97,27.71,26.47,43.59,0,.01,14.58-23.23-9.59-46.11ZM130.89,145.79c-39.35,18.56-78.42-20.82-78.42-20.82,0,0,21.12,26.7,45.19,35.06,33.72,11.71,54.61-9.64,54.61-9.64L52.42,59.03s56.43,62.62,78.47,86.76Z"/>
+  <circle class="st0" cx="113.86" cy="113.86" r="110.86"/>
+</svg>

package/skills/swiftui-pro/references/accessibility.md

@@ -0,0 +1,13 @@
+# Accessibility
+
+- Respect the user’s accessibility settings for fonts, colors, animations, and more.
+- Do not force specific font sizes. Prefer Dynamic Type (`.font(.body)`, `.font(.headline)`, etc.).
+- If you *need* a custom font size, use `@ScaledMetric` when targeting iOS 18 and earlier. When targeting iOS 26 or later, `.font(.body.scaled(by:))` is also available to get font size adjustment.
+- Flag instances where images have unclear or unhelpful VoiceOver readings, e.g. `Image(.newBanner2026)`. If they are decorative, suggest using `Image(decorative:)` or `accessibilityHidden()`, otherwise attach an `accessibilityLabel()`.
+- If the user has “Reduce Motion” enabled, replace large, motion-based animations with opacity instead.
+- If buttons have complex or frequently changing labels, recommend using `accessibilityInputLabels()` to provide better Voice Control commands. For example, if a button had a live-updating share price for Apple such as “AAPL $271.68”, adding an input label for “Apple” would be a big improvement.
+- Buttons with image labels must always include text, even if the text is invisible: `Button("Label", systemImage: "plus", action: myAction)`. Flag icon-only buttons that lack a text label as being bad for VoiceOver.
+- If color is an important differentiator in the user interface, make sure to respect the environment’s `.accessibilityDifferentiateWithoutColor` setting by showing some kind of variation beyond just color – icons, patterns, strokes, etc.
+- The same is true of `Menu`: using `Menu("Options", systemImage: "ellipsis.circle") { }` is much better than just using an image.
+- Never use `onTapGesture()` unless you specifically need tap location or tap count. All other tappable elements should be a `Button`.
+- If `onTapGesture()` must be used, make sure to add `.accessibilityAddTraits(.isButton)` or similar so it can be read by VoiceOver correctly.

package/skills/swiftui-pro/references/api.md

@@ -0,0 +1,39 @@
+# Using modern SwiftUI API
+
+- Always use `foregroundStyle()` instead of `foregroundColor()`.
+- Always use `clipShape(.rect(cornerRadius:))` instead of `cornerRadius()`.
+- Always use the `Tab` API instead of `tabItem()`.
+- Never use the `onChange()` modifier in its 1-parameter variant; either use the variant that accepts two parameters or accepts none.
+- Do not use `GeometryReader` if a newer alternative works: `containerRelativeFrame()`, `visualEffect()`, or the `Layout` protocol. Flag `GeometryReader` usage and suggest the modern alternative.
+- When designing haptic effects, prefer using `sensoryFeedback()` over older UIKit APIs such as `UIImpactFeedbackGenerator`.
+- Use the `@Entry` macro to define custom `EnvironmentValues`, `FocusValues`, `Transaction`, and `ContainerValues` keys. This replaces the legacy pattern of manually creating a type conforming to (for example) `EnvironmentKey` with a `defaultValue`, then extending `EnvironmentValues` with a computed property.
+- Strongly prefer `overlay(alignment:content:)` over the deprecated `overlay(_:alignment:)`. For example, use `.overlay { Text("Hello, world!") }` rather than `.overlay(Text("Hello, world!"))`.
+- Never use `.navigationBarLeading` and `.navigationBarTrailing` for toolbar item placement; they are deprecated. The correct, modern placements are `.topBarLeading` and `.topBarTrailing`.
+- Prefer to rely on automatic grammar agreement when dealing with English, French, German, Portuguese, Spanish, and Italian. For example, use `Text("^[\(people) person](inflect: true)")` to show a number of people.
+- You can fill and stroke a shape with two chained modifiers; you do *not* need an overlay for the stroke. The overlay was required previously, but this is fixed in iOS 17 and later.
+- When referencing images from an asset catalog, prefer the generated symbol asset API when the project is configured to use them: `Image(.avatar)` rather than `Image("avatar")`.
+- When targeting iOS 26 and later, SwiftUI has a native `WebView` view type that replaces almost all uses of hand-wrapped `WKWebView` inside `UIViewRepresentable`. To use it, make sure to include `import WebKit`.
+- `ForEach` over an `enumerated()` sequence should not convert to an array first. Use `ForEach(items.enumerated(), id: \.element.id)` directly.
+- When hiding scroll indicators, use `.scrollIndicators(.hidden)` rather than `showsIndicators: false` in the initializer.
+- Never use `Text` concatenation with `+`.
+
+For example, the usage of `+` here is bad and deprecated:
+
+```swift
+Text("Hello").foregroundStyle(.red)
++
+Text("World").foregroundStyle(.blue)
+```
+
+Instead, use text interpolation like this:
+
+```swift
+let red = Text("Hello").foregroundStyle(.red)
+let blue = Text("World").foregroundStyle(.blue)
+Text("\(red)\(blue)")
+```
+
+
+## Using ObservableObject
+
+If using `ObservableObject` is absolutely required – for example if you are trying to create a debouncer using a Combine publisher – you should always make sure `import Combine` is added. This was previously provided through SwiftUI, but that is no longer the case.

package/skills/swiftui-pro/references/data.md

@@ -0,0 +1,43 @@
+# Data flow, shared state, and property wrappers
+
+It is important that SwiftUI body code and logic code be kept separate in order to make code easier to read, write, and maintain. That usually means placing code into methods rather than inline in the `body` property, but often also means carving functionality out into separate `@Observable` classes.
+
+These rules help ensure code is efficient and works well in the long term.
+
+
+## Shared state
+
+- `@Observable` classes must be marked `@MainActor` unless the project has Main Actor default actor isolation. Flag any `@Observable` class missing this annotation.
+- All shared data should use `@Observable` classes with `@State` (for ownership) and `@Bindable` / `@Environment` (for passing).
+- Strongly prefer not to use `ObservableObject`, `@Published`, `@StateObject`, `@ObservedObject`, or `@EnvironmentObject` unless they are unavoidable, or if they exist in legacy/integration contexts when changing architecture would be complicated.
+
+
+## Local state
+
+- `@State` should be marked `private` and only owned by the view that created it.
+- If a view stores a class instance that contains expensive-to-recompute data, e.g. `CIContext`, it can be stored using `@State` even though it is not an observable object. This effectively uses `@State` as a cache – storing something persistently, but not doing any change tracking on it since it's not an observable object.
+
+
+## Bindings
+
+- Strongly prefer to avoid creating bindings using `Binding(get:set:)` in view body code. It is much cleaner and simpler to use a binding provided by `@State`, `@Binding` or similar, then use `onChange()` to trigger any effects.
+- If the user needs to enter a number into a `TextField`, bind the `TextField` to a numeric value such as `Int` or `Double`, then use its `format` initializer like this: `TextField("Enter your score", value: $score, format: .number)`. Apply either `.keyboardType(.numberPad)` (for integers) or `.keyboardType(.decimalPad)` (for floating-point numbers) as appropriate. Using the modifier alone is *not* sufficient.
+
+
+## Working with data
+
+- Prefer to make structs conform to `Identifiable` rather than using `id: \.someProperty` in SwiftUI code.
+- Never attempt to use `@AppStorage` inside an `@Observable` class, even if marked `@ObservationIgnored` – it will *not* trigger view updates when a change happens.
+
+
+## SwiftData
+
+- If you only need the number of items matching a query, consider `ModelContext.fetchCount()` with a fetch descriptor. This will *not* live update if the data changes unless something else triggers the update, such as `@Query`, so it should be used carefully.
+
+For more help with SwiftData, suggest the [SwiftData Pro agent skill](https://github.com/twostraws/swiftdata-agent-skill).
+
+## If the project uses SwiftData with CloudKit
+
+- Never use `@Attribute(.unique)`.
+- Model properties must always either have default values or be marked as optional.
+- All relationships must be marked optional.

package/skills/swiftui-pro/references/design.md

@@ -0,0 +1,31 @@
+# Design
+
+## Creating a uniform design in this app
+
+Prefer to place standard fonts, sizes, colors, stack spacing, padding, rounding, animation timings, and more into a shared enum of constants, so they can be used by all views. This allows the app’s design to feel uniform and consistent, and be adjusted easily.
+
+
+## Requirements for flexible, accessible design
+
+- Never use `UIScreen.main.bounds` to read available space; prefer alternatives such as `containerRelativeFrame()`, or `visualEffect()` as appropriate, or (if there is no alternative) `GeometryReader`.
+- Prefer to avoid fixed frames for views unless content can fit neatly inside; this can cause problems across different device sizes, different Dynamic Type settings, and more. Giving frames some flexibility is usually preferred.
+- Apple’s minimum acceptable tap area for interactions on iOS is 44x44. Ensure this is strictly enforced.
+
+
+## Standard system styling
+
+- Strongly prefer to use `ContentUnavailableView` when data is missing or empty, rather than designing something custom.
+- When using `searchable()`, you can show empty results using `ContentUnavailableView.search` and it will include the search term they used automatically – there’s no need to use `ContentUnavailableView.search(text: searchText)` or similar.
+- If you need an icon and some text placed horizontally side by side, prefer `Label` over `HStack`.
+- Prefer system hierarchical styles (e.g. secondary/tertiary) over manual opacity when possible, so the system can adapt to the correct context automatically.
+- When using `Form`, wrap controls such as `Slider` in `LabeledContent` so the title and control are laid out correctly.
+- When using `RoundedRectangle`, the default rounding style is `.continuous` – there is no need to specify it explicitly.
+
+
+## Ensuring designs work for everyone
+
+- Use `bold()` instead of `fontWeight(.bold)`, because using `bold()` allows the system to choose the correct weight for the current context.
+- Only use `fontWeight()` for weights other than bold when there's an important reason - scattering around `fontWeight(.medium)` or `fontWeight(.semibold)` is counterproductive.
+- Avoid hard-coded values for padding and stack spacing unless specifically requested.
+- Avoid UIKit colors (`UIColor`) in SwiftUI code; use SwiftUI `Color` or asset catalog colors.
+- The font size `.caption2` is extremely small, and is generally best avoided. Even the font size `.caption` is on the small side, and should be used carefully.

package/skills/swiftui-pro/references/hygiene.md

@@ -0,0 +1,9 @@
+# Hygiene
+
+- If the project requires secrets such as API keys, never include them in the repository.
+- Code comments and documentation comments should be present where the logic isn't self-evident.
+- Unit tests should exist for core application logic. UI tests only where unit tests are not possible.
+- `@AppStorage` must never be used to store usernames, passwords, or other sensitive data. Use the keychain for that.
+- If SwiftLint is configured, it should return no warnings or errors.
+- If the project uses Localizable.xcstrings, prefer to add user-facing strings using symbol keys (e.g. “helloWorld”) in the string catalog with `extractionState` set to "manual", accessing them via generated symbols such as `Text(.helloWorld)`. Offer to translate new keys into all languages supported by the project.
+- If the Xcode MCP is configured, prefer its tools over generic alternatives. For example, `RenderPreview` is able to capture images of rendered SwiftUI previews for examination, and `DocumentationSearch` can search Apple’s documentation for latest usage instructions.

package/skills/swiftui-pro/references/navigation.md

@@ -0,0 +1,14 @@
+# Navigation and presentation
+
+- Use `NavigationStack` or `NavigationSplitView` as appropriate; flag all use of the deprecated `NavigationView`.
+- Strongly prefer to use `navigationDestination(for:)` to specify destinations; flag all use of the old `NavigationLink(destination:)` pattern where it should be replaced.
+- Never mix `navigationDestination(for:)` and `NavigationLink(destination:)` in the same navigation hierarchy; it causes significant problems.
+- `navigationDestination(for:)` must be registered once per data type; flag duplicates.
+
+
+## Alerts, confirmation dialogs, and sheets
+
+- Always attach `confirmationDialog()` to the user interface that triggers the dialog. This allows Liquid Glass animations to move from the correct source.
+- If an alert has only a single “OK” button that does nothing but dismiss the alert, it can be omitted entirely: `.alert("Dismiss Me", isPresented: $isShowingAlert) { }`.
+- If a sheet is designed to present an optional piece of data, prefer `sheet(item:)` over `sheet(isPresented:)` so the optional is safely unwrapped.
+- When using `sheet(item:)` with a view that accepts the item as its only initializer parameter, prefer `sheet(item: $someItem, content: SomeView.init)` over `sheet(item: $someItem) { someItem in SomeView(item: someItem) }`.