buildanything 1.7.1 → 2.0.0

package/skills/ios/ios-bootstrap/references/xcode-mcp-config.md

@@ -0,0 +1,29 @@
+# XcodeBuildMCP — MCP config snippet
+
+Add the following under the `mcpServers` object in `~/.claude.json` (user-wide) or `./.mcp.json` (project-scoped).
+
+```json
+{
+  "mcpServers": {
+    "xcodebuildmcp": {
+      "command": "npx",
+      "args": ["-y", "xcodebuildmcp@latest"]
+    }
+  }
+}
+```
+
+## What it gives you
+- Discover schemes, targets, and destinations from `.xcodeproj` / `.xcworkspace`
+- Build, clean, archive via `xcodebuild` with structured output
+- Boot, shutdown, and install apps on simulators
+- Toggle target capabilities (Push, HealthKit, App Groups, iCloud, Sign in with Apple)
+- Read and patch Info.plist / entitlements plists safely
+
+## Verification
+After adding and restarting Claude Code, confirm tools prefixed `mcp__xcodebuildmcp__` appear in the tool list.
+
+## Troubleshooting
+- **`npx` missing** — install Node 20+ (`brew install node`).
+- **Server never initializes** — check Claude Code logs; usually first-run `npx` download stalled behind a proxy.
+- **Multiple Xcode installs** — run `sudo xcode-select -s /Applications/Xcode.app` so the MCP picks up 26.3.

package/skills/ios/ios-debugger-agent/LICENSE

@@ -0,0 +1,21 @@
+MIT License
+
+Copyright (c) 2026 Thomas Ricouard
+
+Permission is hereby granted, free of charge, to any person obtaining a copy
+of this software and associated documentation files (the "Software"), to deal
+in the Software without restriction, including without limitation the rights
+to use, copy, modify, merge, publish, distribute, sublicense, and/or sell
+copies of the Software, and to permit persons to whom the Software is
+furnished to do so, subject to the following conditions:
+
+The above copyright notice and this permission notice shall be included in all
+copies or substantial portions of the Software.
+
+THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR
+IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY,
+FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE
+AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER
+LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM,
+OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE
+SOFTWARE.

package/skills/ios/ios-debugger-agent/SKILL.md

@@ -0,0 +1,58 @@
+---
+name: ios-debugger-agent
+description: Use XcodeBuildMCP to build, run, launch, and debug the current iOS project on a booted simulator. Trigger when asked to run an iOS app, interact with the simulator UI, inspect on-screen state, capture logs/console output, or diagnose runtime behavior using XcodeBuildMCP tools.
+---
+
+# iOS Debugger Agent
+
+> scope=inner dev-loop; Maestro owns E2E
+
+## Overview
+Use XcodeBuildMCP to build and run the current project scheme on a booted iOS simulator, interact with the UI, and capture logs. Prefer the MCP tools for simulator control, logs, and view inspection.
+
+## Core Workflow
+Follow this sequence unless the user asks for a narrower action.
+
+### 1) Discover the booted simulator
+- Call `mcp__XcodeBuildMCP__list_sims` and select the simulator with state `Booted`.
+- If none are booted, ask the user to boot one (do not boot automatically unless asked).
+
+### 2) Set session defaults
+- Call `mcp__XcodeBuildMCP__session-set-defaults` with:
+  - `projectPath` or `workspacePath` (whichever the repo uses)
+  - `scheme` for the current app
+  - `simulatorId` from the booted device
+  - Optional: `configuration: "Debug"`, `useLatestOS: true`
+
+### 3) Build + run (when requested)
+- Call `mcp__XcodeBuildMCP__build_run_sim`.
+- **If the build fails**, check the error output and retry (optionally with `preferXcodebuild: true`) or escalate to the user before attempting any UI interaction.
+- **After a successful build**, verify the app launched by calling `mcp__XcodeBuildMCP__describe_ui` or `mcp__XcodeBuildMCP__screenshot` before proceeding to UI interaction.
+- If the app is already built and only launch is requested, use `mcp__XcodeBuildMCP__launch_app_sim`.
+- If bundle id is unknown:
+  1) `mcp__XcodeBuildMCP__get_sim_app_path`
+  2) `mcp__XcodeBuildMCP__get_app_bundle_id`
+
+## UI Interaction & Debugging
+Use these when asked to inspect or interact with the running app.
+
+- **Describe UI**: `mcp__XcodeBuildMCP__describe_ui` before tapping or swiping.
+- **Tap**: `mcp__XcodeBuildMCP__tap` (prefer `id` or `label`; use coordinates only if needed).
+- **Type**: `mcp__XcodeBuildMCP__type_text` after focusing a field.
+- **Gestures**: `mcp__XcodeBuildMCP__gesture` for common scrolls and edge swipes.
+- **Screenshot**: `mcp__XcodeBuildMCP__screenshot` for visual confirmation.
+
+## Logs & Console Output
+- Start logs: `mcp__XcodeBuildMCP__start_sim_log_cap` with the app bundle id.
+- Stop logs: `mcp__XcodeBuildMCP__stop_sim_log_cap` and summarize important lines.
+- For console output, set `captureConsole: true` and relaunch if required.
+
+## Troubleshooting
+- If build fails, ask whether to retry with `preferXcodebuild: true`.
+- If the wrong app launches, confirm the scheme and bundle id.
+- If UI elements are not hittable, re-run `describe_ui` after layout changes.
+
+
+---
+
+Vendored from: https://github.com/Dimillian/Skills/tree/main/ios-debugger-agent

