tribunal-kit 9.2.4 → 9.2.5

package/.agents/skills/swiftui-expert/SKILL.md

@@ -1,164 +1,164 @@
----
-name: swiftui-expert
-description: "Use when SwiftUI development mastery. View architecture, state management (@State, @Binding, @Environment, @Observable), performance optimization (identifiable loops, implicit vs explicit animations), architectural patterns (MVVM vs TCA), and iOS-native UX paradigms. Use when writing native Apple platforms code."
-version: 5.0.0
-last-updated: 2026-09-13
-skills:
-  - mobile-design
-  - building-native-ui
-  - apple-design
-tools: Read, Grep, Glob, Bash, Edit, Write
-scripts-binding:
-  - .agent/scripts/lint_runner.js
-  - .agent/scripts/verify_all.js
----
-
-# SwiftUI Expert — Native Apple Platforms Mastery
-
----
-
-## 🛠️ Technical Architecture & Reference Recipes
-
----
-
-## Hallucination Traps (Read First)
-
-- ❌ Using `@State` for shared data between views -> ✅ `@State` is local to a view; use `@Binding`, `@Environment`, or `@Observable` for sharing
-- ❌ Putting heavy computation in the `body` property -> ✅ `body` is called on EVERY re-render; move computation to `.task {}` or `onChange`
-- ❌ `List { ForEach(items) { ... } }` without `id:` parameter -> ✅ Always provide `id:` for `Identifiable` conformance or use `\.self`
-- ❌ Using `NavigationView` -> ✅ Deprecated in iOS 16+; use `NavigationStack` or `NavigationSplitView`
-
----
-
----
-
-## 1. Modern State Management (iOS 17+ / Swift 5.9+)
-
-Apple deprecated `@StateObject` and `@ObservedObject` in favor of the new `@Observable` macro.
-
-```swift
-// ❌ OLD WAY (Pre-iOS 17)
-class UserProfile: ObservableObject {
-    @Published var name: String = "Guest"
-}
-struct ProfileView: View {
-    @StateObject var profile = UserProfile()
-    // ...
-}
-
-// ✅ NEW WAY (iOS 17+ / @Observable)
-import Observation
-
-@Observable
-class UserProfile {
-    var name: String = "Guest"
-    var age: Int = 0
-    // No @Published needed! Only properties that are actually read
-    // inside the body will trigger view updates.
-}
-
-struct ProfileView: View {
-    // Treat the reference type exactly like a value type!
-    @State private var profile = UserProfile()
-
-    var body: some View {
-        VStack {
-            TextField("Name", text: $profile.name)
-            Text("Hello, \(profile.name)")
-        }
-    }
-}
-```
-
-### Property Data Flow Cheat Sheet
-
-- `@State`: The view OWNS value (or reference if `@Observable`).
-- `@Binding`: The view mutates a value OWNED by a parent.
-- `@Environment`: The view reads value injected high up in the view hierarchy.
-- `@Bindable`: Creates bindings from an `@Observable` model passed via parameters/environment.
-
----
-
-## 2. View Architecture & Modifiers
-
-SwiftUI Views should be impossibly small. Extract frequently.
-
-```swift
-// ❌ BAD: Massive body with 10 layers of nesting
-struct MassiveView: View {
-    var body: some View { ... }
-}
-
-// ✅ GOOD: Extract via properties, functions, or new View structs
-struct CleanView: View {
-    var body: some View {
-        VStack {
-            headerSection
-            CustomScrollingList(items: data)
-            footerSection
-        }
-    }
-
-    private var headerSection: some View {
-        Text("Header").font(.headline)
-    }
-}
-```
-
-### Modifier Ordering Matters
-
-Modifiers wrap views sequentially. The order fundamentally changes the rendering.
-
-```swift
-// Padding BEFORE Background
-Text("Hello")
-    .padding()
-    .background(Color.blue)
-// Result: A large blue box with text inside.
-
-// Padding AFTER Background
-Text("Hello")
-    .background(Color.blue)
-    .padding()
-// Result: A tight blue box around text, surrounded by invisible spacing.
-```
-
----
-
-## 3. Performance & Rendering
-
-```swift
-// ❌ BAD: Using indices in ForEach
-// If the array mutates (items injected/deleted), SwiftUI loses
-// track of identity and re-renders EVERYTHING aggressively.
-ForEach(0..<items.count, id: \.self) { index in
-    ItemRow(item: items[index])
-}
-
-// ✅ GOOD: Identifiable protocol
-struct Item: Identifiable {
-    let id = UUID()
-    let title: String
-}
-
-ForEach(items) { item in
-    ItemRow(item: item)
-}
-```
-
-### Avoiding Massive Layout Recalculations
-
-Use `LazyVStack` and `LazyHStack` inside ScrollViews when presenting large lists, but NOT everywhere. Normal `VStack` is faster for < 20 items because it pre-calculates boundaries instantly.
-
----
-
-## 4. MVVM vs Context-Driven Architecture
-
-While MVVM is historically popular, SwiftUI natively represents View-as-a-function-of-State.
-
-```swift
-// ✅ Context-Driven / Feature-Driven
-// The Model handles data fetching/logic.
-// The View creates its own local @State and passes @Bindings down.
-// Only use full ViewModels for complex orchestration crossing multiple views.
-```
+---
+name: swiftui-expert
+description: "Use when SwiftUI development mastery. View architecture, state management (@State, @Binding, @Environment, @Observable), performance optimization (identifiable loops, implicit vs explicit animations), architectural patterns (MVVM vs TCA), and iOS-native UX paradigms. Use when writing native Apple platforms code."
+version: 5.0.0
+last-updated: 2026-09-13
+skills:
+  - mobile-design
+  - building-native-ui
+  - apple-design
+tools: Read, Grep, Glob, Bash, Edit, Write
+scripts-binding:
+  - .agent/scripts/lint_runner.js
+  - .agent/scripts/verify_all.js
+---
+
+# SwiftUI Expert — Native Apple Platforms Mastery
+
+---
+
+## 🛠️ Technical Architecture & Reference Recipes
+
+---
+
+## Hallucination Traps (Read First)
+
+- ❌ Using `@State` for shared data between views -> ✅ `@State` is local to a view; use `@Binding`, `@Environment`, or `@Observable` for sharing
+- ❌ Putting heavy computation in the `body` property -> ✅ `body` is called on EVERY re-render; move computation to `.task {}` or `onChange`
+- ❌ `List { ForEach(items) { ... } }` without `id:` parameter -> ✅ Always provide `id:` for `Identifiable` conformance or use `\.self`
+- ❌ Using `NavigationView` -> ✅ Deprecated in iOS 16+; use `NavigationStack` or `NavigationSplitView`
+
+---
+
+---
+
+## 1. Modern State Management (iOS 17+ / Swift 5.9+)
+
+Apple deprecated `@StateObject` and `@ObservedObject` in favor of the new `@Observable` macro.
+
+```swift
+// ❌ OLD WAY (Pre-iOS 17)
+class UserProfile: ObservableObject {
+    @Published var name: String = "Guest"
+}
+struct ProfileView: View {
+    @StateObject var profile = UserProfile()
+    // ...
+}
+
+// ✅ NEW WAY (iOS 17+ / @Observable)
+import Observation
+
+@Observable
+class UserProfile {
+    var name: String = "Guest"
+    var age: Int = 0
+    // No @Published needed! Only properties that are actually read
+    // inside the body will trigger view updates.
+}
+
+struct ProfileView: View {
+    // Treat the reference type exactly like a value type!
+    @State private var profile = UserProfile()
+
+    var body: some View {
+        VStack {
+            TextField("Name", text: $profile.name)
+            Text("Hello, \(profile.name)")
+        }
+    }
+}
+```
+
+### Property Data Flow Cheat Sheet
+
+- `@State`: The view OWNS value (or reference if `@Observable`).
+- `@Binding`: The view mutates a value OWNED by a parent.
+- `@Environment`: The view reads value injected high up in the view hierarchy.
+- `@Bindable`: Creates bindings from an `@Observable` model passed via parameters/environment.
+
+---
+
+## 2. View Architecture & Modifiers
+
+SwiftUI Views should be impossibly small. Extract frequently.
+
+```swift
+// ❌ BAD: Massive body with 10 layers of nesting
+struct MassiveView: View {
+    var body: some View { ... }
+}
+
+// ✅ GOOD: Extract via properties, functions, or new View structs
+struct CleanView: View {
+    var body: some View {
+        VStack {
+            headerSection
+            CustomScrollingList(items: data)
+            footerSection
+        }
+    }
+
+    private var headerSection: some View {
+        Text("Header").font(.headline)
+    }
+}
+```
+
+### Modifier Ordering Matters
+
+Modifiers wrap views sequentially. The order fundamentally changes the rendering.
+
+```swift
+// Padding BEFORE Background
+Text("Hello")
+    .padding()
+    .background(Color.blue)
+// Result: A large blue box with text inside.
+
+// Padding AFTER Background
+Text("Hello")
+    .background(Color.blue)
+    .padding()
+// Result: A tight blue box around text, surrounded by invisible spacing.
+```
+
+---
+
+## 3. Performance & Rendering
+
+```swift
+// ❌ BAD: Using indices in ForEach
+// If the array mutates (items injected/deleted), SwiftUI loses
+// track of identity and re-renders EVERYTHING aggressively.
+ForEach(0..<items.count, id: \.self) { index in
+    ItemRow(item: items[index])
+}
+
+// ✅ GOOD: Identifiable protocol
+struct Item: Identifiable {
+    let id = UUID()
+    let title: String
+}
+
+ForEach(items) { item in
+    ItemRow(item: item)
+}
+```
+
+### Avoiding Massive Layout Recalculations
+
+Use `LazyVStack` and `LazyHStack` inside ScrollViews when presenting large lists, but NOT everywhere. Normal `VStack` is faster for < 20 items because it pre-calculates boundaries instantly.
+
+---
+
+## 4. MVVM vs Context-Driven Architecture
+
+While MVVM is historically popular, SwiftUI natively represents View-as-a-function-of-State.
+
+```swift
+// ✅ Context-Driven / Feature-Driven
+// The Model handles data fetching/logic.
+// The View creates its own local @State and passes @Bindings down.
+// Only use full ViewModels for complex orchestration crossing multiple views.
+```

