grove

Run and interpret Grove workspace scale performance benchmarks using `benchmark-scale`, including baseline capture, regression comparison, and optimization loops. Use when user asks about performance, scale, regressions, startup/discovery speed, polling/update throughput, p50/p95 timings, or benchmark harness usage. Trigger phrases: "benchmark-scale", "workspace scale", "perf regression", "p95", "performance baseline", "issue 38".

Instrumentation best practices for Grove's NDJSON event logging. Use when adding/changing log events, event fields, or logging schema in runtime code. Not for replay triage, use `replay-debug` for trace analysis and divergence debugging. Trigger phrases: "how to log", "add logging", "add event", "instrumentation", "telemetry", "event schema".

Replay and analyze Grove debug-record traces. Use when debugging runtime regressions, polling races, interactive input bugs, state transitions, frame/render mismatches, or when user asks to analyze `.grove/debug-record`. Not for instrumentation design, use `logging-best-practices` when adding or changing log events/fields. Trigger phrases: "replay", "debug record", "analyze trace", "runtime race", "timing bug", "state mismatch".

Look up FrankenTUI framework APIs, patterns, and examples from the reference codebase at .reference/frankentui/. Use when asking about FrankenTUI APIs, widgets, layout, subscriptions, rendering, styling, hit testing, or any ftui-* crate. Trigger phrases: "frankentui", "ftui", "how does frankentui", "ftui widget", "ftui layout", "ftui subscription", "ftui runtime".