@mmerterden/multi-agent-pipeline 8.6.1 → 10.0.6

package/pipeline/skills/shared/external/swiftui-webkit/references/migration-and-fallbacks.md

@@ -1,14 +1,39 @@
 # Migration and Fallbacks
 
 ## Contents
+- Migration goal
+- Decision guide
 - Migrating from `WKWebView` wrappers
+- Incremental migration pattern
 - When `SFSafariViewController` is still the right choice
 - When `ASWebAuthenticationSession` is required
 - When `WKWebView` remains justified
+- Testing the migration
+- Review checklist
+
+## Migration goal
+
+For SwiftUI apps targeting iOS 26+, the default should be native SwiftUI WebKit
+APIs (`WebView`, `WebPage`) instead of a custom `UIViewRepresentable` wrapper
+around `WKWebView`.
+
+The goal is not "delete every `WKWebView` immediately." The goal is to move
+routine embedded web content to the new native surface and keep legacy fallback
+paths only where they are still justified.
+
+## Decision guide
+
+| Use case | Best default |
+|---|---|
+| Embedded app-owned web content in a SwiftUI screen | `WebView` + `WebPage` |
+| OAuth or third-party sign-in | `ASWebAuthenticationSession` |
+| External public site with Safari behavior | `SFSafariViewController` |
+| Back-deploying below iOS 26 or missing required capability | `WKWebView` fallback |
 
 ## Migrating from `WKWebView` wrappers
 
-For SwiftUI apps targeting iOS 26+, start from `WebView` and `WebPage` instead of a `UIViewRepresentable` wrapper around `WKWebView`.
+For SwiftUI apps targeting iOS 26+, start from `WebView` and `WebPage` instead
+of a `UIViewRepresentable` wrapper around `WKWebView`.
 
 Typical mapping:
 
@@ -20,32 +45,121 @@ Typical mapping:
 | `evaluateJavaScript` | `callJavaScript` |
 | custom `WKWebViewConfiguration` usage | `WebPage.Configuration` |
 
-Migrate first when the app is already SwiftUI-native and only kept `WKWebView` because there was no native view before.
+Migrate first when the app is already SwiftUI-native and only kept `WKWebView`
+because there was no native view before.
+
+## Incremental migration pattern
+
+A clean migration is usually screen-by-screen, not all-at-once.
+
+### Start by separating page ownership from view ownership
+
+If the current wrapper mixes:
+
+- page state
+- navigation policy
+- JS calls
+- UI embedding
+
+split those concerns first. Once page logic is no longer trapped inside the
+wrapper, moving to `WebPage` gets much easier.
+
+### Move the simplest screens first
+
+Best first migrations:
+
+- static help center content
+- app-owned account or legal pages
+- embedded flows that only need URL loading, title, and progress
+
+Leave these for later:
+
+- auth flows
+- highly customized legacy UIKit screens
+- surfaces relying on a capability you have not yet mapped to the new API set
+
+### Keep fallback boundaries explicit
+
+Use availability and architecture boundaries instead of mixing two approaches in
+one view body.
+
+```swift
+struct HelpCenterScreen: View {
+    let page = WebPage()
+
+    var body: some View {
+        WebView(page)
+            .task {
+                try? await page.load(URLRequest(url: helpCenterURL))
+            }
+    }
+}
+```
+
+If a fallback is still needed, isolate it in a separate type rather than
+sprinkling `if #available` checks through the screen's core logic.
 
 ## When `SFSafariViewController` is still the right choice
 
-Use `SFSafariViewController` when the app just needs to show an external site with Safari behavior and does not need page-level control.
+Use `SFSafariViewController` when the app just needs to show an external site
+with Safari behavior and does not need page-level control.
 
 Good fits:
+
 - help center article from a public website
 - a legal page or blog post
 - a temporary browse-out flow that should keep Safari chrome and reader behavior
 
