claude-code

Use when creating, reviewing, or updating a BRIEF.md (the quality law for a surface), defining what "good"/shippable means, or setting up a verified autonomous loop.

Use when checking deployment health, investigating errors, reading logs, or working with Tiltfiles. Queries Tilt resource status, logs, and manages dev environments.

Use when starting tilt, debugging Tiltfile errors, or bootstrapping a dev environment. Starts Tilt in zmx, monitors bootstrap to healthy state, fixes Tiltfile bugs without hard-coding or fallbacks.

Use when creating commits, managing branches, opening PRs, or rewriting history. Not for non-git implementation tasks or repo-specific release policy decisions.

Use when syncing a feature branch onto the latest origin base branch via git rebase.

Fetch latest from origin, prune remote-tracking refs, delete stale local branches and worktrees, and fast-forward important branches. Use when tidying up a worktree-based repo layout.

Use when interacting with USB-attached iOS devices via pymobiledevice3 — screenshots, syslog, crash reports, app install/launch/pull, file transfer, sysmon perf, TCP port forwarding, WebInspector/CDP, and device diagnostics.

Use when reading or writing React components (.tsx, .jsx files with React imports).

Use when creating, reviewing, or updating SPEC.md files, running /specout, or entering the ADF SPEC gate.

Use when automating iOS Simulator interactions, capturing screenshots/video, or inspecting accessibility via AXe CLI.

Use when working with Canton Network participants, DAML smart contracts, Splice applications, or debugging LF version and package ID issues.

Use when running e2e tests, debugging test failures, or fixing flaky tests. Covers failure taxonomy, fix rules, and workflow. Never changes source code logic or API without spec backing.

Use when reading or writing Go files (.go, go.mod).

Use after completing a task, before claiming done, before handoff, or when asked "what are some improvements?" Surfaces concrete suggestions grounded in session observations.

Use when working with Nix flakes, overlays, shell.nix, or flake.nix files.

Use when reading from 1Password, discovering vaults/items, rotating secrets, or piping credentials to other tools via op CLI.

Use when working with OrbStack Linux VMs, Docker on macOS, orbctl commands, or orb machine lifecycle.

Use when writing or modifying Playwright tests (.spec.ts, .test.ts with @playwright/test imports).

Use when reading or writing Python files (.py, pyproject.toml, requirements.txt).

Use when working with Tamagui projects (tamagui.config.ts, @tamagui imports).

Use when designing tests, writing test cases, or planning test strategy for a module. Covers unit, integration, and e2e layering.

Use when reading or writing TypeScript or JavaScript files (.ts, .tsx, .js, tsconfig.json).

Use when reading or writing Zig files (.zig, build.zig, build.zig.zon).

Use when starting dev servers, watchers, tilt, or any process expected to outlive the conversation. Provides zmx session management patterns for long-lived processes.

Use when there are multiple independent subtasks that can progress in parallel without overlapping ownership or blocking the next local step

Use when requirements are clear enough to plan and the work spans multiple steps, files, or verification stages

Use when creating or editing a skill and you need it to be discoverable, concise, and native to the target harness

Use when building or maintaining Electrobun desktop apps in TypeScript, including electrobun.config.ts, electrobun/bun or electrobun/view imports, BrowserWindow/BrowserView usage, updater flows, and distribution artifacts.

Use when working with atlas.hcl, Atlas CLI commands, schema HCL/SQL files, or migration planning and reviews, including Atlas v1.1 security, data, and exporter capabilities.

Fetches web content as clean markdown by preferring markdown-native responses and falling back to selector-based HTML extraction. Use for documentation, articles, and reference pages at http/https URLs.