package/skills/ios/ios-debugger-agent/agents/openai.yaml

@@ -0,0 +1,4 @@
+interface:
+  display_name: "iOS Debugger Agent"
+  short_description: "Debug iOS apps on Simulator"
+  default_prompt: "Use $ios-debugger-agent to build, launch, and inspect the current iOS app on the booted simulator."

package/skills/ios/ios-entitlements-generator/SKILL.md

@@ -0,0 +1,47 @@
+---
+name: ios-entitlements-generator
+description: Generates a .entitlements plist from ios_features flags and syncs Xcode capability toggles via XcodeBuildMCP. Delegates the capability→entitlement table to protocols/ios-frameworks-map.md §4. Use during Phase 4 Foundation.
+version: 0.2.0
+status: ready
+---
+
+# iOS Entitlements Generator (Phase 4)
+
+## Purpose
+Turns the `ios_features` checklist in `.build-state.md` into a correct `.entitlements` plist and syncs the Xcode capability UI. Removes the foot-gun of hand-editing entitlement keys.
+
+## Authoritative mapping source
+**This skill does NOT maintain its own capability→entitlement table.** It DELEGATES to `protocols/ios-frameworks-map.md` **§4 Entitlement Mapping**. Always consult that table at generation time — it is the single source of truth and is kept in sync with iOS SDK releases.
+
+## When this fires
+- Phase 4 Foundation, after architecture decisions finalized
+- A new capability is added mid-project (Push, App Groups, CloudKit, …)
+- Pre-archive audit to confirm entitlements match used capabilities
+
+## Inputs
+- `ios_features` object from `docs/plans/.build-state.md` — boolean flags like `push`, `cloudKit`, `healthKit`, `appGroups`, `signInWithApple`, `associatedDomains`, `keychainSharing`, `weatherKit`, `musicKit`, `networkExtension`
+- `app_groups_ids` (string[], optional)
+- `associated_domains` (string[], optional — e.g. `applinks:app.example.com`)
+- `icloud_container_ids` (string[], optional)
+- `background_modes` (string[], optional — `fetch`, `remote-notification`, `processing`, `audio`, `location`, `bluetooth-central`, `voip`)
+
+## Outputs
+- `<ProjectName>.entitlements` plist at the target's Signing/Capabilities dir
+- `docs/plans/entitlements-summary.md` — diff of added/removed keys, per-capability rationale
+- XcodeBuildMCP capability toggles (Push, HealthKit, CloudKit, App Groups, Sign in with Apple) flipped on in the target UI
+
+## Workflow
+1. **Read state** — load `ios_features` from `docs/plans/.build-state.md`.
+2. **Resolve entitlements** — for each flag set `true`, look up the entitlement key(s) in `protocols/ios-frameworks-map.md §4`. Do not invent keys; if the table doesn't cover it, query `apple-docs-mcp` and surface as a TODO in the summary.
+3. **Merge plist immutably** — read existing `<ProjectName>.entitlements` if present, compute new dict as a merge (never clobber user-added keys), write a new file. Preserve key ordering for clean diffs.
+4. **Sync Xcode capability UI** — for capabilities that require target-level toggles (Push, HealthKit, CloudKit, App Groups, Sign in with Apple, Background Modes), call XcodeBuildMCP's capability-toggle tool so the Signing & Capabilities tab matches the plist.
+5. **Emit summary** — write `entitlements-summary.md` listing each capability, keys added, and values requiring user input (team ID, container IDs, domain list).
+
+## Validation
+- Every key in the output must trace back to a row in `ios-frameworks-map.md §4` or an explicit user-provided value.
+- `aps-environment` must be `development` in debug configs, `production` in release.
+- Associated domains must be prefixed (`applinks:`, `webcredentials:`, `activitycontinuation:`).
+- iCloud container IDs must start with `iCloud.` and match the CloudKit dashboard.
+
+---
+_Part of buildanything iOS mode. Delegates to `protocols/ios-frameworks-map.md §4`. See `protocols/ios-context.md` for persona._

