GitDesktop

GitDesktop repo playbook — hard safety rules, frontend and Rust/Tauri conventions, verification commands, and hard-won gotchas that are NOT in CLAUDE.md. Consult this before writing, refactoring, or reviewing ANY code in this repo, even for small changes. Preloaded into the implementer and spec-reviewer subagents; the main conversation should read it before direct implementation work too.

React best-practice and performance rules from Vercel Engineering — 70 rules spanning eliminating waterfalls, bundle size, server/client data fetching, re-renders, and memoization. Use whenever writing, reviewing, or refactoring ANY React component, hook, effect, or data-fetching code — this covers plain React apps (NOT just Next.js) and everyday component work, not only explicit performance passes. Consult it before and while implementing so the patterns shape the code, rather than as an after-the-fact review.

Orchestrate delegated implementation in GitDesktop — the main model (Fable or Opus) architects, plans, and integrates; Opus subagents implement and review. Gated to Fable/Opus orchestrators (Sonnet and smaller work inline instead). Use whenever the user asks to delegate, fan out, or parallelize implementation work, says "have opus build/implement X", or hands over a well-scoped multi-file feature that should be built by subagents rather than inline. Also applies when resuming a partially delegated feature.