القائمة
Use when reproducing or diagnosing runtime behavior in the running oats desktop app — driving and inspecting its windows via the oats-desktop MCP server (execute JS, read DOM, invoke backend commands). Pairs with systematic-debugging.
التثبيت باستخدام Codex أو Claude انسخ هذا Prompt والصقه في Codex أو Claude أو مساعد آخر ليراجع صفحة Skill ويثبّتها لك.
استنادا إلى تصنيف SOC المهني
Use to orient in the oats codebase or plan cross-cutting features — the cloud-vs-offline backend split, the speech-to-text pipeline, window topology, and where specs live.
Use when changing oats backend — Rust commands in src-tauri, the invoke contract, capabilities/permissions, Tauri plugins, multi-window, or running the cargo test suite. Includes the macOS build/test workarounds.
Use when changing oats code that touches auth/OAuth, session tokens, the capabilities allowlist, a Tauri invoke command, file paths, URL/deep-link opening, the sidecar, network calls, or the offline-mode privacy guarantee. Encodes this app's real attack surface and a pre-PR review checklist.
Use when building or changing oats frontend UI — Vue 3 components, views, composables, routing, Tailwind, or the TipTap notes editor. Encodes this repo's frontend conventions.
| name | oats-debugging |
| description | Use when reproducing or diagnosing runtime behavior in the running oats desktop app — driving and inspecting its windows via the oats-desktop MCP server (execute JS, read DOM, invoke backend commands). Pairs with systematic-debugging. |
oats ships a Tauri MCP server (tauri-plugin-mcp) that lets you drive the live app —
list windows, screenshot, execute JS in a webview, and call backend commands. Use it to
verify a fix in the real app, not just in unit tests. Pair this with superpowers'
systematic-debugging for the methodology.
It is registered in .mcp.json as oats-desktop. In Claude Code, it may be
disabled by default in .claude/settings.local.json (disabledMcpjsonServers);
remove it from that list or approve the server when prompted. The app must be launched
with the MCP feature:
npm run tauri:dev:debug # = tauri dev --features mcp
Run it in the background with the sandbox disabled (cargo must compile and the GUI / network must spawn). It's a never-exiting dev server — don't wait on it to "finish".
Routes live in src/main.ts. See oats-architecture for the full map. Quick version:
settings — the settings window (pre-created hidden).library — titled "Meetings"; the main user-facing window.main — headless/blank BootstrapView; a blank screenshot of it is expected.execute_js times out until the
window is shown and focused. Show the window first.window.__TAURI__ is not exposed (the app uses ESM
@tauri-apps/api). Call commands via
window.__TAURI_INTERNALS__.invoke('cmd_name', args).await — make the last expression a promise; the tool resolves it.tauri:dev:debug in the background.show the target window before any execute_js.__TAURI_INTERNALS__.invoke(...) to isolate frontend vs Rust.oats-vue / oats-tauri and re-verify here.