@event4u/agent-config 1.26.0 → 1.28.0

package/.agent-src/skills/deep-reading-analyst/SKILL.md

@@ -0,0 +1,192 @@
+---
+name: deep-reading-analyst
+description: "Deep analysis of articles/long-form via thinking frameworks (SCQA, mental models, inversion) — 'analyze article', 'deep dive', 'extract insights', URL/text wanting depth not summary."
+status: active
+source: package
+external_source: "https://github.com/ginobefun/deep-reading-analyst-skill/tree/26cd7dc9920e025d39751e396e707399022e49ef/src/deep-reading-analyst"
+refresh_trigger: "Upstream `ginobefun/deep-reading-analyst-skill` major rewrite (new framework added, dispatch table reshaped, or SHA pin invalidated by reference rename)."
+sunset_criterion: "Replace with a 50-line pointer skill if (a) all referenced modules are adopted as project-local guidelines (`docs/guidelines/agent-infra/{framework}.md`) AND (b) the dispatch logic moves into a project-native router."
+---
+
+> **Pinned upstream:** `ginobefun/deep-reading-analyst-skill` @ SHA `26cd7dc9` (MIT). Re-verify per upstream major rewrite. Reference modules below link to the same SHA.
+
+# deep-reading-analyst
+
+Wing-1 deep-thinking skill for articles, papers, opinion pieces, case studies, and long-form decision documents. Routes the user's content through 8 thinking frameworks at four depth levels (Quick / Standard / Deep / Research) and returns insight tied to the user's **goal**, not framework completion.
+
+## When to use
+
+- User pastes an article URL, paper, or long text and wants depth ("analyze", "deep dive", "extract insights", "help me understand").
+- User asks for a specific framework ("apply SCQA to this", "use inversion thinking", "give me the mental models lens").
+- User is making a decision and wants pre-mortem / multi-lens analysis on a written proposal.
+- User is studying or note-taking on dense material (research papers, strategy memos, books).
+
+Do NOT use when:
+- User wants a 3-bullet TL;DR — use `agent-docs-writing` or write a direct summary.
+- Content is code or a diff — route to `judge-bug-hunter`, `judge-code-quality`, or `adversarial-review`.
+- User wants risk analysis on a code change — route to `adversarial-review` (diff-bound) or `threat-modeling`.
+- User wants debugging or incident analysis — route to `bug-analyzer` or `systematic-debugging`.
+
+## Framework Arsenal
+
+| Depth | Time | Frameworks | Reference module |
+|---|---|---|---|
+| **L1 — Quick** | ~15 min | SCQA, 5W2H | [`scqa-framework`](../../../docs/guidelines/agent-infra/scqa-framework.md), `5w2h_analysis.md` (upstream) |
+| **L2 — Standard** | ~30 min | L1 + Critical Thinking, Inversion | + [`inversion-thinking`](../../../docs/guidelines/agent-infra/inversion-thinking.md), `critical_thinking.md` (upstream) |
+| **L3 — Deep** | ~60 min | L2 + Mental Models, First Principles, Systems Thinking, Six Hats | + [`mental-models`](../../../docs/guidelines/agent-infra/mental-models.md), `first_principles.md`, `systems_thinking.md`, `six_hats.md` (upstream) |
+| **L4 — Research** | 120 min+ | L3 + Cross-source comparison via web search | + `comparison_matrix.md` (upstream) |
+
+Modules tagged `(upstream)` link to SHA-pinned files at the URL in `external_source` above; project-local modules are adopted as guidelines.
+
+## Procedure: deep-reading-analyst
+
+### Step 0: Inspect
+
+1. **Detect content type** — article, paper, opinion piece, case study, how-to, strategy memo. Drives auto-suggested frameworks (Step 1).
+2. **Detect goal signal** — problem-solving, learning, writing reference, decision-making, curiosity. Drives Step 4 output shape.
+3. **Skip if mismatched** — see "Do NOT use when" above; route to the named skill.
+
+### Step 1: Initialize Analysis
+
+Ask the user three things in **one** message (not three turns), per `ask-when-uncertain` Iron Law (one question per turn — these three are bundled into a single numbered-options block):
+
+1. **Goal** — problem-solving · learning · writing · decision-making · curiosity.
+2. **Depth** — L1 Quick (15 min) · L2 Standard (30 min) · L3 Deep (60 min) · L4 Research (120 min+).
+3. **Framework override** — defaults are auto-suggested by content type (table below); user may name specific frameworks.
+
+If the user does not answer, default to L2 Standard with auto-selected frameworks.
+
+**Auto-suggest matrix:**
+
+| Content type | Default frameworks |
+|---|---|
+| Strategy / business article | SCQA + Mental Models + Inversion |
+| Research paper | 5W2H + Critical Thinking + Systems Thinking |
+| How-to guide | SCQA + 5W2H + First Principles |
+| Opinion piece | Critical Thinking + Inversion + Six Hats |
+| Case study | SCQA + Mental Models + Systems Thinking |
+
+### Step 2: Structural Understanding (always run)
+
+Regardless of depth, open with two short blocks:
+
+**2A — Basic structure.**
+
+```markdown
+📄 Type: [article/paper/report]
+🎯 Core thesis: [one sentence]
+Structure:
+├─ Argument 1 → [key support]
+├─ Argument 2 → [key support]
+└─ Argument 3 → [key support]
+Key concepts: [3–5 terms with one-line definitions]
+```
+
+**2B — SCQA breakdown.** Apply the four-element decomposition from [`scqa-framework`](../../../docs/guidelines/agent-infra/scqa-framework.md):
+
+```markdown
+**S (Situation)**: [context the article establishes]
+**C (Complication)**: [problem identified]
+**Q (Question)**: [core question]
+**A (Answer)**: [main solution / conclusion]
+Structure quality — clarity / logic / completeness: [★★★☆☆]
+```
+
+**2C — 5W2H gap check** (L1+). Quick scan: which of *What, Why, Who, When, Where, How, How much* are well-covered, partial, or missing? Flag the 1–2 most critical gaps.
+
+### Step 3: Apply Frameworks (depth-gated)
+
+Load only the frameworks the user's depth bought. Each framework follows the same pattern: **load reference module → apply lens → produce one fixed-shape block**.
+
+**L2 additions:**
+
+- **Critical Thinking** (`critical_thinking.md`, upstream) — argument strength score (X/10), strengths, weaknesses, logical fallacies detected.
+- **Inversion** ([`inversion-thinking`](../../../docs/guidelines/agent-infra/inversion-thinking.md)) — pre-mortem on the article's recommendation: "how would this fail?", missing risk factors, mitigations.
+
+**L3 additions:**
+
+- **Mental Models** ([`mental-models`](../../../docs/guidelines/agent-infra/mental-models.md)) — pick 3–5 models from different disciplines (physics, biology, psychology, economics, math), apply each lens, surface cross-model patterns.
+- **First Principles** (`first_principles.md`, upstream) — strip to fundamental truths, validate each core assumption, rebuild from base.
+- **Systems Thinking** (`systems_thinking.md`, upstream) — map relationships, feedback loops, leverage points.
+- **Six Hats** (`six_hats.md`, upstream) — White (facts), Red (feelings), Black (cautions), Yellow (benefits), Green (creativity), Blue (process).
+
+**L4 addition:**
+
+- **Cross-source comparison** (`comparison_matrix.md`, upstream) — web-search 2–3 related sources, compare SCQA across sources, identify consensus vs divergence, synthesize integrated perspective.
+
+### Step 4: Synthesize by Goal
+
+Output shape is **driven by Step 0 goal**, not by frameworks applied. Pick exactly one of the four blocks below.
+
+**For problem-solving:** Applicable solutions (2–3 from content) → Application plan with timed action steps → Success metrics → Risk mitigations from Inversion.
+
+**For learning:** Core concepts (definition + example) → Mental models gained → Connections to prior knowledge → First Principles fundamental question → 3 verification questions (understanding / application / evaluation).
+
+**For writing reference:** Key arguments + evidence (with paragraph citations) → Quotable insights with context → Critical analysis (strengths for citing, limitations for balanced discussion) → Alternative perspectives from Mental Models → Gaps and counterfactuals.
+
+**For decision-making:** Options presented → Multi-model evaluation (economic + risk + systems lens) → Six Hats decision analysis → Scenario analysis (best / worst / most likely) → Synthesized recommendation.
+
+### Step 5: Knowledge Activation (always end here)
+
+Regardless of goal, close with three fixed blocks:
+
+```markdown
+## 🎯 Top 3 takeaways
+1. **[Insight]** — Why it matters: [...] · One action: [specific, time-bound]
+2. **[Insight]** — Why it matters: [...] · One action: [specific, time-bound]
+3. **[Insight]** — Why it matters: [...] · One action: [specific, time-bound]
+
+## 💡 Quick win — one tiny, specific action for the next 24 hours.
+
+## 🧭 Frameworks used
+✅ SCQA  ✅ 5W2H  ✅ Critical  ✅ Inversion
+□ Mental Models  □ First Principles  □ Systems  □ Six Hats
+```
+
+### Step 6: Validate
+
+1. Every claim is faithful to the source — no misrepresentation, facts distinguished from opinions.
+2. Frameworks applied **purposefully**, not force-fit — drop a framework that adds no insight rather than padding the output.
+3. Output ends with concrete, actionable steps — no analysis-without-application.
+4. Specific citations (paragraph numbers, quotes) where the source supports them.
+
+## Output format
+
+1. **Structural block (Step 2)** — type / thesis / structure tree / key concepts / SCQA / 5W2H gaps.
+2. **Framework blocks (Step 3)** — one fixed-shape block per framework the depth bought.
+3. **Goal-shaped synthesis (Step 4)** — problem-solving / learning / writing / decision-making.
+4. **Knowledge activation (Step 5)** — top 3 takeaways · quick win · frameworks-used checkboxes.
+
+## Gotcha
+
+- The model tends to **apply every framework** even at L1 — respect the depth budget; skip frameworks the user did not buy.
+- The model tends to **summarize** instead of analyze when the user pastes long text — go deep on 1–3 points, not shallow on all of them.
+- Inversion drifts into adversarial code review — this skill targets **decisions and arguments**, not diffs. Route diff stress-tests to `adversarial-review` / `judge-bug-hunter`.
+- Mental Models drifts into name-dropping — pick 3–5, apply each lens *concretely* to the article's claims, drop models that yield no new insight.
+- L4 cross-source comparison drifts into a literature review — keep it to 2–3 sources, focus on consensus / divergence / unique value.
+- Output without action steps is a failure mode — every Step-4 synthesis must end with timed, concrete actions tied to the user's goal.
+
+## Do NOT
+
+- Do NOT force-apply all frameworks at the user's chosen depth — drop ones that add no insight.
+- Do NOT copy text verbatim from the source — always reword for the user's understanding.
+- Do NOT use academic jargon without one-line definitions in the "key concepts" block.
+- Do NOT skip Step 5 — the takeaways + quick win are the load-bearing output, not optional decoration.
+- Do NOT route code reviews, diff stress-tests, or incident debugging through this skill.
+
+## Reference modules
+
+Project-local guidelines (full text adopted under the Reference-Guideline Sunset Policy):
+
+- [`scqa-framework`](../../../docs/guidelines/agent-infra/scqa-framework.md) — full 499-line authoritative-link adopt.
+- [`mental-models`](../../../docs/guidelines/agent-infra/mental-models.md) — pure adopt of Munger's multi-discipline toolkit.
+- [`inversion-thinking`](../../../docs/guidelines/agent-infra/inversion-thinking.md) — pre-mortem on decisions, distinct from `adversarial-review`.
+
+Upstream modules (loaded on demand from the SHA-pinned URL in `external_source`):
+
+- `5w2h_analysis.md` — completeness check (7 questions).
+- `critical_thinking.md` — argument quality / fallacy detection.
+- `first_principles.md` — fundamental-truth extraction.
+- `systems_thinking.md` — feedback loops + leverage points.
+- `six_hats.md` — White / Red / Black / Yellow / Green / Blue protocol.
+- `comparison_matrix.md` — cross-source synthesis (L4 only).

