docs: remove TablePlus competitive tracking content

.claude/skills/fix-issue/SKILL.md

@@ -7,7 +7,7 @@ description: >-
   scope, no quick patches. It runs a parallel investigation team (codebase tracing + Apple
   platform research + competitor/UX research), synthesizes a refactor-aware implementation
   blueprint, gets the user's approval, then implements to TablePro's standards. Trigger on
-  things like "fix issue #1234", "fix this bug", "this should behave like TablePlus", "do this
+  things like "fix issue #1234", "fix this bug", "this should behave like a native app", "do this
   properly / natively", or any non-trivial defect or behaviour gap in the app. Prefer this over
   an ad-hoc fix when the change touches UI behaviour, architecture, or anything the user expects
   to match Apple conventions.
@@ -59,7 +59,7 @@ Then spawn the three roles in a single turn so they run concurrently. Full chart
 | --- | --- | --- |
 | Codebase Analyzer | `feature-dev:code-explorer` | How does the relevant code actually work today? Which files, types, and call paths are involved? Where is the real cause? |
 | Apple Platform Researcher | `general-purpose` | What does Apple's documentation (HIG, AppKit, SwiftUI) say the correct behaviour and the right API are? |
-| Competitor / UX Researcher | `general-purpose` | How do TablePlus, DataGrip, Postico, and similar native clients handle this? What's the expected UX? |
+| Competitor / UX Researcher | `general-purpose` | How do DataGrip, Postico, Sequel Ace, and similar native clients handle this? What's the expected UX? |
 
 Give each investigator the Phase 0 problem statement and a sharp question. Tell them to report findings as a structured message back to you, citing concrete evidence (`file:line` for code, doc URLs or API names for platform research). `references/research-sources.md` lists the documentation map and the tools each researcher should reach for (`mcp__xcode__DocumentationSearch`, `WebSearch`, `WebFetch`).
 

.claude/skills/fix-issue/references/research-sources.md

@@ -24,7 +24,6 @@ Prefer the Xcode docs tool for API questions: it's authoritative and version-mat
 
 Native macOS database clients worth checking for expected behaviour:
 
-- **TablePlus** — the closest comparison; TablePro positions against it. `https://docs.tableplus.com`.
 - **DataGrip** — JetBrains, feature-rich; good for data-grid and SQL-editor behaviour.
 - **Postico** — native macOS Postgres client, strong HIG conformance; good model for "what feels native on macOS".
 - **Sequel Ace** — open-source MySQL client; behaviour is inspectable.

.claude/skills/fix-issue/references/team-roles.md

@@ -72,13 +72,13 @@ structured message with citations.
 
 ```
 You are the Competitor / UX Researcher on a TablePro fix investigation. TablePro is a native
-macOS database client, a fast alternative to TablePlus.
+macOS database client.
 
 Problem statement:
 <PROBLEM STATEMENT>
 
 Research how mature native DB clients handle this interaction. I need:
-1. How TablePlus, DataGrip, Postico, and Sequel Ace handle this specific behaviour or UI, as
+1. How DataGrip, Postico, and Sequel Ace handle this specific behaviour or UI, as
    concretely as you can (documented behaviour, help docs, release notes, reviews, screenshots).
 2. The interaction pattern users expect: what the control looks like, what the keyboard/mouse
    affordances are, edge cases these tools handle.