vercel-react-best-practices
React and Next.js performance optimization guidelines from Vercel Engineering. This skill should be used when writing, reviewing, or refactoring React/Next.js code to ensure optimal performance patterns. Triggers on tasks involving React components, Next.js pages, data fetching, bundle optimization, or performance improvements.
- License 许可
- MIT
- 所属仓库
- fmal/dotfiles
- 最近更新
- 2026-11-09
- Stars
- ★ 3
- Forks
- 0
01 前言 Front Matter
- name
- industrial-pursuit-tender-handover
- version
- 1
- triggers
- [ "tender response", "spec-shaping", "bill of quantities", "epc pursuit", "bid deadline", "site handover", "distributor enablement" ]
- description
- Use for engineered or project-based deals that run from spec-shaping through tender, bid, contract, and site handover.
02 资源文件 75
- 参考文档AGENTS.md104.0 KB
- 参考文档README.md3.3 KB
- 参考文档rules/_sections.md1.5 KB
- 参考文档rules/_template.md631 B
- 参考文档rules/advanced-effect-event-deps.md1.8 KB
- 参考文档rules/advanced-event-handler-refs.md1.4 KB
- 参考文档rules/advanced-init-once.md958 B
- 参考文档rules/advanced-use-latest.md1.0 KB
- 参考文档rules/async-api-routes.md1.1 KB
- 参考文档rules/async-cheap-condition-before-await.md1.2 KB
- 参考文档rules/async-defer-await.md2.2 KB
- 参考文档rules/async-dependencies.md1.3 KB
- 参考文档rules/async-parallel.md654 B
- 参考文档rules/async-suspense-boundaries.md2.5 KB
- 参考文档rules/bundle-analyzable-paths.md2.3 KB
- 参考文档rules/bundle-barrel-imports.md2.7 KB
- 参考文档rules/bundle-conditional.md949 B
- 参考文档rules/bundle-defer-third-party.md920 B
- 参考文档rules/bundle-dynamic-imports.md791 B
- 参考文档rules/bundle-preload.md1.1 KB
- 参考文档rules/client-event-listeners.md1.9 KB
- 参考文档rules/client-localstorage-schema.md1.9 KB
- 参考文档rules/client-passive-event-listeners.md1.6 KB
- 参考文档rules/client-swr-dedup.md1.1 KB
- 参考文档rules/js-batch-dom-css.md3.2 KB
- 参考文档rules/js-cache-function-results.md1.9 KB
- 参考文档rules/js-cache-property-access.md532 B
- 参考文档rules/js-cache-storage.md1.6 KB
- 参考文档rules/js-combine-iterations.md753 B
- 参考文档rules/js-early-exit.md1.1 KB
- 参考文档rules/js-flatmap-filter.md1.4 KB
- 参考文档rules/js-hoist-regexp.md1.0 KB
- 参考文档rules/js-index-maps.md837 B
- 参考文档rules/js-length-check-first.md1.7 KB
- 参考文档rules/js-min-max-loop.md2.2 KB
- 参考文档rules/js-request-idle-callback.md2.6 KB
- 参考文档rules/js-set-map-lookups.md532 B
- 参考文档rules/js-tosorted-immutable.md1.7 KB
- 参考文档rules/rendering-activity.md564 B
- 参考文档rules/rendering-animate-svg-wrapper.md1.2 KB
- 参考文档rules/rendering-conditional-render.md980 B
- 参考文档rules/rendering-content-visibility.md815 B
- 参考文档rules/rendering-hoist-jsx.md1.0 KB
- 参考文档rules/rendering-hydration-no-flicker.md2.3 KB
- 参考文档rules/rendering-hydration-suppress-warning.md872 B
- 参考文档rules/rendering-resource-hints.md2.5 KB
- 参考文档rules/rendering-script-defer-async.md1.8 KB
- 参考文档rules/rendering-svg-precision.md588 B
- 参考文档rules/rendering-usetransition-loading.md2.0 KB
- 参考文档rules/rerender-defer-reads.md973 B
- 参考文档rules/rerender-dependencies.md824 B
- 参考文档rules/rerender-derived-state-no-effect.md1.2 KB
- 参考文档rules/rerender-derived-state.md728 B
- 参考文档rules/rerender-functional-setstate.md2.9 KB
- 参考文档rules/rerender-lazy-state-init.md2.0 KB
- 参考文档rules/rerender-memo-with-default-value.md1.1 KB
- 参考文档rules/rerender-memo.md1.1 KB
- 参考文档rules/rerender-move-effect-to-event.md1.2 KB
- 参考文档rules/rerender-no-inline-components.md2.1 KB
- 参考文档rules/rerender-simple-expression-in-memo.md1018 B
- 参考文档rules/rerender-split-combined-hooks.md1.8 KB
- 参考文档rules/rerender-transitions.md1.0 KB
- 参考文档rules/rerender-use-deferred-value.md1.8 KB
- 参考文档rules/rerender-use-ref-transient-values.md1.7 KB
- 参考文档rules/server-after-nonblocking.md2.0 KB
- 参考文档rules/server-auth-actions.md2.6 KB
- 参考文档rules/server-cache-lru.md1.3 KB
- 参考文档rules/server-cache-react.md2.2 KB
- 参考文档rules/server-dedup-props.md2.0 KB
- 参考文档rules/server-hoist-static-io.md4.3 KB
- 参考文档rules/server-parallel-fetching.md1.5 KB
- 参考文档rules/server-parallel-nested-fetching.md992 B
- 参考文档rules/server-serialization.md996 B
- 参考文档rules/useeffect-alternatives.md4.9 KB
- 参考文档rules/useeffect-anti-patterns.md6.0 KB
03 SKILL.md 正文
Industrial pursuit tender handover
Use this for engineered or project-based deals. Start from the project or tender, the consultants or architects shaping the spec, the bid deadline and bond or qualification needs, the distributor or engineering, procurement and construction (EPC) partners involved, and the handover site and date if known.
Shape the spec before it freezes
Map which consultants and architects write the requirements, what language favors your solution, and the dated steps to get it specified. Prescription work is dated like any close step.
Validate the solution with the buyer
Confirm the design meets the spec, prep the bill of quantities (BoQ) with quantities the buyer has confirmed, and price only against the validated BoQ.
Run the stage plan to handover
Survey, solution, design, tender, bid, contract, handover. Each stage has an owner, a date, and an exit test. A stage is done only when its exit test passes.
Program-manage large and EPC pursuits
One tracker across engineering, supply, distributors, and the buyer, with the most-stuck item first at every check. Distributors get tasks with dates, not FYIs. Introduce new products through the channel: train and enable the distributors who will quote and support them, and log who was trained on what and when.
Hand over clean
Confirm install or delivery readiness, open items with owners and dates, and the service contact the site calls first. Nothing is "done" with unnamed open items.
What you hand back
The spec-shaping plan with dated steps, the validated BoQ, the stage plan with exit tests, the EPC tracker with the stuck item first, the distributor training log, and a handover sheet with open items.
Fallbacks
No spec access means you draft the consultant-discovery questions and work from the published tender docs. No BoQ inputs means you list the quantities needed and who confirms each.
Approval gate
Nothing goes to the buyer, the consultant, or the EPC and no price or delivery date is promised without your explicit yes.
04 同仓库更多 Skills
vercel-composition-patterns
React composition patterns that scale. Use when refactoring components with boolean prop proliferation, building flexible component libraries, or designing reusable APIs. Triggers on tasks involving compound components, render props, context providers, or component architecture. Includes React 19 API changes.
improve
Survey any codebase as a senior advisor and produce prioritized, self-contained implementation plans for OTHER models/agents to execute. Strictly read-only on source code — never implements, fixes, or refactors anything itself. Use when asked to audit a codebase, find improvement opportunities (bugs, security, performance, test coverage, tech debt, migrations, DX), suggest features or where to take the project next (roadmap, product direction), or generate handoff plans for another agent to implement.