-Do not use `SFSafariViewController` when the app needs to observe page state, run JavaScript, or intercept page navigation.
+Do not use `SFSafariViewController` when the app needs to:
+
+- observe page state
+- run JavaScript
+- intercept navigation
+- coordinate in-app page history
 
 ## When `ASWebAuthenticationSession` is required
 
 Use `ASWebAuthenticationSession` for OAuth and third-party sign-in.
 
-This remains true even if the rest of the app uses `WebView` for embedded content.
+This remains true even if the rest of the app uses `WebView` for embedded
+content.
 
-Do not replace auth sessions with embedded web views. The authentication skill owns that flow.
+Do not replace auth sessions with embedded web views. The authentication skill
+owns that flow because the product requirement is secure sign-in, not generic
+web content.
 
 ## When `WKWebView` remains justified
 
 A fallback `WKWebView` path can still make sense when:
-- the app must back-deploy below iOS 26
-- the codebase is still UIKit-first and not ready to move the surface into native SwiftUI WebKit APIs
-- a required legacy-only WebKit capability is not yet available through the new SwiftUI-facing API surface
 
-When you keep `WKWebView`, treat it as a deliberate fallback, not the default architecture for a modern iOS 26+ SwiftUI feature.
+- the app must back-deploy below iOS 26
+- the codebase is still UIKit-first and not ready to move the surface into
+  native SwiftUI WebKit APIs
+- a required legacy-only WebKit capability is not yet available through the new
+  SwiftUI-facing API surface
+- a heavily customized existing surface would create churn without product value
+
+When you keep `WKWebView`, treat it as a deliberate fallback, not the default
+architecture for a modern iOS 26+ SwiftUI feature.
+
+## Testing the migration
+
+For each migrated screen, verify:
+
+- title and URL state still update correctly
+- JavaScript calls still reach the page when needed
+- navigation policy behavior still matches product expectations
+- loading and error states still render at the right time
+- no auth flow accidentally moved from `ASWebAuthenticationSession` to an
+  embedded view
+- fallback `WKWebView` screens stay isolated instead of spreading wrapper logic
+  back into new screens
+
+## Review checklist
+
+- [ ] New SwiftUI-native screens default to `WebView` and `WebPage`
+- [ ] `SFSafariViewController` used only for browse-out Safari-style flows
+- [ ] `ASWebAuthenticationSession` retained for OAuth and sign-in
+- [ ] `WKWebView` kept only where back-deployment or capability gaps justify it
+- [ ] Fallback paths isolated to dedicated wrapper types
+- [ ] No new iOS 26+ feature starts from a `UIViewRepresentable` wrapper by default

package/pipeline/skills/shared/external/tailwind-css/SKILL.md

@@ -1,4 +1,5 @@
 ---
+name: tailwind-css
 description: "Tailwind CSS v4: utility-first styling, responsive design, dark mode, custom themes, component patterns, and cn() utility"
 tags: [tailwind, css, styling, responsive, dark-mode, frontend]
 version: "2025.1"
