菜单
Stack-native React performance patterns for this Vite SPA (React 19, MUI, TanStack Query, Cloudflare Workers). Use when optimizing bundles, waterfalls, re-renders, or client fetch behavior — not for repo-wide refactors (optimize2) or Lighthouse audits (web-perf).
用 Codex 或 Claude 帮你安装 复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。
基于 SOC 职业分类
Bundles all uncommitted work from multiple Cursor agent threads on the same branch and checkout into one finish commit, then pushes. Use when the user runs /bundle-ship, /finish-all, or asks to finish and push everything across threads on one checkout.
Interview the user until scope edges and interaction boundaries are aligned and the decision tree is resolved. Focuses on where the feature stops, what it will NOT do or touch, and how it meets other functionality. Chat-only alignment — authors no artifact. Use to stress-test scope/boundaries before feature or plan, or when the user says "grill me".
Picks the next action and skill, then invokes it (read that SKILL.md and execute the workflow in the same turn). Mid-thread: continue the logical next step on active work. Idle or new: fall back to gates and app-tasks.json backlog. Maps situations to project, user, and plugin skills; resolves overlaps. Product context SSOT: documentation/DOC_APP_VISION.md. Use when the user types /router, asks which skill to use, starts ambiguous work, or routes slash commands to SKILL.md files. Bare /router is next-action dispatch (not finish).
Challenges and simplifies a concrete feature to reduce steps, clicks, and cognitive load (flow and code modes by default). Use when the user targets a workflow and asks whether it is overbuilt, or runs /challenge.
Systematically audit the codebase for consolidation, abstraction, and redundancy removal opportunities across features. Use when the user asks to find duplication, consolidate code, audit for redundancy, reduce repetition, or identify shared patterns that should be unified.
Structured scientific debugging for runtime bugs, regressions, flaky behavior, frontend/backend failures, Supabase/RLS/Auth/Storage issues, and user-reported errors. Use when the user invokes /debug, asks to debug, reports an error, or describes inconsistent behavior.
| name | react-perf-vite |
| description | Stack-native React performance patterns for this Vite SPA (React 19, MUI, TanStack Query, Cloudflare Workers). Use when optimizing bundles, waterfalls, re-renders, or client fetch behavior — not for repo-wide refactors (optimize2) or Lighthouse audits (web-perf). |
On-demand performance playbook for this repo's stack. Rules live in rules/ — read only the files relevant to the task.
SSOT for server state: TanStack Query — see documentation/DOC_TANSTACK_QUERY.md and architecture/RULE.md § Plain optimistic + server-canonical response.
Human overview: documentation/DOC_REACT_PERF.md.
| Use instead | When |
|---|---|
optimize2 | Hotspot refactor across design → approach → efficiency → complexity; Rule of Three |
web-perf | Browser-measured CWVs, traces, network (DevTools MCP) |
review | Component quality rubric (props, MUI, a11y) |
| SWR / Next.js patterns | This repo uses TanStack Query + Vite — not applicable |
Do not add a compiled AGENTS.md in this folder — it would bloat every agent turn.
| Priority | Prefix | Rules |
|---|---|---|
| CRITICAL | async- | parallel, defer-await, cheap-condition-before-await |
| CRITICAL | bundle- | barrel-imports, lazy-routes, preload, defer-third-party |
| HIGH | worker- | parallel-fetch, hoist-static-io |
| MEDIUM-HIGH | client- | tanstack-dedup, passive-event-listeners, localstorage-schema |
| MEDIUM | rerender- | no-inline-components, derived-state-no-effect, move-effect-to-event, functional-setstate, simple-expression-in-memo |
| MEDIUM | rendering- | content-visibility, conditional-render |
| LOW-MEDIUM | js- | tosorted-immutable |
rules/<name>.md only.@/ imports, feature layers, TanStack keys).optimize2.Adapted from Vercel React Best Practices (MIT). Next.js / RSC / SWR rules were dropped; Vite + TanStack + Workers mappings added. Re-vendor upstream only into documentation/vendor/ if refreshing — never restore a nested AGENTS.md under .agents/skills/.