package/.agents/skills/swiss-design/SKILL.md

@@ -1,44 +1,44 @@
----
-name: swiss-design
-description: "Use when International Typographic Style (Swiss Design) principles for web interfaces. Strict grid discipline, asymmetric layouts, bold typographic contrast, flush-left un-justified text, and mathematical negative space."
-version: 5.0.0
-last-updated: 2026-09-13
-skills:
-  - typeset
-  - baseline-ui
-  - better-ui
-tools: Read, Grep, Glob, Bash, Edit, Write
-scripts-binding:
-  - .agent/scripts/lint_runner.js
-  - .agent/scripts/verify_all.js
----
-
-# Swiss Design — International Typographic Style for Web
-
----
-
-## 🛠️ Technical Architecture & Reference Recipes
-
----
-
----
-
-## 4 Swiss Design Pillars
-
-### 1. Strict Grid Alignment
-
-- Every layout element MUST align strictly to a visible or invisible 12-column grid.
-- Border dividers use thin, sharp 1px solid lines matching `--foreground` opacity (e.g. `border-color: rgba(0,0,0,0.15)`).
-
-### 2. High-Contrast Sans-Serif Typography
-
-- Use clean grotesque sans-serif fonts (Helvetica, Inter, Geist, Neue Haas Grotesk).
-- Pair large bold display titles (`3rem+`, `font-weight: 700`, `letter-spacing: -0.03em`) with clean flush-left, rag-right body copy (`text-align: left`).
-
-### 3. Asymmetric Structural Balance
-
-- Reject centered, symmetrical layouts. Align headings and content to strong left vertical axes, using generous negative space to anchor visual weight.
-
-### 4. Mathematical Numbering & Labels
-
-- Use small uppercase metadata badges (`SECTION 01 // OVERVIEW`) with tracking (`letter-spacing: 0.08em`) and monospace or tabular numbers (`font-variant-numeric: tabular-nums`).
+---
+name: swiss-design
+description: "Use when International Typographic Style (Swiss Design) principles for web interfaces. Strict grid discipline, asymmetric layouts, bold typographic contrast, flush-left un-justified text, and mathematical negative space."
+version: 5.0.0
+last-updated: 2026-09-13
+skills:
+  - typeset
+  - baseline-ui
+  - better-ui
+tools: Read, Grep, Glob, Bash, Edit, Write
+scripts-binding:
+  - .agent/scripts/lint_runner.js
+  - .agent/scripts/verify_all.js
+---
+
+# Swiss Design — International Typographic Style for Web
+
+---
+
+## 🛠️ Technical Architecture & Reference Recipes
+
+---
+
+---
+
+## 4 Swiss Design Pillars
+
+### 1. Strict Grid Alignment
+
+- Every layout element MUST align strictly to a visible or invisible 12-column grid.
+- Border dividers use thin, sharp 1px solid lines matching `--foreground` opacity (e.g. `border-color: rgba(0,0,0,0.15)`).
+
+### 2. High-Contrast Sans-Serif Typography
+
+- Use clean grotesque sans-serif fonts (Helvetica, Inter, Geist, Neue Haas Grotesk).
+- Pair large bold display titles (`3rem+`, `font-weight: 700`, `letter-spacing: -0.03em`) with clean flush-left, rag-right body copy (`text-align: left`).
+
+### 3. Asymmetric Structural Balance
+
+- Reject centered, symmetrical layouts. Align headings and content to strong left vertical axes, using generous negative space to anchor visual weight.
+
+### 4. Mathematical Numbering & Labels
+
+- Use small uppercase metadata badges (`SECTION 01 // OVERVIEW`) with tracking (`letter-spacing: 0.08em`) and monospace or tabular numbers (`font-variant-numeric: tabular-nums`).