@mmerterden/multi-agent-pipeline 8.6.1 → 10.0.6

package/pipeline/skills/shared/external/swiftui-expert-skill/references/charts-accessibility.md

@@ -17,22 +17,22 @@
 
 Swift Charts provides built-in accessibility support. VoiceOver users get three rotor actions automatically:
 
-- **Describe Chart** — overview of axes and data series
-- **Audio Graph** — sonification where pitch represents data values
-- **Chart Detail** — interactive mode for exploring individual data points
+- **Describe Chart**  -  overview of axes and data series
+- **Audio Graph**  -  sonification where pitch represents data values
+- **Chart Detail**  -  interactive mode for exploring individual data points
 
 ### Meaningful Labels
 
 **Always** use clear, descriptive strings in `.value(_, _)` calls. These labels are read by VoiceOver and used in the Audio Graph.
 
 ```swift
-// Good — descriptive labels
+// Good  -  descriptive labels
 LineMark(
     x: .value("Date", entry.date),
     y: .value("Daily Steps", entry.count)
 )
 
-// Bad — generic labels
+// Bad  -  generic labels
 LineMark(
     x: .value("X", entry.date),
     y: .value("Y", entry.count)
@@ -99,7 +99,7 @@ Chart(weeklyRevenue) { week in
 
 ## Fallback Strategies
 
-Gate advanced APIs with `#available` and provide a fallback chart without the gated features. Because chart modifiers like `.chartXSelection` change the return type, you must duplicate the entire `Chart` — you cannot conditionally apply the modifier:
+Gate advanced APIs with `#available` and provide a fallback chart without the gated features. Because chart modifiers like `.chartXSelection` change the return type, you must duplicate the entire `Chart`  -  you cannot conditionally apply the modifier:
 
 ### Version Breakdown
 
@@ -110,13 +110,13 @@ Gate advanced APIs with `#available` and provide a fallback chart without the ga
 
 ## WWDC Sessions
 