package/skills/ios/ios-info-plist-hardening/SKILL.md

@@ -0,0 +1,130 @@
+---
+name: ios-info-plist-hardening
+description: Generates and audits Info.plist defaults (usage-description strings, URL schemes, background modes, scene manifest) AND produces PrivacyInfo.xcprivacy so the app clears App Review and launches cleanly. Use during Phase 4 Foundation on every iOS project.
+version: 0.2.0
+status: ready
+---
+
+# iOS Info.plist Hardening (Phase 4)
+
+## Purpose
+Ensures `Info.plist` carries every required usage-description string, correctly registered URL schemes, declared background modes, and a sane SwiftUI scene manifest. Also emits the iOS 17+ `PrivacyInfo.xcprivacy` manifest. Catches "rejected because NSCameraUsageDescription is missing" before it happens.
+
+## When this fires
+- Phase 4 Foundation (always, for iOS projects)
+- Whenever a new API that requires a usage-description is added
+- Pre-archive audit
+
+## Inputs
+- `ios_features` from `docs/plans/.build-state.md` (boolean flags: camera, microphone, location_when_in_use, location_always, photos, contacts, calendar, reminders, motion, health, bluetooth, localNetwork, tracking, faceID, music, homeKit, siri, nearbyInteraction, speech, appleMusic)
+- `url_schemes` (string[], optional)
+- `background_modes` (string[], optional)
+- `app_lifecycle` (enum: `swiftui_app` | `uikit_appdelegate`, default `swiftui_app`)
+- `tracking_required_reasons` (object, optional) — required-reason API categories in use
+- `collects_tracking_data` (bool, default false)
+
+## Outputs
+- Updated `Info.plist` with merged keys (via XcodeBuildMCP)
+- `PrivacyInfo.xcprivacy` at target root (iOS 17+)
+- Audit report `docs/plans/plist-audit.md`: missing keys, stale keys, weak description strings
+
+## Required usage-description keys
+
+| Info.plist key | Triggered by |
+|---|---|
+| `NSCameraUsageDescription` | Camera / AVFoundation / Vision / ARKit / VisionKit |
+| `NSMicrophoneUsageDescription` | Microphone / Speech / ShazamKit |
+| `NSPhotoLibraryUsageDescription` | PhotoKit read |
+| `NSPhotoLibraryAddUsageDescription` | Writing to photo library |
+| `NSLocationWhenInUseUsageDescription` | CoreLocation foreground |
+| `NSLocationAlwaysAndWhenInUseUsageDescription` | CoreLocation background |
+| `NSContactsUsageDescription` | Contacts |
+| `NSCalendarsUsageDescription` / `NSCalendarsFullAccessUsageDescription` | EventKit (iOS 17+ split) |
+| `NSRemindersUsageDescription` / `NSRemindersFullAccessUsageDescription` | EventKit reminders |
+| `NSMotionUsageDescription` | CoreMotion |
+| `NSHealthShareUsageDescription` | HealthKit read |
+| `NSHealthUpdateUsageDescription` | HealthKit write |
+| `NSSpeechRecognitionUsageDescription` | Speech |
+| `NSBluetoothAlwaysUsageDescription` | CoreBluetooth |
+| `NSLocalNetworkUsageDescription` | Bonjour / Multipeer / Network framework LAN |
+| `NSUserTrackingUsageDescription` | AppTrackingTransparency / IDFA |
+| `NSFaceIDUsageDescription` | LocalAuthentication biometrics |
+| `NSAppleMusicUsageDescription` | MediaPlayer / MusicKit |
+| `NSHomeKitUsageDescription` | HomeKit |
+| `NSSiriUsageDescription` | SiriKit / App Intents w/ Siri |
+| `NSNearbyInteractionUsageDescription` | NearbyInteraction (UWB) |
+
+Usage descriptions must be **specific and user-facing** ("To scan receipts with your camera" beats "Needs camera"). Reject strings under 20 characters or containing placeholder text.
+
+## URL scheme registration template
+```xml
+<key>CFBundleURLTypes</key>
+<array>
+  <dict>
+    <key>CFBundleURLName</key>
+    <string>com.acme.habitforge</string>
+    <key>CFBundleURLSchemes</key>
+    <array>
+      <string>habitforge</string>
+    </array>
+    <key>CFBundleTypeRole</key>
+    <string>Editor</string>
+  </dict>
+</array>
+```
+
+## UIBackgroundModes enumeration
+Valid values (set only what the app actually uses):
+- `fetch` — background app refresh
+- `remote-notification` — silent push wake
+- `audio` — background audio playback
+- `location` — continuous location updates
+- `bluetooth-central` — BLE central role
+- `bluetooth-peripheral` — BLE peripheral role
+- `voip` — VoIP calls
+- `external-accessory`
+- `processing` — BGProcessingTask (long-running)
+- `nearby-interaction`
+
+## Scene manifest (SwiftUI app lifecycle default)
+```xml
+<key>UIApplicationSceneManifest</key>
+<dict>
+  <key>UIApplicationSupportsMultipleScenes</key>
+  <true/>
+  <key>UISceneConfigurations</key>
+  <dict/>
+</dict>
+```
+
+## PrivacyInfo.xcprivacy (iOS 17+ — this skill owns creation at Phase 4)
+Generate with four top-level keys:
+
+- **`NSPrivacyTracking`** — bool; true only if `collects_tracking_data` is true.
+- **`NSPrivacyTrackingDomains`** — array of tracking domains contacted (only if tracking is true).
+- **`NSPrivacyCollectedDataTypes`** — array of dicts, one per data category collected, each with: `NSPrivacyCollectedDataType`, `NSPrivacyCollectedDataTypeLinked`, `NSPrivacyCollectedDataTypeTracking`, `NSPrivacyCollectedDataTypePurposes`.
+- **`NSPrivacyAccessedAPITypes`** — array of required-reason API declarations. Each entry has `NSPrivacyAccessedAPIType` + `NSPrivacyAccessedAPITypeReasons`. Common categories:
+  - `NSPrivacyAccessedAPICategoryFileTimestamp`
+  - `NSPrivacyAccessedAPICategorySystemBootTime`
+  - `NSPrivacyAccessedAPICategoryDiskSpace`
+  - `NSPrivacyAccessedAPICategoryActiveKeyboards`
+  - `NSPrivacyAccessedAPICategoryUserDefaults`
+
+Detect required-reason API usage by scanning code for patterns (e.g. `FileManager` attributes, `UserDefaults` access, `UIDevice` boot time). Emit a declaration for each detected category with the appropriate reason code.
+
+## Workflow
+1. **Read state** — load `ios_features` flags from `docs/plans/.build-state.md`.
+2. **Select required keys** — for each true flag, resolve to usage-description key(s) from the table above (cross-check `ios-frameworks-map.md §4` column "Info.plist keys").
+3. **Scan code for required-reason APIs** — grep for `FileManager`, `UserDefaults`, `systemUptime`, `.systemFreeSize`, keyboard APIs; build privacy-manifest entries.
+4. **Generate patches** — compute Info.plist additions and PrivacyInfo.xcprivacy content.
+5. **Write via XcodeBuildMCP** — merge Info.plist (never clobber user keys), create/overwrite `PrivacyInfo.xcprivacy` at target root.
+6. **Emit audit report** — `docs/plans/plist-audit.md` listing additions, weak descriptions, and any manual follow-ups (e.g. "add tracking domain list").
+
+## Validation
+- Every usage-description string is ≥ 20 chars and references the concrete app action.
+- No placeholder strings (`TODO`, `lorem`, `test`, `permission required`).
+- Background modes in plist match entitlements and actual runtime usage.
+- PrivacyInfo.xcprivacy includes a required-reason entry for every detected API category — missing entries block App Store submission.
+
+---
+_Part of buildanything iOS mode. See `protocols/ios-context.md` for persona. Cross-references `protocols/ios-frameworks-map.md §4`._