@@ -289,8 +290,8 @@ function Button({ variant = 'primary', size = 'md', className, children }: Butto
 ## Don'ts
 
 - Do not use `@apply` to recreate components; use component composition instead
-- Do not fight Tailwind with `!important` — restructure class order or use `cn()`
-- Do not create tailwind.config.js for v4 — use CSS `@theme` directive
+- Do not fight Tailwind with `!important`  -  restructure class order or use `cn()`
+- Do not create tailwind.config.js for v4  -  use CSS `@theme` directive
 - Do not mix Tailwind with inline styles for the same property
 - Do not use arbitrary values (`[17px]`) if a standard scale value is close enough
 - Do not nest responsive classes inside each other (redundant, confusing)

package/pipeline/skills/shared/external/testing-backend/SKILL.md

@@ -1,4 +1,5 @@
 ---
+name: testing-backend
 description: "Backend testing: pytest patterns (Python), Jest patterns (Node.js), integration testing, database fixtures/factories, API contract testing"
 tags: [testing, pytest, jest, integration, database, api-testing, backend]
 version: "2025.1"
@@ -301,7 +302,7 @@ describe('POST /api/v1/users', () => {
 ## Database Testing
 
 ```python
-# Isolated transactions — each test rolls back
+# Isolated transactions  -  each test rolls back
 @pytest.fixture
 async def db_session(engine):
     connection = await engine.connect()

package/pipeline/skills/shared/external/tipkit/SKILL.md

@@ -126,12 +126,12 @@ to `TipViewStyle` and implement `makeBody(configuration:)`.
 ```swift
 struct CustomTipStyle: TipViewStyle {
     func makeBody(configuration: Configuration) -> some View {
-        HStack(spacing: 12) {
+        HStack {
             configuration.image?
                 .font(.title2)
                 .foregroundStyle(.tint)
 
-            VStack(alignment: .leading, spacing: 4) {
+            VStack(alignment: .leading) {
                 configuration.title
                     .font(.headline)
                 configuration.message?
@@ -488,7 +488,7 @@ struct DataLossTip: Tip {
 
 ## References
 
-- See `references/tipkit-patterns.md` for complete implementation patterns
+- See [references/tipkit-patterns.md](references/tipkit-patterns.md) for complete implementation patterns
   including custom styles, event-based rules, tip groups, testing strategies,
   onboarding flows, and SwiftUI preview configuration.
 

package/pipeline/skills/shared/external/tipkit/references/tipkit-patterns.md

@@ -2,7 +2,7 @@
 
 Complete implementation patterns for TipKit including custom styles, event-based
 rules, tip groups, testing strategies, onboarding flows, and SwiftUI previews.
-All examples target iOS 17+ with Swift 6.2 conventions.
+All examples target iOS 17+ with Swift 6.3 conventions.
 
 ## Contents
 
@@ -261,14 +261,14 @@ and actions.
 ```swift
 struct BrandedTipStyle: TipViewStyle {
     func makeBody(configuration: Configuration) -> some View {
-        HStack(alignment: .top, spacing: 16) {
+        HStack(alignment: .top) {
             configuration.image?
                 .font(.system(size: 24))
                 .foregroundStyle(.white)
                 .frame(width: 44, height: 44)
                 .background(.blue.gradient, in: RoundedRectangle(cornerRadius: 10))
 
-            VStack(alignment: .leading, spacing: 6) {
+            VStack(alignment: .leading) {
                 configuration.title
                     .font(.headline)
 
@@ -277,7 +277,7 @@ struct BrandedTipStyle: TipViewStyle {
                     .foregroundStyle(.secondary)
 
                 if !configuration.actions.isEmpty {
-                    HStack(spacing: 12) {
+                    HStack {
                         ForEach(configuration.actions) { action in
                             Button(action: action.handler) {
                                 action.label
@@ -286,7 +286,7 @@ struct BrandedTipStyle: TipViewStyle {
                             .buttonStyle(.bordered)
                         }
                     }
-                    .padding(.top, 4)
+                    .padding(.top)
                 }
             }
         }
@@ -320,15 +320,15 @@ A stripped-down style for tips in tight layouts like toolbars or sidebars.
 ```swift
 struct CompactTipStyle: TipViewStyle {
     func makeBody(configuration: Configuration) -> some View {
-        HStack(spacing: 8) {
+        HStack {
             configuration.image?
                 .foregroundStyle(.tint)
 
             configuration.title
                 .font(.caption.bold())
         }
-        .padding(.horizontal, 12)
-        .padding(.vertical, 8)
+        .padding(.horizontal)
+        .padding(.vertical)
         .background(.tint.opacity(0.1), in: Capsule())
     }
 }
@@ -367,7 +367,7 @@ struct HomeView: View {
     }
 
     var body: some View {
-        VStack(spacing: 20) {
+        VStack {
             if let currentTip = tipGroup.currentTip {
                 TipView(currentTip) { action in
                     currentTip.invalidate(reason: .actionPerformed)

package/pipeline/skills/shared/external/typescript-patterns/SKILL.md

@@ -1,4 +1,5 @@
 ---
+name: typescript-patterns
 description: "Modern TypeScript patterns: strict mode, utility types, generics, conditional types, type guards, discriminated unions, Zod validation"
 tags: [typescript, types, generics, zod, validation, frontend, backend]
 version: "2025.1"
@@ -41,19 +42,19 @@ interface User {
   createdAt: Date;
 }
 
-// Partial — all properties optional
+// Partial  -  all properties optional
 type UpdateUserDto = Partial<Pick<User, 'name' | 'email' | 'role'>>;
 
-// Required — all properties required
+// Required  -  all properties required
 type CompleteUser = Required<User>;
 
-// Pick — select specific properties
+// Pick  -  select specific properties
 type UserPreview = Pick<User, 'id' | 'name'>;
 
-// Omit — exclude specific properties
+// Omit  -  exclude specific properties
 type CreateUserDto = Omit<User, 'id' | 'createdAt'>;
 
-// Record — typed key-value map
+// Record  -  typed key-value map
 type RolePermissions = Record<User['role'], string[]>;
 
 const permissions: RolePermissions = {
@@ -62,7 +63,7 @@ const permissions: RolePermissions = {
   viewer: ['read'],
 };
 
-// Extract / Exclude — filter union types
+// Extract / Exclude  -  filter union types
 type AdminOrUser = Extract<User['role'], 'admin' | 'user'>; // 'admin' | 'user'
 type NonAdmin = Exclude<User['role'], 'admin'>; // 'user' | 'viewer'
 
@@ -70,13 +71,13 @@ type NonAdmin = Exclude<User['role'], 'admin'>; // 'user' | 'viewer'
 type FetchResult = ReturnType<typeof fetchUser>; // Promise<User>
 type FetchParams = Parameters<typeof fetchUser>; // [id: string]
 
-// Awaited — unwrap Promise types
+// Awaited  -  unwrap Promise types
 type ResolvedUser = Awaited<ReturnType<typeof fetchUser>>; // User
 
-// Readonly — immutable object
+// Readonly  -  immutable object
 type ImmutableUser = Readonly<User>;
 
-// NonNullable — remove null | undefined
+// NonNullable  -  remove null | undefined
 type DefinitelyString = NonNullable<string | null | undefined>; // string
 ```
 
@@ -316,14 +317,14 @@ const PaginationSchema = z.object({
 
 ## Don'ts
 
-- Do not use `any` — use `unknown` and narrow with type guards
-- Do not use `!` non-null assertion — use proper null checks
-- Do not use `@ts-ignore` — use `@ts-expect-error` with an explanation if needed
-- Do not use `enum` for new code — use `as const` objects or union types
-- Do not use `Function` type — use specific function signatures
+- Do not use `any`  -  use `unknown` and narrow with type guards
+- Do not use `!` non-null assertion  -  use proper null checks
+- Do not use `@ts-ignore`  -  use `@ts-expect-error` with an explanation if needed
+- Do not use `enum` for new code  -  use `as const` objects or union types
+- Do not use `Function` type  -  use specific function signatures
 - Do not cast with `as` when a type guard is possible
-- Do not use `object` type — use `Record<string, unknown>` or specific shapes
-- Do not create "god interfaces" with 20+ properties — split into composable types
+- Do not use `object` type  -  use `Record<string, unknown>` or specific shapes
+- Do not create "god interfaces" with 20+ properties  -  split into composable types
 
 ## Troubleshooting
 

package/pipeline/skills/shared/external/vision-framework/SKILL.md

@@ -6,11 +6,11 @@ description: "Implement computer vision features including text recognition (OCR
 # Vision Framework
 
 Detect text, faces, barcodes, objects, and body poses in images and video using
-on-device computer vision. Patterns target iOS 26+ with Swift 6.2,
+on-device computer vision. Patterns target iOS 26+ with Swift 6.3,
 backward-compatible where noted.
 
-See `references/vision-requests.md` for complete code patterns and
-`references/visionkit-scanner.md` for DataScannerViewController integration.
+See [references/vision-requests.md](references/vision-requests.md) for complete code patterns and
+[references/visionkit-scanner.md](references/visionkit-scanner.md) for DataScannerViewController integration.
 
 ## Contents
 
@@ -36,7 +36,7 @@ Vision has two distinct API layers. Prefer the modern API for new code.
 | Aspect | Modern (iOS 18+) | Legacy |
 |---|---|---|
 | Pattern | `let result = try await request.perform(on: image)` | `VNImageRequestHandler` + completion handler |
-| Request types | Swift types — structs and classes (`RecognizeTextRequest`, `DetectFaceRectanglesRequest`) | ObjC classes (`VNRecognizeTextRequest`, `VNDetectFaceRectanglesRequest`) |
+| Request types | Swift types  -  structs and classes (`RecognizeTextRequest`, `DetectFaceRectanglesRequest`) | ObjC classes (`VNRecognizeTextRequest`, `VNDetectFaceRectanglesRequest`) |
 | Concurrency | Native async/await | Completion handlers or synchronous `perform` |
 | Observations | Typed return values | Cast `results` from `[Any]` |
 | Availability | iOS 18+ / macOS 15+ | iOS 11+ |
@@ -288,7 +288,7 @@ for index in indices {
 }
 ```
 
-See `references/vision-requests.md` for mask composition and Core Image filter
+See [references/vision-requests.md](references/vision-requests.md) for mask composition and Core Image filter
 integration patterns.
 
 ## Object Tracking
@@ -329,7 +329,7 @@ if let result = trackRequest.results?.first {
 
 ## Other Request Types
 
-Vision provides additional requests covered in `references/vision-requests.md`:
+Vision provides additional requests covered in [references/vision-requests.md](references/vision-requests.md):
 
 | Request | Purpose |
 |---|---|
@@ -343,7 +343,7 @@ Vision provides additional requests covered in `references/vision-requests.md`:
 | `DetectHumanBodyPose3DRequest` | 3D human body pose estimation |
 | `DetectHumanHandPoseRequest` | Detect hand joints and finger positions |
 | `DetectAnimalBodyPoseRequest` | Detect animal body joint positions |
-| `DetectFaceCaptureQualityRequest` | Face capture quality scoring (0–1) for photo selection |
+| `DetectFaceCaptureQualityRequest` | Face capture quality scoring (0-1) for photo selection |
 | `TrackRectangleRequest` | Track rectangular objects across video frames |
 | `TrackOpticalFlowRequest` | Optical flow between video frames |
 | `DetectTrajectoriesRequest` | Detect object trajectories in video |
@@ -384,7 +384,7 @@ For model conversion and optimization, see the `coreml` skill.
 ## VisionKit: DataScannerViewController
 
 `DataScannerViewController` provides a full-screen live camera scanner for text
-and barcodes. See `references/visionkit-scanner.md` for complete patterns.
+and barcodes. See [references/visionkit-scanner.md](references/visionkit-scanner.md) for complete patterns.
 
 ### Quick Start
 
@@ -414,7 +414,7 @@ present(scanner, animated: true) {
 ### SwiftUI Integration
 
 Wrap `DataScannerViewController` in `UIViewControllerRepresentable`. See
-`references/visionkit-scanner.md` for the full implementation.
+[references/visionkit-scanner.md](references/visionkit-scanner.md) for the full implementation.
 
 ## Common Mistakes
 
@@ -467,8 +467,8 @@ Wrap `DataScannerViewController` in `UIViewControllerRepresentable`. See
 
 ## References
 
-- Vision request patterns: `references/vision-requests.md`
-- VisionKit scanner integration: `references/visionkit-scanner.md`
+- Vision request patterns: [references/vision-requests.md](references/vision-requests.md)
+- VisionKit scanner integration: [references/visionkit-scanner.md](references/visionkit-scanner.md)
 - Apple docs: [Vision](https://sosumi.ai/documentation/vision) |
   [VisionKit](https://sosumi.ai/documentation/visionkit) |
   [RecognizeTextRequest](https://sosumi.ai/documentation/vision/recognizetextrequest) |

package/pipeline/skills/shared/external/vision-framework/references/vision-requests.md

@@ -2,7 +2,7 @@
 
 Complete implementation patterns for Vision framework requests covering text
 recognition, face detection, barcode scanning, segmentation, classification,
-and video processing. All patterns target iOS 26+ with Swift 6.2 unless noted.
+and video processing. All patterns target iOS 26+ with Swift 6.3 unless noted.
 
 ## Contents
 - Complete Text Recognition Pipeline

package/pipeline/skills/shared/external/vision-framework/references/visionkit-scanner.md

@@ -3,7 +3,7 @@
 Complete implementation patterns for DataScannerViewController and
 VNDocumentCameraViewController covering availability checking, configuration,
 SwiftUI integration, delegate handling, custom overlays, and camera permissions.
-All patterns target iOS 26+ with Swift 6.2 unless noted.
+All patterns target iOS 26+ with Swift 6.3 unless noted.
 
 ## Contents
 - Camera Permission Setup
@@ -508,10 +508,10 @@ struct ScannerWithOverlay: View {
                 // Top instruction bar
                 Text("Point camera at text or barcode")
                     .font(.subheadline)
-                    .padding(.horizontal, 16)
-                    .padding(.vertical, 8)
+                    .padding(.horizontal)
+                    .padding(.vertical)
                     .background(.ultraThinMaterial, in: Capsule())
-                    .padding(.top, 60)
+                    .padding(.top)
 
                 Spacer()
 
@@ -529,7 +529,7 @@ struct ScannerWithOverlay: View {
                         .padding()
                         .frame(maxWidth: .infinity)
                         .background(.ultraThinMaterial)
-                        .clipShape(RoundedRectangle(cornerRadius: 12))
+                        .clipShape(.rect(cornerRadius: 12))
                         .padding()
                 }
             }

package/pipeline/skills/shared/external/vue-composition/SKILL.md

@@ -1,4 +1,5 @@
 ---
+name: vue-composition
 description: "Vue 3 Composition API: ref, reactive, computed, watch, composables, Pinia state management, Vue Router 4, script setup"
 tags: [vue, composition-api, pinia, vue-router, frontend, javascript]
 version: "2025.1"
@@ -92,12 +93,12 @@ onMounted(() => {
 ```typescript
 import { ref, reactive, toRefs } from 'vue';
 
-// ref — for primitives and single values (unwraps in template)
+// ref  -  for primitives and single values (unwraps in template)
 const count = ref(0);
 count.value++; // need .value in script
-// <template>{{ count }}</template> — no .value needed
+// <template>{{ count }}</template>  -  no .value needed
 
-// reactive — for objects (deep reactive, no .value needed)
+// reactive  -  for objects (deep reactive, no .value needed)
 const state = reactive({
   name: '',
   email: '',
@@ -105,7 +106,7 @@ const state = reactive({
 });
 state.name = 'John'; // direct property access
 
-// toRefs — destructure reactive object without losing reactivity
+// toRefs  -  destructure reactive object without losing reactivity
 const { name, email } = toRefs(state);
 // name is Ref<string>, tracks state.name
 
@@ -121,7 +122,7 @@ const searchQuery = ref('');
 const selectedCategory = ref('all');
 const results = ref([]);
 
-// watch — explicit source, access old/new values
+// watch  -  explicit source, access old/new values
 watch(searchQuery, async (newQuery, oldQuery) => {
   if (newQuery.length >= 3) {
     results.value = await search(newQuery);
@@ -136,7 +137,7 @@ watch(
   }
 );
 
-// watchEffect — auto-tracks dependencies, runs immediately
+// watchEffect  -  auto-tracks dependencies, runs immediately
 watchEffect(async () => {
   // Automatically re-runs when searchQuery.value or selectedCategory.value changes
   if (searchQuery.value.length >= 3) {

package/pipeline/skills/shared/external/weatherkit/SKILL.md

@@ -7,7 +7,7 @@ description: "Fetch current, hourly, and daily weather forecasts and display req
 
 Fetch current conditions, hourly and daily forecasts, weather alerts, and
 historical statistics using `WeatherService`. Display required Apple Weather
-attribution. Targets Swift 6.2 / iOS 26+.
+attribution. Targets Swift 6.3 / iOS 26+.
 
 ## Contents
 
@@ -222,7 +222,7 @@ struct WeatherAttributionView: View {
     @Environment(\.colorScheme) private var colorScheme
 
     var body: some View {
-        VStack(spacing: 8) {
+        VStack {
             // Display the Apple Weather mark
             AsyncImage(url: markURL) { image in
                 image
@@ -396,7 +396,7 @@ actor WeatherCache {
 
 ## References
 
-- Extended patterns (SwiftUI dashboard, charts integration, historical statistics): `references/weatherkit-patterns.md`
+- Extended patterns (SwiftUI dashboard, charts integration, historical statistics): [references/weatherkit-patterns.md](references/weatherkit-patterns.md)
 - [WeatherKit framework](https://sosumi.ai/documentation/weatherkit)
 - [WeatherService](https://sosumi.ai/documentation/weatherkit/weatherservice)
 - [WeatherAttribution](https://sosumi.ai/documentation/weatherkit/weatherattribution)

package/pipeline/skills/shared/external/weatherkit/references/weatherkit-patterns.md

@@ -13,7 +13,7 @@ Overflow reference for the `weatherkit` skill. Contains advanced patterns that e
 
 ## WeatherKit SwiftUI Integration
 
-### Weather Manager with @Observable
+### Weather Manager with `@Observable`
 
 ```swift
 import WeatherKit
@@ -68,7 +68,7 @@ struct WeatherDashboardView: View {
     var body: some View {
         NavigationStack {
             ScrollView {
-                VStack(spacing: 20) {
+                VStack {
                     if manager.isLoading {
                         ProgressView("Loading weather...")
                     } else if let current = manager.current {
@@ -104,7 +104,7 @@ struct WeatherDashboardView: View {
     }
 
     private func currentConditionsCard(_ current: CurrentWeather) -> some View {
-        VStack(spacing: 12) {
+        VStack {
             Image(systemName: current.symbolName)
                 .font(.system(size: 60))
                 .symbolRenderingMode(.multicolor)
@@ -116,7 +116,7 @@ struct WeatherDashboardView: View {
                 .font(.title3)
                 .foregroundStyle(.secondary)
 
-            HStack(spacing: 24) {
+            HStack {
                 Label(
                     "Humidity \(current.humidity.formatted(.percent))",
                     systemImage: "humidity"
@@ -141,9 +141,9 @@ struct WeatherDashboardView: View {
                 .font(.headline)
 
             ScrollView(.horizontal, showsIndicators: false) {
-                HStack(spacing: 16) {
+                HStack {
                     ForEach(Array(forecast.prefix(12)), id: \.date) { hour in
-                        VStack(spacing: 8) {
+                        VStack {
                             Text(hour.date, format: .dateTime.hour())
                                 .font(.caption)
                             Image(systemName: hour.symbolName)
@@ -220,7 +220,7 @@ struct WeatherDashboardView: View {
                 }
                 .padding()
                 .background(.yellow.opacity(0.1))
-                .clipShape(RoundedRectangle(cornerRadius: 8))
+                .clipShape(.rect(cornerRadius: 8))
             }
         }
     }
@@ -235,7 +235,7 @@ struct WeatherAttributionView: View {
     @Environment(\.colorScheme) private var colorScheme
 
     var body: some View {
-        VStack(spacing: 4) {
+        VStack {
             AsyncImage(url: markURL) { image in
                 image
                     .resizable()
@@ -252,7 +252,7 @@ struct WeatherAttributionView: View {
                     .foregroundStyle(.secondary)
             }
         }
-        .padding(.vertical, 8)
+        .padding(.vertical)
     }
 
     private var markURL: URL {

package/pipeline/skills/shared/external/web-accessibility/SKILL.md

@@ -1,4 +1,5 @@
 ---
+name: web-accessibility
 description: "WCAG 2.2 AA web accessibility: ARIA roles/states, keyboard navigation, screen readers, color contrast, focus management, axe-core testing"
 tags: [accessibility, a11y, wcag, aria, screen-reader, frontend]
 version: "2025.1"