package/.agent-src/skills/mobile-e2e-strategy/SKILL.md

@@ -0,0 +1,147 @@
+---
+name: mobile-e2e-strategy
+description: "Use when picking a mobile E2E framework — Detox / Appium / Maestro / XCUITest / Espresso — or planning iOS Simulator / Android Emulator coverage in CI for RN, Expo, or native apps."
+source: package
+---
+
+# mobile-e2e-strategy
+
+## When to use
+
+- Choosing an E2E framework for a mobile app (React Native, Expo, Flutter, native iOS, native Android).
+- Deciding whether to extend existing Playwright/web E2E to mobile or stand up a separate mobile suite.
+- Planning iOS Simulator / Android Emulator coverage in CI (cost, runner type, parallelism).
+- Triaging flaky mobile tests that span the simulator/emulator boundary.
+- Bridging mobile E2E results into the same review surface as web E2E
+  (`playwright-testing`, `e2e-plan`, `e2e-heal`).
+
+**This skill selects and plans — it does not generate test code.** For the chosen framework, apply its own conventions; for the host environment, see the cross-links below.
+
+## Cross-links
+
+- `react-native-setup` — RN/Expo environment, Xcode/Android Studio, EAS Build.
+- `docs/guidelines/agent-infra/ios-simulator-guide.md` — `simctl` / `idb` / accessibility-driven testing on iOS.
+- `playwright-testing` — web E2E baseline (do **not** reuse for native mobile).
+- `e2e-plan` — explore an app and produce an E2E plan in Markdown.
+- `e2e-heal` — debug and fix failing E2E tests.
+
+## Procedure
+
+1. **Classify the app.** Is it native iOS, native Android, React Native, Expo, Flutter, or a web view inside a shell?
+2. **Classify the goal.** Smoke (boots + login + key flow), regression (every release), visual diff, accessibility audit, or performance baseline.
+3. **Pick the framework** using the decision matrix below.
+4. **Confirm host availability.** macOS for iOS Simulator (mandatory); any OS for Android Emulator.
+5. **Plan CI coverage.** Decide runner type, parallelism, and whether iOS coverage runs every PR or nightly only.
+6. **Define the artefact contract.** Screenshots, accessibility trees, video, log archives — name the storage path and retention.
+7. **Validate.** Run a single smoke test locally before wiring CI; verify both iOS and Android paths if both are in scope.
+
+## Decision matrix — framework selection
+
+| Framework | Best for | Avoid when |
+|---|---|---|
+| **Detox** | React Native apps, gray-box testing, deterministic sync with the JS bridge | Native iOS/Android-only; Expo managed without a dev client |
+| **Maestro** | Cross-platform smoke + regression, declarative YAML flows, fast onboarding | Need full programmable assertions or deep native introspection |
+| **Appium** | Truly cross-platform (RN + Flutter + native), one team owning many apps, WebDriver-compatible tooling | Solo project — setup overhead is high; flaky on JS-heavy RN unless tuned |
+| **XCUITest** (iOS) | Native iOS apps, deepest Apple toolchain integration, Xcode Cloud | Cross-platform coverage in one suite |
+| **Espresso** (Android) | Native Android apps, in-process execution, fast reliable runs | Cross-platform coverage in one suite |
+| **Playwright + WebView** | Web app embedded in a thin native shell, purely web flows | Native UI flows of any depth (use a mobile framework instead) |
+
+**Default starting point:**
+
+- React Native / Expo → **Detox** (single-platform RN team) or **Maestro** (cross-platform smoke).
+- Flutter → **Maestro** (smoke) + **Flutter integration_test** (deep) — Flutter-specific, out of scope here.
+- Native iOS only → **XCUITest**.
+- Native Android only → **Espresso**.
+- Mixed native portfolio → **Appium**.
+
+## Host & environment prerequisites
+
+**iOS (macOS-only)**
+- Xcode 16.1+ and matching Command Line Tools — see `react-native-setup`.
+- iOS Simulator boot/install/launch via `simctl` — see `ios-simulator-guide.md`.
+- Optional: `idb` for accessibility-tree access and coordinate-level UI control.
+- Apple developer account only required for physical-device or signed-build runs.
+
+**Android (any host)**
+- Android Studio Ladybug+ with SDK 35, Platform-Tools, Emulator.
+- AVD with API 35 image; verify `emulator -list-avds` and `adb devices`.
+- HAXM/Hypervisor (Intel) or hardware acceleration on Apple Silicon.
+
+**Authoritative upstream docs**
+- iOS Simulator: `https://developer.apple.com/documentation/xcode/running-your-app-in-simulator-or-on-a-device`
+- Android Emulator: `https://developer.android.com/studio/run/emulator`
+- Detox: `https://wix.github.io/Detox/`
+- Maestro: `https://maestro.mobile.dev/`
+- Appium: `https://appium.io/docs/en/latest/`
+- XCUITest: `https://developer.apple.com/documentation/xctest/user_interface_tests`
+- Espresso: `https://developer.android.com/training/testing/espresso`
+
+## CI floor — cost and capacity
+
+| Concern | iOS | Android |
+|---|---|---|
+| Runner OS | macOS only (GitHub `macos-latest`, self-hosted Mac) | Any (Linux fastest) |
+| Boot time | 30–90 s per simulator cold-boot | 60–180 s per emulator cold-boot |
+| Parallelism | 1 simulator per macOS runner is the safe default | KVM-accelerated on Linux scales well |
+| Cost (GitHub Actions) | macOS minutes are ~10× Linux minutes | Standard Linux pricing |
+| Recommended cadence | Nightly + on-release for full suite; smoke on every PR | Every PR feasible |
+
+**Pragmatic split:**
+
+- Every PR: Android emulator full suite + iOS smoke only.
+- Nightly / pre-release: iOS full suite + cross-device matrix.
+- Adjust if the project pays for self-hosted Mac runners or the
+  release cadence demands per-PR iOS parity.
+
+## Artefact contract (recommended)
+
+For every E2E run the suite SHOULD persist:
+
+1. **Screenshots** — per-step PNG, named `{suite}/{test}/{step}.png`.
+2. **Accessibility tree** — JSON dump per failure (iOS via `idb ui describe-all --json --nested`, Android via Espresso accessibility checks).
+3. **Video** — full run on failure; first-class for Detox and Maestro.
+4. **Logs** — structured logcat (Android) or `simctl spawn log` (iOS) filtered to the app under test.
+5. **Result XML / JUnit** — for CI dashboard ingestion.
+
+Retain artefacts for at least one release cycle; promote screenshots
+of failures to the PR comment surface so reviewers see the failure
+without leaving the review.
+
+## Bridging to the existing E2E surface
+
+- **Web + mobile in one repo:** keep Playwright for web, add a separate `mobile/` suite using Detox or Maestro. Do **not** force-fit Playwright onto native UI.
+- **Plan reuse:** the planning patterns in `e2e-plan` (user journeys, test pyramid placement, stable selectors) apply unchanged. The implementation lives in the mobile framework.
+- **Heal reuse:** the diagnostic loop in `e2e-heal` (reproduce → isolate → minimal fix → verify) applies. Replace browser-specific tooling with mobile-framework equivalents (Detox `--loglevel verbose`, Maestro Studio replays, Appium Inspector).
+- **Selectors:** prefer accessibility identifiers (`accessibilityIdentifier` on iOS, `contentDescription` on Android) over coordinate taps — see `ios-simulator-guide.md` Module 1.
+
+## Output format
+
+1. A framework recommendation keyed off app type + team shape + cross-platform need.
+2. A host & runner plan naming the macOS/Linux split for CI.
+3. A cadence plan (per-PR vs nightly) with cost rationale.
+4. An artefact contract listing screenshot/log/video/accessibility-tree paths.
+
+## Auto-trigger keywords
+
+- mobile E2E, React Native E2E, Expo E2E, Flutter E2E
+- Detox, Appium, Maestro, XCUITest, Espresso
+- iOS Simulator, Android Emulator, AVD, simctl, idb
+- mobile CI, mobile test runner, macOS runner cost
+
+## Gotcha
+
+- Mobile E2E is fundamentally slower than web E2E — the test pyramid still applies; do not reach for E2E when a unit or integration test would do.
+- iOS coverage on every PR is expensive on hosted runners; default to smoke on PR + full suite nightly until the cost is measured.
+- React Native + Appium + non-trivial JS bridge timing is the historical flake hotspot — Detox or Maestro avoids the WebDriver layer entirely.
+- Do not chain emulator-only tests from a developer laptop and a CI runner; environment drift (locale, timezone, API level) corrupts deterministic comparisons.
+- Visual regression baselines are tied to a specific simulator/emulator image — pin the image SHA / API level explicitly in CI config.
+- Maestro YAML is concise but not a full language; complex assertions still need Detox / Appium / native frameworks.
+
+## Do NOT
+
+- Do NOT reuse a Playwright suite for native UI flows — accessibility-tree access is wholly different.
+- Do NOT mix two mobile E2E frameworks in one suite — pick one per platform pair, factor shared helpers behind a thin abstraction.
+- Do NOT run iOS E2E on every PR until you measured the macOS-runner cost on the project's actual cadence.
+- Do NOT rely on coordinate taps (`idb ui tap <x> <y>`) for stable tests — use accessibility identifiers instead. Coordinate taps are debug aids, not test selectors.
+- Do NOT fork upstream simulator scripts (`accessibility_audit.py`, `visual_diff.py`, etc.) into the consumer project — link to the upstream SHA per `ios-simulator-guide.md`.
+- Do NOT skip the artefact contract — without screenshots, logs, and accessibility trees, mobile E2E failures are nearly impossible to diagnose.