package/skills/ios/ios-maestro-flow-author/SKILL.md

@@ -0,0 +1,68 @@
+---
+name: ios-maestro-flow-author
+description: Generates Maestro .yaml E2E flow files from natural-language user journeys. Use during /verify iOS branch whenever a critical user journey needs automated coverage.
+version: 0.2.0
+status: ready
+---
+
+# iOS Maestro Flow Author (Phase 6, /verify twin)
+
+## Purpose
+Converts a plain-English user journey ("sign up, create first habit, mark complete") into a runnable Maestro flow YAML, ready to execute against a booted simulator via `maestro test`.
+
+## When this fires
+- `/verify` iOS branch
+- A new critical user journey needs E2E coverage
+- Regression: existing flow drifted from current UI
+
+## Inputs
+- `journey_nl` (string) — natural-language user journey
+- `app_id` (string) — bundle identifier under test (e.g. `com.acme.HabitForge`)
+- `test_name` (string, optional) — defaults to slugified journey
+
+## Outputs
+- `maestro/<test_name>.yaml`
+- Dry-run summary (commands emitted, accessibility-id assumptions, skipped steps)
+
+## Workflow
+1. Parse `journey_nl` into ordered discrete user actions (one sentence = one action group).
+2. Match each action to a Maestro command pattern from the cheat-sheet below; prefer accessibility IDs over visible text when the app exposes them.
+3. Emit YAML with `appId: {app_id}` header and one command per step.
+4. Write to `maestro/<test_name>.yaml`.
+5. Validate via `maestro test maestro/<test_name>.yaml` on a booted simulator (Maestro has no true `--dry-run`; shortest validation is to run it once against the sim).
+
+## Maestro cheat-sheet (10 core commands)
+
+```yaml
+- launchApp                                   # launches the appId declared in the header
+- tapOn: "Sign Up"                            # tap element by visible text
+- tapOn:
+    id: "emailField"                          # tap by accessibility identifier (preferred)
+- assertVisible: "Welcome back"               # assert text/element visible, fails flow if not
+- inputText: "alice@example.com"              # types into currently focused field
+- scroll                                      # scroll down on current screen
+- swipe:
+    direction: LEFT                           # swipe: LEFT | RIGHT | UP | DOWN
+- hideKeyboard                                # dismiss soft keyboard
+- back                                        # system back / pop navigation
+- pressKey: Enter                             # hardware key: Enter, Backspace, Home, Lock
+```
+
+See `references/` for five copy-and-adapt templates covering the 90% cases.
+
+## Authoring rules
+- Always start with `- launchApp`.
+- Prefer `id:` selectors (stable) over raw text (fragile to copy changes).
+- After every `inputText`, insert `hideKeyboard` before the next `tapOn` to avoid the keyboard intercepting taps.
+- End every flow with at least one `assertVisible` that confirms the user reached the destination screen.
+- Keep flows single-purpose — one user journey per file. Compose with `runFlow:` in a parent flow if needed.
+
+## Reference templates
+- `references/onboarding-flow.yaml` — launch → splash → signup → main screen
+- `references/tap-and-assert.yaml` — minimal tap + assertVisible pattern
+- `references/input-and-scroll.yaml` — form input + scroll + tap
+- `references/modal-and-dismiss.yaml` — open sheet, interact, dismiss
+- `references/tab-navigation.yaml` — switch tabs, verify each screen
+
+---
+_Part of buildanything iOS mode. See `protocols/ios-context.md` for Senior iOS Engineer persona._

