conductor-rewrite-performance
Use when building or optimizing a local-first desktop app with React, dealing with excessive re-renders during navigation, slow chat/list UIs with streaming content, or profiling a Tauri app without native Chrome DevTools access.
boraoztunc · 已有 AI 审核记录
安装与使用
运行命令前先阅读来源与依赖说明。复制命令不会自动安装或执行。
npx skills add boraoztunc/skills --skill conductor-rewrite-performance技能说明
name: conductor-rewrite-performance description: "Use when building or optimizing a local-first desktop app with React, dealing with excessive re-renders during navigation, slow chat/list UIs with streaming content, or profiling a Tauri app without native Chrome DevTools access."
When to use this skill
- You're building a local-first desktop application with React and experiencing performance bottlenecks
- Navigation or route changes trigger cascading re-renders across multiple mounted components
- You have a chat interface or long list that streams content and re-renders become sluggish
- You're using Tauri and need to profile React performance but can't access Chrome DevTools
- Multiple heavy views are mounted simultaneously (sidebar, nav, chat, terminal, editor) and all re-render on state changes
- You need to manage multiple heavyweight child processes without exhausting system memory
Core principles
-
Local-first eliminates an entire category of performance problems. When SQLite is your source of truth and the UI never waits on the network, the bottleneck moves up into the rendering layer—every unnecessary re-render becomes the slowest thing users feel.
-
Unstable references cascade re-renders through the entire component tree. When router hooks return fresh objects on every render, every component reading them re-renders even when values haven't changed, and those re-renders propagate to all children.
-
Virtualization plus memoization is the only way to make streaming lists fast. Render only what's on screen (15 messages instead of 500), and ensure only the actively changing item re-renders while the rest stay memoized.
-
The fastest operation is the one the user never waits on. Move expensive synchronous work (like git checkpoints) off the critical path so the first token arrives immediately.
Tactics
Shim the Tauri bridge to profile in Chrome
When you can't use Safari's Web Inspector to debug React performance in a Tauri webview, create a development shim that lets the same client run in Chrome with full DevTools access.
// Conductor's UI reaches the Rust core through Tauri's invoke() bridge.
// In a real browser there's no Tauri runtime: __TAURI_INTERNALS__ is
// undefined and every invoke() throws. So in dev we shim that single
// entry point and boot the exact same client in Chrome, where the
// Chrome profiler AND the React DevTools profiler both work.
import { invoke as tauriInvoke } from "@tauri-apps/api/core";
export function invoke<T>(cmd: string, args?: Record<string, unknown>): Promise<T> {
// Packaged app: use the native bridge.
if ("__TAURI_INTERNALS__" in window) return tauriInvoke<T>(cmd, args);
// Dev in Chrome: stand in for the Rust backend. Proxy to a dev server
// running the real commands, or return canned data for the surface
// you're profiling.
return fetch(`/__backend__/${cmd}`, {
method: "POST",
body: JSON.stringify(args ?? {}),
}).then((r) => r.json());
}
Steps:
- Identify the single bridge function your UI uses to talk to the native layer (e.g., Tauri's
invoke()) - Check for the presence of the native runtime object (
__TAURI_INTERNALS__) - In production, call through to the real bridge
- In development, proxy to a local server or return mock data
- Boot the client in Chrome and use React DevTools Profiler to identify bottlenecks
Replace react-router with TanStack Router for stable references
When navigation produces fresh param/search references that cascade re-renders, switch to a router that provides structural sharing and stable references.
Before with react-router:
// Before with react-router
import { useSearchParams } from "react-router-dom";
function WorkspaceView() {
const [searchParams] = useSearchParams();
// useSearchParams() returns a NEW URLSearchParams every render,
// and this parsed object is a new reference every render too.
const filters = {
agent: searchParams.get("agent"),
status: searchParams.get("status"),
};
useEffect(() => {
refetchAgents(filters);
}, [filters]); // new object each render → fires on EVERY render
return <AgentList filters={filters} />; // child re-renders every time
}
After with TanStack Router:
// After with tanstack router
import { createFileRoute } from "@tanstack/react-router";
export const Route = createFileRoute("/workspace")({
// parse + validate search once, fully typed
validateSearch: (s): { agent?: string; status?: string } => ({
agent: s.agent as string | undefined,
status: s.status as string | undefined,
}),
});
function WorkspaceView() {
// structural sharing: SAME reference unless agent/status actually change
const filters = Route.useSearch();
useEffect(() => {
refetchAgents(filters);
}, [filters]); // fires only when a value really changes
return <AgentList filters={filters} />; // no re-render!
}
Steps:
- Define routes with
createFileRouteand add avalidateSearchfunction that parses and types search params - Replace
useSearchParams()withRoute.useSearch()to get a stable reference - Remove manual
useMemowrappers around parsed params—structural sharing handles it - Verify with React DevTools Profiler that only components with actual changes re-render on navigation
Virtualize + memoize streaming chat lists
When a chat UI with hundreds of messages re-renders on every token, combine virtualization (render only visible items) with memoization (skip unchanged items).
Before:
// Before: the simple approach where each message/token rerenders everything
function Chat({ messages }) {
return (
<div>
{messages.map((m) => (
<Message key={m.id} message={m} /> // all N re-render on each token
))}
</div>
);
}
After:
// After: virtualize the list + memoize each row
const Message = React.memo(function Message({ messa
阅读完整来源 ↗