package/.agent-src/skills/playwright-testing/SKILL.md

@@ -18,6 +18,7 @@ Use this skill when:
 
 **Guideline:** `../../../docs/guidelines/e2e/playwright.md` — full conventions, config templates, CI setup.
 **Rule:** `.augment/rules/e2e-testing.md` — constraints enforced during E2E test work.
+**Mobile:** for native iOS/Android or React Native E2E, do NOT reuse Playwright — see the `mobile-e2e-strategy` skill for framework selection.
 
 ## Procedure: Write Playwright tests
 

package/.agent-src/skills/react-native-setup/SKILL.md

@@ -0,0 +1,221 @@
+---
+name: react-native-setup
+description: "Use when setting up React Native or Expo dev environments — Xcode, Android Studio, CocoaPods, EAS, Metro, New Architecture — even when the user just says 'my RN build won't start'."
+source: package
+---
+
+# react-native-setup
+
+## When to use
+
+- Initial React Native 0.76+ / Expo SDK 52+ environment setup
+- Installing or configuring Xcode, Android Studio, or their command-line tools
+- Setting up iOS simulators or Android emulators for development
+- Troubleshooting "Command not found", `ANDROID_HOME`, or SDK path errors
+- Fixing CocoaPods install failures (Apple Silicon, FFI, Ruby mismatches)
+- Clearing Metro / Watchman cache or diagnosing reload loops
+- Configuring EAS Build, dev clients, or OTA updates
+- Migrating to or troubleshooting the New Architecture (Fabric / Turbo Modules)
+
+**Cross-links:** `mobile-e2e-strategy` (Detox / Appium / Maestro selection),
+`docs/guidelines/agent-infra/ios-simulator-guide.md` (iOS simulator decision matrix).
+
+## Assess current setup before changing anything
+
+Before installing or upgrading anything, inspect what's already there — modifying a working toolchain blindly is the most common source of wasted hours.
+
+1. **Read `package.json`** — RN version, Expo SDK, scripts, native dependencies.
+2. **Check `ios/Podfile` and `ios/Podfile.lock`** — CocoaPods version, deployment target, RCT_NEW_ARCH_ENABLED flag.
+3. **Check `android/build.gradle` and `android/gradle.properties`** — Gradle version, compile/target SDK, `newArchEnabled`, NDK version.
+4. **Verify host tools** — `node --version`, `xcodebuild -version`, `sdkmanager --list_installed`, `pod --version`, `watchman --version`.
+5. **Check for an existing `.nvmrc`, `.tool-versions`, or `Brewfile`** — honour the project's pinned versions over global ones.
+6. **Read project README and CONTRIBUTING** — many RN repos document one-time setup quirks (Apple Silicon Rosetta, Hermes flags, EAS profile names).
+
+## Procedure
+
+1. **Identify the target stack** — RN CLI vs Expo, target SDK, supported OS, monorepo or single-package.
+2. **Verify prerequisites** — Node, package manager, Watchman, platform SDKs (see matrix below).
+3. **Configure platform tooling** — Xcode + CocoaPods (iOS) or Android Studio + SDK 34/35 (Android).
+4. **Install project dependencies** — `npm`/`yarn`/`pnpm`/`bun install`, then `pod install` for iOS.
+5. **Run a smoke build** — `npm run ios` / `npm run android` / `npx expo start`.
+6. **Validate** — app launches, fast refresh works, Metro bundler runs without warnings.
+7. **On failure** — apply the matching pattern from "Common setup issues" below.
+
+## Prerequisites (2025 baseline)
+
+**Node.js**
+- Node 20.x minimum (Node 18 EOL April 2025); Node 22 LTS recommended.
+- `node --version && npm --version`.
+- npm, yarn, pnpm, bun all supported. Corepack for yarn:
+  `corepack enable && corepack prepare yarn@stable --activate`.
+
+**Xcode (macOS, iOS)**
+- Xcode 16.1+ minimum (RN 0.83), Xcode 26+ for Liquid Glass.
+- `xcode-select --install` then `sudo xcodebuild -license accept`.
+- iOS 15.1+ deployment target; iOS 18+/26 for latest features.
+
+**Android Studio**
+- Ladybug or later (2024.2.1+).
+- SDK Platform 35 (API 35), Build-Tools 35.0.0, Platform-Tools, Emulator.
+- NDK 27.1.12297006 + CMake 3.22.1+ for native modules / Turbo Modules.
+- `compileSdkVersion 35`, `targetSdkVersion 35`, `minSdkVersion 24`.
+- `ANDROID_HOME` exported; edge-to-edge display ready (Android 15+).
+
+**Watchman**
+- macOS: `brew install watchman`.
+- Required for fast refresh on large codebases. Reset: `watchman watch-del-all`.
+
+## Platform setup
+
+**iOS**
+- CocoaPods 1.15+: `sudo gem install cocoapods`.
+- New Architecture pods: `RCT_NEW_ARCH_ENABLED=1 pod install`.
+- Provisioning profiles, certificates managed in Xcode or via EAS.
+- Simulator management: `xcrun simctl list devices`. Liquid Glass requires iOS 26 simulator.
+
+**Android**
+- Gradle 8.10+ (bundled with Ladybug).
+- AVD with API 35 image; verify edge-to-edge layout.
+- New Architecture: `newArchEnabled=true` in `gradle.properties`.
+
+**Metro bundler**
+- Default port 8081. Cache reset: `npx react-native start --reset-cache`.
+- Symlink support and custom resolvers needed for monorepos.
+
+**EAS Build (Expo)**
+- `npm install -g eas-cli` then `eas login`.
+- `eas build:configure` to seed `eas.json`.
+- Dev clients for custom native modules; EAS Update for OTA.
+
+## Common setup issues
+
+**"Command not found"**
+- PATH for Node, Android SDK, Xcode tools missing in `~/.zshrc` or `~/.bash_profile`.
+- Symlink drift with nvm / fnm — re-run `nvm use` after shell reload.
+
+**SDK not found**
+- `echo $ANDROID_HOME` empty → re-export.
+- Re-run SDK Manager; reinstall NDK if native modules fail.
+
+**Pod install failures**
+- CocoaPods < 1.15 incompatible with New Architecture — upgrade.
+- Apple Silicon FFI compile errors → use system Ruby or rbenv-managed Ruby.
+- Stuck pods: `pod deintegrate && pod install`.
+
+**Build failures**
+- Clean iOS: `cd ios && rm -rf build Pods Podfile.lock && pod install && cd ..`.
+- Clean Android: `cd android && ./gradlew clean && cd ..`.
+- Clear Xcode derived data when stale build artefacts persist.
+
+**New Architecture issues**
+- Turbo Module not found → confirm codegen ran during build.
+- Fabric component not rendering → verify native registration.
+- Bridge incompatibility → use the interop layer.
+
+## Quick verification
+
+```bash
+node --version          # 20+ (22 LTS preferred)
+npm --version
+xcodebuild -version     # 16.1+
+pod --version           # 1.15+
+adb --version
+emulator -version
+watchman version
+eas --version           # Expo only
+echo $ANDROID_HOME      # non-empty
+```
+
+## Quick commands
+
+**Create / run RN CLI project**
+```bash
+npx @react-native-community/cli init MyProject
+cd MyProject
+cd ios && RCT_NEW_ARCH_ENABLED=1 pod install && cd ..
+npm start                # Metro
+npm run ios              # in a second terminal
+npm run android          # in a third terminal
+```
+
+**Create / run Expo project**
+```bash
+npx create-expo-app@latest MyProject
+cd MyProject
+npx expo start
+# Custom native code → dev client:
+npx expo install expo-dev-client
+eas build --profile development --platform ios
+eas build --profile development --platform android
+```
+
+**Simulator / emulator**
+```bash
+xcrun simctl list devices
+xcrun simctl boot "iPhone 16 Pro"
+emulator -list-avds
+emulator -avd Pixel_8_API_35
+```
+
+**Reset everything**
+```bash
+watchman watch-del-all
+npx react-native start --reset-cache    # RN CLI
+npx expo start --clear                  # Expo
+```
+
+## Pro tips
+
+1. **Shell profile** — add SDK paths once, reload once:
+   ```bash
+   export ANDROID_HOME=$HOME/Library/Android/sdk
+   export PATH=$PATH:$ANDROID_HOME/emulator
+   export PATH=$PATH:$ANDROID_HOME/platform-tools
+   export PATH=$PATH:$ANDROID_HOME/cmdline-tools/latest/bin
+   ```
+2. **EAS minimum `eas.json`** — `development` (dev client + internal), `preview` (internal), `production` (defaults).
+3. **Hermes** — RN ≥ 0.70 ships Hermes by default; verify with `global.HermesInternal !== undefined` at runtime.
+4. **Health check** — a single shell function running the verification block above catches 80 % of "it doesn't build" reports.
+
+## Version compatibility (2025)
+
+| Component | Minimum | Recommended | Notes |
+|---|---|---|---|
+| Node.js | 20.x | 22 LTS | Node 18 EOL April 2025 |
+| React Native | 0.76 | 0.83 | New Architecture default since 0.76 |
+| React | 18.3 | 19.2 | `Activity`, `useEffectEvent` |
+| Expo SDK | 52 | 54 | Native tabs, Liquid Glass |
+| Xcode | 16.1 | 26 | iOS 26 required for Liquid Glass |
+| Android SDK | 34 | 35 | Edge-to-edge support |
+| CocoaPods | 1.14 | 1.15+ | New Architecture compatibility |
+| Gradle | 8.6 | 8.10+ | K2 compiler support |
+
+## Output format
+
+1. A short setup plan keyed off the target stack (RN CLI vs Expo, iOS vs Android vs both).
+2. Concrete shell commands the user can paste — no placeholders unless flagged `<…>`.
+3. A verification block confirming the toolchain is healthy before any feature work.
+
+## Auto-trigger keywords
+
+- React Native, Expo, EAS Build
+- Xcode, CocoaPods, pod install
+- Android Studio, ANDROID_HOME, AVD, emulator
+- Metro bundler, Watchman, fast refresh
+- New Architecture, Fabric, Turbo Modules
+
+## Gotcha
+
+- Don't set `RCT_NEW_ARCH_ENABLED=1` selectively — once enabled, every `pod install` for that project must use it or cached artefacts diverge.
+- Apple Silicon + system Ruby + FFI is the single biggest source of "pod install hangs" reports — switch to rbenv before retrying.
+- Watchman left over from a previous project can pin Metro to a stale tree — `watchman watch-del-all` is cheap, run it before deeper debugging.
+- iOS Simulator versions are tied to Xcode versions. Liquid Glass features need both Xcode 26 AND an iOS 26 simulator image installed.
+- Android NDK version drift breaks Turbo Modules silently — pin `27.1.12297006` until the project explicitly upgrades.
+
+## Do NOT
+
+- Do NOT mix `npm`, `yarn`, `pnpm`, and `bun` lockfiles in the same project — pick one, commit its lockfile, delete the others.
+- Do NOT skip `pod install` after pulling iOS-side changes — the JS bundle will load but native modules will be stale.
+- Do NOT enable New Architecture mid-feature — flag it on a clean branch, run a full clean build, validate both platforms.
+- Do NOT hand-edit `Podfile.lock` or `gradle.lock`-style files — re-run the installers instead.
+- Do NOT commit `node_modules`, `ios/Pods`, `android/.gradle`, or platform `build/` directories.