package/skills/ios/ios-maestro-flow-author/references/input-and-scroll.yaml

@@ -0,0 +1,17 @@
+# Form fill + scroll + submit
+appId: com.acme.HabitForge
+---
+- launchApp
+- tapOn: "Add Habit"
+- assertVisible: "New Habit"
+- tapOn:
+    id: "habitNameField"
+- inputText: "Drink water"
+- hideKeyboard
+- tapOn:
+    id: "notesField"
+- inputText: "Eight glasses per day, spread across mornings and afternoons"
+- hideKeyboard
+- scroll
+- tapOn: "Save"
+- assertVisible: "Drink water"

package/skills/ios/ios-maestro-flow-author/references/modal-and-dismiss.yaml

@@ -0,0 +1,14 @@
+# Open modal sheet, interact, dismiss
+appId: com.acme.HabitForge
+---
+- launchApp
+- tapOn: "Settings"
+- assertVisible: "Preferences"
+- tapOn: "Appearance"
+- assertVisible: "Theme"
+- tapOn: "Dark"
+- swipe:
+    direction: DOWN
+- assertVisible: "Preferences"
+- back
+- assertVisible: "Your Habits"

package/skills/ios/ios-maestro-flow-author/references/onboarding-flow.yaml

@@ -0,0 +1,16 @@
+# Onboarding: launch -> splash -> sign up -> main screen
+appId: com.acme.HabitForge
+---
+- launchApp
+- assertVisible: "Welcome"
+- tapOn: "Sign Up"
+- assertVisible: "Create your account"
+- tapOn:
+    id: "emailField"
+- inputText: "alice@example.com"
+- tapOn:
+    id: "passwordField"
+- inputText: "hunter2hunter2"
+- hideKeyboard
+- tapOn: "Continue"
+- assertVisible: "Your Habits"