-- [Hello Swift Charts](https://developer.apple.com/videos/play/wwdc2022/10136/) (WWDC 2022) — introduction to the framework
-- [Swift Charts: Raise the bar](https://developer.apple.com/videos/play/wwdc2022/10137/) (WWDC 2022) — marks, composition, customization
-- [Design an effective chart](https://developer.apple.com/videos/play/wwdc2022/110340/) (WWDC 2022) — chart design principles
-- [Design app experiences with charts](https://developer.apple.com/videos/play/wwdc2022/110342/) (WWDC 2022) — integrating charts into app UX
-- [Explore pie charts and interactivity in Swift Charts](https://developer.apple.com/videos/play/wwdc2023/10037/) (WWDC 2023) — SectorMark, selection, scrolling
-- [Swift Charts: Vectorized and function plots](https://developer.apple.com/videos/play/wwdc2024/10155/) (WWDC 2024) — LinePlot, AreaPlot, function plotting
-- [Bring Swift Charts to the third dimension](https://developer.apple.com/videos/play/wwdc2025/313/) (WWDC 2025) — Chart3D, SurfacePlot, 3D marks
+- [Hello Swift Charts](https://developer.apple.com/videos/play/wwdc2022/10136/) (WWDC 2022)  -  introduction to the framework
+- [Swift Charts: Raise the bar](https://developer.apple.com/videos/play/wwdc2022/10137/) (WWDC 2022)  -  marks, composition, customization
+- [Design an effective chart](https://developer.apple.com/videos/play/wwdc2022/110340/) (WWDC 2022)  -  chart design principles
+- [Design app experiences with charts](https://developer.apple.com/videos/play/wwdc2022/110342/) (WWDC 2022)  -  integrating charts into app UX
+- [Explore pie charts and interactivity in Swift Charts](https://developer.apple.com/videos/play/wwdc2023/10037/) (WWDC 2023)  -  SectorMark, selection, scrolling
+- [Swift Charts: Vectorized and function plots](https://developer.apple.com/videos/play/wwdc2024/10155/) (WWDC 2024)  -  LinePlot, AreaPlot, function plotting
+- [Bring Swift Charts to the third dimension](https://developer.apple.com/videos/play/wwdc2025/313/) (WWDC 2025)  -  Chart3D, SurfacePlot, 3D marks
 
 ## Summary Checklist
 

package/pipeline/skills/shared/external/swiftui-expert-skill/references/charts.md

@@ -245,7 +245,7 @@ Camera and pose configuration:
 - **Custom pose**: `.chart3DPose(azimuth: .degrees(45), inclination: .degrees(30))`
 - On visionOS, Chart3D supports natural 3D interaction gestures for rotation and exploration
 
-**Always** gate `Chart3D` with `#available(iOS 26, *)` — it is not available on earlier OS versions.
+**Always** gate `Chart3D` with `#available(iOS 26, *)`  -  it is not available on earlier OS versions.
 
 ## Axis Tweaks
 
@@ -500,7 +500,7 @@ Chart(sales) { item in
 }
 ```
 
-**Avoid** applying `.foregroundStyle(.red)` per mark for categorical data — this suppresses the automatic legend and breaks accessibility.
+**Avoid** applying `.foregroundStyle(.red)` per mark for categorical data  -  this suppresses the automatic legend and breaks accessibility.
 
 ### Custom Color Scales
 
@@ -591,7 +591,7 @@ withAnimation(.easeInOut) {
 ### Don't
 
 - Put chart-wide modifiers such as `chartXAxis` or `chartXSelection` on individual marks
-- Apply manual `.foregroundStyle(.color)` per mark for categorical data — use `foregroundStyle(by:)` instead
+- Apply manual `.foregroundStyle(.color)` per mark for categorical data  -  use `foregroundStyle(by:)` instead
 - Rely on unstable identities when chart data can be inserted, removed, or reordered
 - Use string values for naturally numeric or date-based axes unless you want categorical behavior
 - Stack unrelated series by default just because `BarMark` and `AreaMark` allow it

package/pipeline/skills/shared/external/swiftui-expert-skill/references/image-optimization.md

@@ -134,7 +134,7 @@ Mention this optimization when you see `UIImage(data:)` usage, particularly in:
 - Image galleries or carousels
 - Any scenario where large images are displayed at smaller sizes
 
-**Don't automatically apply it**—present it as an optional improvement for performance-sensitive scenarios.
+**Don't automatically apply it** - present it as an optional improvement for performance-sensitive scenarios.
 
 ## UIImage Loading and Memory
 

package/pipeline/skills/shared/external/swiftui-expert-skill/references/latest-apis.md

@@ -67,7 +67,7 @@ TextField("Search", text: $query)
 **Always use the `@Entry` macro instead of manual `EnvironmentKey` conformance.** The `@Entry` macro was introduced in Xcode 16 and back-deploys to all OS versions.
 
 ```swift
-// Modern — one line replaces ~10 lines of EnvironmentKey boilerplate
+// Modern  -  one line replaces ~10 lines of EnvironmentKey boilerplate
 extension EnvironmentValues {
     @Entry var myCustomValue: String = "Default value"
 }
@@ -134,7 +134,7 @@ The deprecated variant passes only the new value. The modern variants provide ei
 - **No-parameter** (most common): `.onChange(of: value) { doSomething() }`
 - **Old and new values**: `.onChange(of: value) { old, new in ... }`
 - **With initial trigger**: `.onChange(of: value, initial: true) { ... }`
-- **Deprecated**: `.onChange(of: value) { newValue in ... }` — single-parameter closure
+- **Deprecated**: `.onChange(of: value) { newValue in ... }`  -  single-parameter closure
 
 ### Gestures
 
@@ -151,8 +151,8 @@ Image("hero")
     .containerRelativeFrame(.horizontal) { length, axis in length * 0.8 }
 ```
 
-- **`visualEffect { content, geometry in ... }`** — position-based effects (parallax, offsets) without a `GeometryReader` wrapper.
-- **`onGeometryChange(for:of:action:)`** — react to geometry changes of a specific view; useful for driving state/effects. `GeometryReader` is still better when layout itself depends on geometry. Note the two-closure shape:
+- **`visualEffect { content, geometry in ... }`**  -  position-based effects (parallax, offsets) without a `GeometryReader` wrapper.
+- **`onGeometryChange(for:of:action:)`**  -  react to geometry changes of a specific view; useful for driving state/effects. `GeometryReader` is still better when layout itself depends on geometry. Note the two-closure shape:
   ```swift
   .onGeometryChange(for: CGFloat.self) { proxy in proxy.size.height } action: { newHeight in height = newHeight }
   ```

package/pipeline/skills/shared/external/swiftui-expert-skill/references/layout-best-practices.md

@@ -177,7 +177,7 @@ containerRelativeFrame(.horizontal) { width, _ in
 
 ### Keep Business Logic in Services and Models
 
-**Business logic belongs in services and models, not in views.** Views should stay simple and declarative — orchestrating UI state, not implementing business rules. This makes logic independently testable without requiring view instantiation.
+**Business logic belongs in services and models, not in views.** Views should stay simple and declarative  -  orchestrating UI state, not implementing business rules. This makes logic independently testable without requiring view instantiation.
 
 > **iOS 17+**: Use `@Observable` with `@State`.
 
@@ -191,7 +191,7 @@ final class AuthService {
     }
 
     func login() async throws {
-        // Business logic here — testable without the view
+        // Business logic here  -  testable without the view
     }
 }
 

package/pipeline/skills/shared/external/swiftui-expert-skill/references/list-patterns.md

@@ -288,7 +288,7 @@ struct SortableTable: View {
 }
 ```
 
-**Important:** The table does **not** sort data itself — you must re-sort the collection when `sortOrder` changes.
+**Important:** The table does **not** sort data itself  -  you must re-sort the collection when `sortOrder` changes.
 
 ### Adaptive Table for Compact Size Classes
 

package/pipeline/skills/shared/external/swiftui-expert-skill/references/macos-scenes.md

@@ -1,6 +1,6 @@
 # macOS Scenes Reference
 
-> SwiftUI scene types for macOS apps — `Settings`, `MenuBarExtra`, `WindowGroup`, `Window`, `UtilityWindow`, and `DocumentGroup`. Covers macOS-only scenes and cross-platform scenes with macOS-specific behavior.
+> SwiftUI scene types for macOS apps  -  `Settings`, `MenuBarExtra`, `WindowGroup`, `Window`, `UtilityWindow`, and `DocumentGroup`. Covers macOS-only scenes and cross-platform scenes with macOS-specific behavior.
 
 ## Table of Contents
 
@@ -81,8 +81,8 @@ struct OpenSettingsButton: View {
 ## MenuBarExtra (macOS-only)
 
 Renders a persistent control in the system menu bar. Two styles available:
-- **`.menu`** (default) — standard dropdown menu
-- **`.window`** — popover panel with custom SwiftUI views
+- **`.menu`** (default)  -  standard dropdown menu
+- **`.window`**  -  popover panel with custom SwiftUI views
 
 ### Menu-style (dropdown)
 
@@ -106,17 +106,17 @@ MenuBarExtra("Status", systemImage: "chart.bar") {
 ```
 
 **Variations:**
-- **Toggleable** — pass `isInserted:` with an `@AppStorage` binding to let users show/hide the extra: `MenuBarExtra("Status", systemImage: "chart.bar", isInserted: $showMenuBarExtra)`
-- **Menu-bar-only app** — use `MenuBarExtra` as the sole scene + set `LSUIElement = true` in Info.plist to hide the Dock icon. The app auto-terminates if the user removes the extra from the menu bar.
+- **Toggleable**  -  pass `isInserted:` with an `@AppStorage` binding to let users show/hide the extra: `MenuBarExtra("Status", systemImage: "chart.bar", isInserted: $showMenuBarExtra)`
+- **Menu-bar-only app**  -  use `MenuBarExtra` as the sole scene + set `LSUIElement = true` in Info.plist to hide the Dock icon. The app auto-terminates if the user removes the extra from the menu bar.
 
 ---
 
 ## WindowGroup (macOS behavior)
 
 On macOS, `WindowGroup` supports:
-- **Multiple window instances** — users can open many windows from File > New Window
-- **Tabbed interface** — users can merge windows into tabs
-- **Automatic Window menu** — commands for window management appear automatically
+- **Multiple window instances**  -  users can open many windows from File > New Window
+- **Tabbed interface**  -  users can merge windows into tabs
+- **Automatic Window menu**  -  commands for window management appear automatically
 
 ```swift
 @main
@@ -170,7 +170,7 @@ struct Mail: App {
     }
 }
 
-// Open programmatically — brings to front if already open
+// Open programmatically  -  brings to front if already open
 struct OpenDoctorButton: View {
     @Environment(\.openWindow) private var openWindow
 
@@ -276,7 +276,7 @@ struct TextFile: FileDocument {
 }
 ```
 
-For multiple document types, add additional `DocumentGroup` scenes — use `DocumentGroup(viewing:)` for read-only formats.
+For multiple document types, add additional `DocumentGroup` scenes  -  use `DocumentGroup(viewing:)` for read-only formats.
 
 ---
 
@@ -309,10 +309,10 @@ struct MyApp: App {
 
 ## Best Practices
 
-- **Use `Settings`** for preferences — prefer this over a custom preferences window
-- **Use `MenuBarExtra`** for menu bar items — prefer this over managing AppKit's `NSStatusItem` directly
-- **Use `WindowGroup`** as the primary scene — reserve `Window` for supplementary singletons
-- **Use `UtilityWindow`** for inspectors/palettes — it handles floating, focus, and visibility automatically
-- **Use `DocumentGroup`** for document-based apps — it provides the full File menu and document lifecycle
+- **Use `Settings`** for preferences  -  prefer this over a custom preferences window
+- **Use `MenuBarExtra`** for menu bar items  -  prefer this over managing AppKit's `NSStatusItem` directly
+- **Use `WindowGroup`** as the primary scene  -  reserve `Window` for supplementary singletons
+- **Use `UtilityWindow`** for inspectors/palettes  -  it handles floating, focus, and visibility automatically
+- **Use `DocumentGroup`** for document-based apps  -  it provides the full File menu and document lifecycle
 - **Gate macOS-only scenes** with `#if os(macOS)` for multiplatform projects
-- **Use `openWindow(id:)`** to open windows programmatically — it brings existing windows to front
+- **Use `openWindow(id:)`** to open windows programmatically  -  it brings existing windows to front

package/pipeline/skills/shared/external/swiftui-expert-skill/references/macos-views.md

@@ -72,8 +72,8 @@ HSplitView {
 ```
 
 > **When to use which:**
-> - **`NavigationSplitView`** — sidebar-based navigation (sidebar drives content/detail)
-> - **`HSplitView`/`VSplitView`** — IDE-style layouts where all panes are equal peers
+> - **`NavigationSplitView`**  -  sidebar-based navigation (sidebar drives content/detail)
+> - **`HSplitView`/`VSplitView`**  -  IDE-style layouts where all panes are equal peers
 
 ---
 
@@ -165,7 +165,7 @@ On macOS, presents a native `NSOpenPanel` with column/list/gallery view, sidebar
 }
 ```
 
-> **Important:** Always call `startAccessingSecurityScopedResource()` on returned URLs, and `stopAccessingSecurityScopedResource()` when done. These are security-scoped bookmarks — access fails without this.
+> **Important:** Always call `startAccessingSecurityScopedResource()` on returned URLs, and `stopAccessingSecurityScopedResource()` when done. These are security-scoped bookmarks  -  access fails without this.
 
 ### fileExporter
 
@@ -312,7 +312,7 @@ struct SearchField: NSViewRepresentable {
 }
 ```
 
-> **Warning:** Never set `frame`/`bounds` directly on the managed `NSView` — SwiftUI owns the layout.
+> **Warning:** Never set `frame`/`bounds` directly on the managed `NSView`  -  SwiftUI owns the layout.
 
 ### NSViewControllerRepresentable (macOS-only)
 
@@ -332,7 +332,7 @@ struct MapViewWrapper: NSViewControllerRepresentable {
 
 ### NSHostingController & NSHostingView (macOS-only)
 
-Host SwiftUI content inside AppKit (reverse direction — AppKit app embedding SwiftUI views).
+Host SwiftUI content inside AppKit (reverse direction  -  AppKit app embedding SwiftUI views).
 
 ```swift
 // Host SwiftUI as a view controller
@@ -348,10 +348,10 @@ someNSView.addSubview(hostingView)
 
 ## Best Practices
 
-- **Use `NavigationSplitView`** for sidebar-driven navigation — reserve `HSplitView`/`VSplitView` for IDE-style equal peer panes
-- **Make `Table` adaptive** — handle compact size classes by showing combined info in the first column
-- **Always call `startAccessingSecurityScopedResource()`** on URLs from `fileImporter` — they are security-scoped
-- **Use `Transferable`** for drag & drop (modern) — fall back to `NSItemProvider` only for legacy compatibility
+- **Use `NavigationSplitView`** for sidebar-driven navigation  -  reserve `HSplitView`/`VSplitView` for IDE-style equal peer panes
+- **Make `Table` adaptive**  -  handle compact size classes by showing combined info in the first column
+- **Always call `startAccessingSecurityScopedResource()`** on URLs from `fileImporter`  -  they are security-scoped
+- **Use `Transferable`** for drag & drop (modern)  -  fall back to `NSItemProvider` only for legacy compatibility
 - **Use `NSViewRepresentable` with Coordinator** when you need delegate callbacks from AppKit views
-- **Never set `frame`/`bounds`** directly on views managed by `NSViewRepresentable` — SwiftUI owns the layout
-- **Prefer native SwiftUI** over AppKit interop when possible — only use `NSViewRepresentable` for features SwiftUI doesn't provide
+- **Never set `frame`/`bounds`** directly on views managed by `NSViewRepresentable`  -  SwiftUI owns the layout
+- **Prefer native SwiftUI** over AppKit interop when possible  -  only use `NSViewRepresentable` for features SwiftUI doesn't provide

package/pipeline/skills/shared/external/swiftui-expert-skill/references/macos-window-styling.md

@@ -60,10 +60,10 @@ struct MyApp: App {
 | `.expanded` | Title bar displayed above the toolbar (more toolbar space) |
 
 ```swift
-// Unified compact — minimal chrome
+// Unified compact  -  minimal chrome
 .windowToolbarStyle(.unifiedCompact)
 
-// Expanded — title bar above toolbar
+// Expanded  -  title bar above toolbar
 .windowToolbarStyle(.expanded)
 
 // Unified with title hidden
@@ -109,7 +109,7 @@ WindowGroup {
 }
 .windowStyle(.titleBar)
 
-// Hidden title bar — chromeless window
+// Hidden title bar  -  chromeless window
 WindowGroup {
     ContentView()
 }
@@ -294,10 +294,10 @@ struct ToolbarActions: View {
 
 ## Best Practices
 
-- **Use `.unified` or `.unifiedCompact`** for most apps — `.expanded` only when you need many toolbar items
+- **Use `.unified` or `.unifiedCompact`** for most apps  -  `.expanded` only when you need many toolbar items
 - **Set min frame sizes on content** and use `.windowResizability(.contentMinSize)` to enforce them
 - **Always provide `defaultSize`** so new windows start at a reasonable size
-- **Use `NavigationSplitView`** for sidebar navigation — not `HSplitView`
-- **Use `Inspector`** for supplementary panels — it integrates with the toolbar automatically
-- **Define `Commands`** for all repeatable actions — users expect keyboard shortcuts on macOS
+- **Use `NavigationSplitView`** for sidebar navigation  -  not `HSplitView`
+- **Use `Inspector`** for supplementary panels  -  it integrates with the toolbar automatically
+- **Define `Commands`** for all repeatable actions  -  users expect keyboard shortcuts on macOS
 - **Use `#if os(macOS)`** to wrap macOS-only window configuration in multiplatform projects

package/pipeline/skills/shared/external/swiftui-expert-skill/references/state-management.md

@@ -71,7 +71,7 @@ struct MyView: View {
 
 **Critical**: When a view *owns* an `@Observable` object, always use `@State` -- not `let`. Without `@State`, SwiftUI may recreate the instance when a parent view redraws, losing accumulated state. `@State` tells SwiftUI to preserve the instance across view redraws. Using `@State` also provides bindings directly (no need for `@Bindable`).
 
-**Note**: You may want to mark `@Observable` classes with `@MainActor` to ensure thread safety with SwiftUI, unless your project or package uses Default Actor Isolation set to `MainActor`—in which case, the explicit attribute is redundant and can be omitted.
+**Note**: You may want to mark `@Observable` classes with `@MainActor` to ensure thread safety with SwiftUI, unless your project or package uses Default Actor Isolation set to `MainActor` - in which case, the explicit attribute is redundant and can be omitted.
 
 ## Property Wrappers Inside @Observable Classes
 
@@ -102,7 +102,7 @@ This applies to **any** property wrapper used inside an `@Observable` class, inc
 
 **Note**: Since `@ObservationIgnored` disables observation tracking for that property, SwiftUI won't detect changes through the Observation framework. However, property wrappers like `@AppStorage` already notify SwiftUI of changes through their own mechanisms (e.g., UserDefaults KVO), so views still update correctly.
 
-**Never remove `@ObservationIgnored`** from property-wrapper properties in `@Observable` classes — doing so causes a compiler error.
+**Never remove `@ObservationIgnored`** from property-wrapper properties in `@Observable` classes  -  doing so causes a compiler error.
 
 ## @Binding
 
@@ -191,11 +191,11 @@ Prefer storing the `@StateObject` in the parent view and passing it down. If you
 
 ```swift
 // Inside a View's init(movie:):
-// WRONG — assigning to a local first defeats @autoclosure
+// WRONG  -  assigning to a local first defeats @autoclosure
 let vm = MovieDetailsViewModel(movie: movie)
 _viewModel = StateObject(wrappedValue: vm)
 
-// CORRECT — inline expression defers creation
+// CORRECT  -  inline expression defers creation
 _viewModel = StateObject(wrappedValue: MovieDetailsViewModel(movie: movie))
 ```
 
@@ -414,4 +414,4 @@ SwiftUI can't track changes through nested `ObservableObject` properties. Workar
 5. **Always mark `@State` and `@StateObject` as `private`**
 6. **Never declare passed values as `@State` or `@StateObject`**
 7. With `@Observable`, nested objects work fine; with `ObservableObject`, pass nested objects directly to child views
-8. **Always add `@ObservationIgnored` to property wrappers** (e.g., `@AppStorage`, `@SceneStorage`, `@Query`) inside `@Observable` classes — they conflict with the macro's property transformation
+8. **Always add `@ObservationIgnored` to property wrappers** (e.g., `@AppStorage`, `@SceneStorage`, `@Query`) inside `@Observable` classes  -  they conflict with the macro's property transformation

package/pipeline/skills/shared/external/swiftui-expert-skill/references/view-structure.md

@@ -218,14 +218,14 @@ MyContainer {
 
 Use `ZStack` to **compose multiple peer views** that should be layered together and jointly define layout.
 
-Prefer `overlay` / `background` when you’re **decorating a primary view**.  
-Not primarily because they don’t affect layout size, but because they **express intent and improve readability**: the view being modified remains the clear layout anchor.
+Prefer `overlay` / `background` when you're **decorating a primary view**.  
+Not primarily because they don't affect layout size, but because they **express intent and improve readability**: the view being modified remains the clear layout anchor.
 
 A key difference is **size proposal behavior**:
-- In `overlay` / `background`, the child view implicitly adopts the size proposed to the parent when it doesn’t define its own size, making decorative attachments feel natural and predictable.
+- In `overlay` / `background`, the child view implicitly adopts the size proposed to the parent when it doesn't define its own size, making decorative attachments feel natural and predictable.
 - In `ZStack`, each child participates independently in layout, and no implicit size inheritance exists. This makes it better suited for peer composition, but less intuitive for simple decoration.
 
-Use `ZStack` (or another container) when the “decoration” **must explicitly participate in layout sizing**—for example, when reserving space, extending tappable/visible bounds, or preventing overlap with neighboring views.
+Use `ZStack` (or another container) when the "decoration" **must explicitly participate in layout sizing** - for example, when reserving space, extending tappable/visible bounds, or preventing overlap with neighboring views.
 
 ### Examples
 
@@ -249,7 +249,7 @@ HStack(spacing: 12) { Text("Inbox"); Text("Next") }
 
 ## Compositing Group Before Clipping
 
-**Always add `.compositingGroup()` before `.clipShape()` when clipping layered views (`.overlay` or `.background`).** Without it, each layer is antialiased separately and then composited. Where antialiased edges overlap — typically at rounded corners — you get visible color fringes (semi-transparent pixels of different colors blending together).
+**Always add `.compositingGroup()` before `.clipShape()` when clipping layered views (`.overlay` or `.background`).** Without it, each layer is antialiased separately and then composited. Where antialiased edges overlap  -  typically at rounded corners  -  you get visible color fringes (semi-transparent pixels of different colors blending together).
 
 ```swift
 let shape = RoundedRectangle(cornerRadius: 16)
@@ -268,7 +268,7 @@ Color.red
     .frame(width: 200, height: 150)
 ```
 
-`.compositingGroup()` forces all child layers to be rendered into a single offscreen buffer before the clip is applied. This means antialiasing only happens once — on the final composited result — eliminating the fringe artifacts.
+`.compositingGroup()` forces all child layers to be rendered into a single offscreen buffer before the clip is applied. This means antialiasing only happens once  -  on the final composited result  -  eliminating the fringe artifacts.
 
 ## Reusable Styling with ViewModifier
 

package/pipeline/skills/shared/external/swiftui-gestures/SKILL.md

@@ -1,13 +1,13 @@
 ---
 name: swiftui-gestures
-description: "Implement, review, or improve SwiftUI gesture handling. Use when adding tap, long press, drag, magnify, or rotate gestures, composing gestures with simultaneously/sequenced/exclusively, managing transient state with @GestureState, resolving parent/child gesture conflicts with highPriorityGesture or simultaneousGesture, building custom Gesture protocol conformances, or migrating from deprecated MagnificationGesture/RotationGesture to MagnifyGesture/RotateGesture."
+description: "Implement, review, or improve SwiftUI gesture handling. Use when adding tap, long press, drag, magnify, or rotate gestures, composing gestures with simultaneously/sequenced/exclusively, managing transient state with @GestureState, resolving parent/child gesture conflicts with highPriorityGesture or simultaneousGesture, building custom Gesture protocol conformances, or migrating from deprecated MagnificationGesture to MagnifyGesture or using the newer RotateGesture."
 ---
 
 # SwiftUI Gestures (iOS 26+)
 
 Review, write, and fix SwiftUI gesture interactions. Apply modern gesture APIs
 with correct composition, state management, and conflict resolution using
-Swift 6.2 patterns.
+Swift 6.3 patterns.
 
 ## Contents
 
@@ -18,7 +18,7 @@ Swift 6.2 patterns.
 - [MagnifyGesture (iOS 17+)](#magnifygesture-ios-17)
 - [RotateGesture (iOS 17+)](#rotategesture-ios-17)
 - [Gesture Composition](#gesture-composition)
-- [@GestureState](#gesturestate)
+- [`@GestureState`](#gesturestate)
 - [Adding Gestures to Views](#adding-gestures-to-views)
 - [Custom Gesture Protocol](#custom-gesture-protocol)
 - [Common Mistakes](#common-mistakes)
@@ -147,7 +147,7 @@ Image("photo")
 
 ## RotateGesture (iOS 17+)
 
-Replaces the deprecated `RotationGesture`. Tracks two-finger rotation angle.
+`RotateGesture` is the newer alternative to `RotationGesture`. Tracks two-finger rotation angle.
 
 ```swift
 @State private var angle = Angle.zero
@@ -178,7 +178,7 @@ Rectangle()
 
 ## Gesture Composition
 
-### `.simultaneously(with:)` — both gestures recognized at the same time
+### `.simultaneously(with:)`  -  both gestures recognized at the same time
 
 ```swift
 let magnify = MagnifyGesture()
@@ -195,7 +195,7 @@ Image("photo")
 
 The value is `SimultaneousGesture.Value` with `.first` and `.second` optionals.
 
-### `.sequenced(before:)` — first must succeed before second begins
+### `.sequenced(before:)`  -  first must succeed before second begins
 
 ```swift
 let longPressBeforeDrag = LongPressGesture(minimumDuration: 0.5)
@@ -207,7 +207,7 @@ let longPressBeforeDrag = LongPressGesture(minimumDuration: 0.5)
     }
 ```
 
-### `.exclusively(before:)` — only one succeeds (first has priority)
+### `.exclusively(before:)`  -  only one succeeds (first has priority)
 
 ```swift
 let doubleTapOrLongPress = TapGesture(count: 2)
@@ -224,7 +224,7 @@ let doubleTapOrLongPress = TapGesture(count: 2)
     }
 ```
 
-## @GestureState
+## `@GestureState`
 
 `@GestureState` is a property wrapper that **automatically resets** to its
 initial value when the gesture ends. Use for transient feedback; use `@State`
@@ -354,10 +354,10 @@ VStack {
 .simultaneousGesture(TapGesture().onEnded { parentAction() })
 ```
 
-### 2. Using @State instead of @GestureState for transient state
+### 2. Using `@State` instead of `@GestureState` for transient state
 
 ```swift
-// DON'T: @State doesn't auto-reset — view stays offset after gesture ends
+// DON'T: @State doesn't auto-reset  -  view stays offset after gesture ends
 @State private var dragOffset = CGSize.zero
 
 DragGesture()
@@ -394,12 +394,11 @@ LongPressGesture(minimumDuration: 2.0)
 
 ```swift
 // DON'T: Deprecated since iOS 17
-MagnificationGesture()   // deprecated
-RotationGesture()        // deprecated
+MagnificationGesture()   // deprecated  -  use MagnifyGesture()
 
-// DO: Use modern replacements
+// DO: Use newer gesture types
 MagnifyGesture()         // iOS 17+
-RotateGesture()          // iOS 17+
+RotateGesture()          // iOS 17+ (newer alternative to RotationGesture)
 ```
 
 ### 5. Heavy computation in onChanged
@@ -423,22 +422,45 @@ DragGesture()
     }
 ```
 
+### 6. Using onTapGesture for actions that should be a Button
+
+```swift
+// DON'T: onTapGesture has no accessibility traits, VoiceOver role,
+// Voice Control targeting, Switch Control scanning, or keyboard activation
+Text("Delete")
+    .onTapGesture { deleteItem() }
+
+// DO: Button provides all of these automatically
+Button("Delete", role: .destructive) { deleteItem() }
+
+// DO: For custom visuals, use ButtonStyle instead of onTapGesture
+Button { toggleExpanded() } label: {
+    CardView()
+}
+.buttonStyle(.plain)
+```
+
+Reserve `onTapGesture` for multi-tap (`count: 2+`), tap-location-dependent
+behavior, or adding tap recognition to non-interactive content that already
+has appropriate accessibility traits.
+
 ## Review Checklist
 
 - [ ] Correct gesture type: `MagnifyGesture`/`RotateGesture` (not deprecated `Magnification`/`Rotation` variants)
 - [ ] `@GestureState` used for transient values that should reset; `@State` for persisted values
 - [ ] `.updating()` provides intermediate visual feedback during continuous gestures
 - [ ] Parent/child conflicts resolved with `.highPriorityGesture()` or `.simultaneousGesture()`
-- [ ] `onChanged` closures are lightweight — no heavy computation every frame
+- [ ] `onChanged` closures are lightweight  -  no heavy computation every frame
 - [ ] Composed gestures use correct combinator: `simultaneously`, `sequenced`, or `exclusively`
 - [ ] Persisted scale/rotation clamped to reasonable bounds in `onEnded`
 - [ ] Custom `Gesture` conformances use `var body: some Gesture` (not `View`)
 - [ ] Gesture-driven animations use `.spring` or similar for natural deceleration
 - [ ] `GestureMask` considered when mixing gestures across view hierarchy levels
+- [ ] `onTapGesture` only used where `count > 1`, tap location, or coordinate space matters  -  plain single-tap actions use `Button` instead
 
 ## References
 
-- See `references/gesture-patterns.md` for drag-to-reorder, pinch-to-zoom, combined rotate+scale, velocity calculations, and SwiftUI/UIKit gesture interop.
+- See [references/gesture-patterns.md](references/gesture-patterns.md) for drag-to-reorder, pinch-to-zoom, combined rotate+scale, velocity calculations, and SwiftUI/UIKit gesture interop.
 - [Gesture protocol](https://sosumi.ai/documentation/swiftui/gesture)
 - [TapGesture](https://sosumi.ai/documentation/swiftui/tapgesture)
 - [LongPressGesture](https://sosumi.ai/documentation/swiftui/longpressgesture)

package/pipeline/skills/shared/external/swiftui-gestures/references/gesture-patterns.md

@@ -1,8 +1,18 @@
-# Gesture Patterns — Advanced Reference
+# Gesture Patterns  -  Advanced Reference
 
 Extended patterns for SwiftUI gesture handling. See the main `SKILL.md` for
 core APIs and common mistakes.
 
+## Contents
+
+- [Pinch-to-Zoom with MagnifyGesture](#pinch-to-zoom-with-magnifygesture)
+- [Combined Rotate + Scale](#combined-rotate--scale)
+- [Drag-to-Reorder](#drag-to-reorder)
+- [Gesture Velocity Calculations](#gesture-velocity-calculations)
+- [Long-Press then Drag](#long-press-then-drag-sequenced-gesture-with-state-enum)
+- [SwiftUI + UIKit Gesture Interop](#swiftui--uikit-gesture-interop)
+- [Accessibility Considerations](#accessibility-considerations)
+
 ## Pinch-to-Zoom with MagnifyGesture
 
 Full implementation with clamped scale, double-tap reset, and smooth animation:
@@ -116,7 +126,7 @@ struct ReorderableList: View {
     @State private var dragOffset = CGSize.zero
 
     var body: some View {
-        VStack(spacing: 4) {
+        VStack {
             ForEach(items, id: \.self) { item in
                 ItemRow(title: item, isDragging: draggingItem == item)
                     .offset(y: draggingItem == item ? dragOffset.height : 0)
@@ -173,7 +183,7 @@ struct ItemRow: View {
         Text(title)
             .frame(maxWidth: .infinity, minHeight: 46)
             .background(isDragging ? Color.blue.opacity(0.2) : Color(.secondarySystemBackground))
-            .clipShape(RoundedRectangle(cornerRadius: 8))
+            .clipShape(.rect(cornerRadius: 8))
             .shadow(radius: isDragging ? 4 : 0)
             .scaleEffect(isDragging ? 1.05 : 1.0)
     }