package/.agent-src/skills/roadmap-writing/SKILL.md

@@ -152,6 +152,6 @@ to every roadmap you author.
 
 ## Examples
 
-See `agents/roadmaps/archive/road-to-token-frugality.md`
-(structural, multi-phase, council-integrated) and any
-`agents/roadmaps/road-to-*.md` for canonical structure.
+Browse `agents/roadmaps/` (active plate) and `agents/roadmaps/archive/`
+(closed work) for canonical structural / tactical / structural-with-council
+examples.

package/.agent-src/templates/agent-settings.md

@@ -453,7 +453,7 @@ the canonical narrative lives in
 | `commands.suggestion.max_options` | integer | `4` | Max number of command suggestions before the always-present "run as-is" option (total rendered = `max_options + 1`). |
 | `commands.suggestion.blocklist` | list of command names | `[]` | Commands that never appear as a suggestion. They still work when typed explicitly. |
 | `commands.create_pr.preview_description` | `true`, `false` | `false` | When `false`: `/create-pr` skips the title/body preview + adjust loop and uses the generated content directly. Saves agent tokens. When `true`: show title and body before creating and ask for adjustments. `/create-pr:description-only` always previews regardless of this setting. |
-| `verbosity.preview_artifacts` | `true`, `false` | `false` | Show generated commit messages, PR titles/bodies, branch names before acting. `false` = use generated content directly. See [`road-to-token-frugality`](../../../agents/roadmaps/road-to-token-frugality.md) Phase 2/3. |
+| `verbosity.preview_artifacts` | `true`, `false` | `false` | Show generated commit messages, PR titles/bodies, branch names before acting. `false` = use generated content directly. See the token-frugality plate under `agents/roadmaps/` (Phase 2/3). |
 | `verbosity.routine_confirmations` | `true`, `false` | `false` | Confirmation prompts for routine workflow steps when there is one obvious answer ("looks good — commit?"). Iron-Law gates (`commit-policy`, `scope-control` git-ops, `non-destructive-by-default`) ALWAYS ask regardless. |
 | `verbosity.offer_council_in_delivery` | `true`, `false` | `false` | Offer "run AI Council on this?" inside delivery commands (`/feature-plan`, `/review-changes`, `/roadmap-create`). Council commands themselves are unaffected. |
 | `verbosity.post_action_reports` | `off`, `minimal`, `full` | `minimal` | Multi-line status / summary blocks after a successful action. `off` = no report; `minimal` = one-line confirmation; `full` = bullet list. |