package/skills/ios/ios-maestro-flow-author/references/tab-navigation.yaml

@@ -0,0 +1,13 @@
+# Tab bar navigation — verify each tab loads its root screen
+appId: com.acme.HabitForge
+---
+- launchApp
+- assertVisible: "Your Habits"
+- tapOn: "Stats"
+- assertVisible: "Weekly Progress"
+- tapOn: "Journal"
+- assertVisible: "Entries"
+- tapOn: "Settings"
+- assertVisible: "Preferences"
+- tapOn: "Habits"
+- assertVisible: "Your Habits"

package/skills/ios/ios-maestro-flow-author/references/tap-and-assert.yaml

@@ -0,0 +1,9 @@
+# Minimal tap + assert pattern
+appId: com.acme.HabitForge
+---
+- launchApp
+- assertVisible: "Your Habits"
+- tapOn: "Add Habit"
+- assertVisible: "New Habit"
+- tapOn: "Cancel"
+- assertVisible: "Your Habits"

package/skills/ios/swift-accessibility/LICENSE

@@ -0,0 +1,21 @@
+MIT License
+
+Copyright (c) 2026 Pasquale Vittoriosi
+
+Permission is hereby granted, free of charge, to any person obtaining a copy
+of this software and associated documentation files (the "Software"), to deal
+in the Software without restriction, including without limitation the rights
+to use, copy, modify, merge, publish, distribute, sublicense, and/or sell
+copies of the Software, and to permit persons to whom the Software is
+furnished to do so, subject to the following conditions:
+
+The above copyright notice and this permission notice shall be included in all
+copies or substantial portions of the Software.
+
+THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR
+IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY,
+FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE
+AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER
+LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM,
+OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE
+SOFTWARE.