package/.claude-plugin/marketplace.json

@@ -6,7 +6,7 @@
   },
   "metadata": {
     "description": "Shared agent configuration \u2014 skills for AI coding tools (Claude Code, Augment, Cursor, Cline, Windsurf, Gemini CLI).",
-    "version": "1.26.0"
+    "version": "1.28.0"
   },
   "plugins": [
     {
@@ -80,6 +80,7 @@
         "./.claude/skills/data-flow-mapper",
         "./.claude/skills/database",
         "./.claude/skills/dcf-modeling",
+        "./.claude/skills/deep-reading-analyst",
         "./.claude/skills/dependency-upgrade",
         "./.claude/skills/description-assist",
         "./.claude/skills/design-review",
@@ -153,6 +154,7 @@
         "./.claude/skills/memory-propose",
         "./.claude/skills/merge-conflicts",
         "./.claude/skills/migration-creator",
+        "./.claude/skills/mobile-e2e-strategy",
         "./.claude/skills/mode",
         "./.claude/skills/module",
         "./.claude/skills/module-create",
@@ -198,6 +200,7 @@
         "./.claude/skills/prompt-optimizer",
         "./.claude/skills/quality-fix",
         "./.claude/skills/quality-tools",
+        "./.claude/skills/react-native-setup",
         "./.claude/skills/react-shadcn-ui",
         "./.claude/skills/readme-reviewer",
         "./.claude/skills/readme-writing",
@@ -206,6 +209,7 @@
         "./.claude/skills/refine-prompt",
         "./.claude/skills/refine-ticket",
         "./.claude/skills/requesting-code-review",
+        "./.claude/skills/research",
         "./.claude/skills/review-changes",
         "./.claude/skills/review-routing",
         "./.claude/skills/rice-prioritization",