Token导航 LogoToken导航

Agent Skill · 前端设计

react-optimise(React optimise 前端)

用于辅助前端页面、组件、样式和交互逻辑的开发与维护。它适合让 Agent 生成或审查 React、Next.js、Vue、Tailwind、CSS 等相关代码,整理组件结构,或定位布局和性能问题。使用时需要结合项目现有设计系统、路由和构建方式,避免只生成孤立片段;涉及页面改动时,应配合本地预览和构建检查确认视觉效果。

react-optimise 是前端设计类 Agent Skill,可用宿主为 Codex、Claude、Cursor、Gemini CLI,通过GitHub 仓库获取,权限为需要联网;许可证信息还不明确,第三方扫描已通过,按安装量在前端设计类的 10,216 个 Skill 里排第 1,793。

总安装 3,834周安装 163GitHub Stars 131下载 1,343核验 2026-05-01

安装说明

本站只整理中文说明,不托管安装包,也不代用户安装。
GitHub
许可证
unknown

安装方式

通过对话安装

复制提示词发给支持本地命令或 Skills 的 AI 助手,先确认命令和权限,再让它执行。

请帮我安装这个 Agent Skill:react-optimise(React optimise 前端)
来源仓库:https://github.com/pproenca/dot-skills
仓库路径:skills/react-optimise
安装命令:
npx skills add https://github.com/pproenca/dot-skills --skill react-optimise
安装前请先检查当前环境是否支持对应 CLI,并向我确认将要执行的命令、安装目录、联网范围和文件读写权限;确认后再执行。

命令行安装

复制命令到本机终端执行。该命令会通过 npx skills 从第三方来源获取 Skill;本站只展示命令,不托管安装包,也不自动执行。

skills.shnpx skills
npx skills add https://github.com/pproenca/dot-skills --skill react-optimise

这个 Skill 是做什么的

前端设计类 Skill 关注页面结构、视觉规范和组件写法,输出通常是可运行的界面代码。

系统性优化 React 应用性能,从渲染效率、内存占用与包体积多角度切入改进。适用于存在卡顿现象、加载缓慢或资源消耗异常的前端项目诊断与修复。可识别不必要的重渲染、大尺寸状态变更及未优化的依赖项提供重构建议。需配合 React DevTools 分析组件树更新频率作为优化基准依据。

每次优化后应对比前后性能指标,确保收益大于潜在复杂度代价。

来源仓库内路径:skills/react-optimise

上手步骤

4 步
  1. 1

    确认自己的宿主工具

    公开资料标注支持 Codex、Claude、Cursor、Gemini CLI;先确认自己用的是其中之一,再按对应工具的 Skills 目录放置。

  2. 2

    拿到安装命令

    可以直接复制的命令是 npx skills add https://github.com/pproenca/dot-skills --skill react-optimise;命令里的占位符换成自己的路径或密钥再执行。

  3. 3

    安装后重启宿主

    命令执行完要完全退出宿主工具再打开,让新装的 Skill 被重新扫描到,否则列表里可能看不到。

  4. 4

    按最小权限试用

    它需要需要联网,先在测试目录或测试账号里跑,确认没问题再放到正式项目。

常见问题

6 条

react-optimise 怎么安装?

在终端执行 npx skills add https://github.com/pproenca/dot-skills --skill react-optimise。装完完全退出宿主工具再打开,让它重新扫描本地 Skill。

react-optimise 支持哪些 AI 工具?

公开资料标注支持 Codex、Claude、Cursor、Gemini CLI。其他工具只要能读取本地 Skill 目录,一般也能手动放进去,但要自己确认触发方式是否一致。

react-optimise 需要什么权限?

权限级别是需要联网。该 Skill 可能需要联网访问来源站点、仓库或外部 API;具体网络访问范围需要结合源码和 README 复核。

react-optimise 是免费的吗?

公开资料没有标注明确许可证,收费和商用限制都无法确认。正式使用前请到来源仓库核对授权说明。

react-optimise 用的人多吗?

公开数据是累计安装 3,834 次,近一周安装 163 次,下载 1,343 次,GitHub 131 星。这些数字来自第三方目录统计,只能当作热度参考,不代表质量或安全性。

react-optimise 安全吗?

第三方扫描结果为通过,但这只覆盖已知的静态检查项,不能替代自己读一遍源码和安装命令。

值得选的地方和要先想清楚的地方

值得选的地方

  • 同时适配 4 种工具,换客户端不用重新找替代品。
  • 第三方扫描已通过,常见的高风险行为没有命中。

先想清楚的地方

  • 许可证没有明确标注,能不能商用、能不能再分发都不确定。
  • 第三方目录整理,版本更新和行为细节以来源仓库为准。

适不适合你

更适合

  • 已经在用 Codex,想直接扩展它能力的人。
  • 需要处理前端设计类任务、又不想每次都手写提示词的人。

不太适合

  • 需要明确授权才能用到公司项目里的场景。
  • 需要厂商级技术支持和 SLA 的生产系统。

前端设计类 Skill 对比

6 个同类
Skill总安装GitHub 星权限许可证扫描
frontend-design

前端设计 · Codex、Claude

8,823,360126,072只读MIT通过
vercel-composition-patterns

Vercel 组合模式 · Codex、Claude

3,858,81625,893需要联网MIT通过
vercel-react-native-skills

Vercel React native skills 前端 · Codex、Claude

2,468,66425,878只读MIT通过
adapt

adapt 搜索 · Codex、Claude

2,027,04023,125操作浏览器未明确通过
bolder

bolder 分析 · Codex、Claude

2,004,28823,130只读未明确通过
react-optimise

React optimise 前端 · 本页

3,834131需要联网未明确通过

按安装量取同分类前几名;数字来自第三方目录统计,只作热度参考,不代表质量结论。

SKILL.md 原文

React Optimise Best Practices

Application-level performance optimization guide for React applications. Contains 43 rules across 8 categories, prioritized by impact from critical (React Compiler, bundle optimization) to incremental (memory management).

When to Apply

  • Optimizing React application performance or bundle size
  • Adopting or troubleshooting React Compiler v1.0
  • Splitting bundles and configuring code splitting
  • Improving Core Web Vitals (INP, LCP, CLS)
  • Profiling render performance and identifying bottlenecks
  • Fixing memory leaks in long-lived single-page applications
  • Optimizing data fetching patterns and eliminating waterfalls

Rule Categories

CategoryImpactRulesKey Topics
React Compiler MasteryCRITICAL6Compiler-friendly code, bailout detection, incremental adoption
Bundle & LoadingCRITICAL6Route splitting, barrel elimination, dynamic imports, prefetching
Rendering OptimizationHIGH6Virtualization, children pattern, debouncing, CSS containment
Data Fetching PerformanceHIGH5Waterfall elimination, route preloading, SWR, deduplication
Core Web VitalsMEDIUM-HIGH5INP yielding, LCP priority, CLS prevention, image optimization
State & Subscription PerformanceMEDIUM-HIGH5Context splitting, selectors, atomic state, derived state
Profiling & MeasurementMEDIUM5DevTools profiling, flame charts, CI budgets, production builds
Memory ManagementLOW-MEDIUM5Effect cleanup, async cancellation, closure leaks, heap analysis

Quick Reference

Critical patterns — get these right first:

  • Write compiler-friendly components to unlock automatic 2-10x optimization
  • Split code at route boundaries to reduce initial bundle by 40-70%
  • Eliminate barrel files to enable tree shaking
  • Detect and fix silent compiler bailouts

Common mistakes — avoid these anti-patterns:

  • Reading refs during render (breaks compiler optimization)
  • Importing entire libraries when only using one function
  • Not profiling before optimizing (targeting the wrong bottleneck)
  • Missing effect cleanup (subscription memory leaks)

Table of Contents

  1. React Compiler Mastery — CRITICAL

- 1.1 Detect and Fix Silent Compiler Bailouts — CRITICAL (prevents losing automatic memoization) - 1.2 Isolate Side Effects from Render for Compiler Correctness — CRITICAL (prevents compiler from producing incorrect cached output) - 1.3 Remove Manual Memoization After Compiler Adoption — CRITICAL (20-40% code reduction in component files) - 1.4 Use Incremental Compiler Adoption with Directives — CRITICAL (enables safe rollout without full codebase migration) - 1.5 Use Ref Access Patterns That Enable Compilation — CRITICAL (maintains compiler optimization for ref-using components) - 1.6 Write Compiler-Friendly Component Patterns — CRITICAL (2-10x automatic render optimization)

  1. Bundle & Loading — CRITICAL

- 2.1 Configure Dependencies for Effective Tree Shaking — CRITICAL (50-90% dead code elimination in dependencies) - 2.2 Eliminate Barrel Files to Enable Tree Shaking — CRITICAL (200-800ms import cost eliminated) - 2.3 Enforce Bundle Size Budgets with Analysis Tools — CRITICAL (prevents gradual bundle size regression) - 2.4 Prefetch Likely Next Routes on Interaction — CRITICAL (200-1000ms faster perceived navigation) - 2.5 Split Code at Route Boundaries with React.lazy — CRITICAL (40-70% reduction in initial bundle size) - 2.6 Use Dynamic Imports for Heavy Libraries — CRITICAL (100-500KB removed from critical path)

  1. Rendering Optimization — HIGH

- 3.1 Avoid Inline Object Creation in JSX Props — HIGH (prevents unnecessary child re-renders) - 3.2 Debounce Expensive Derived Computations — HIGH (50-200ms saved per keystroke) - 3.3 Use CSS Containment to Isolate Layout Recalculation — HIGH (60-90% layout recalc reduction) - 3.4 Use Children Pattern to Prevent Parent Re-Renders — HIGH (eliminates re-renders of static subtrees) - 3.5 Use Stable Keys for List Rendering Performance — HIGH (O(n) DOM mutations to O(1) moves) - 3.6 Virtualize Long Lists with TanStack Virtual — HIGH (O(n) to O(1) DOM nodes)

  1. Data Fetching Performance — HIGH

- 4.1 Abort Stale Requests on Navigation or Re-fetch — HIGH (prevents stale data display) - 4.2 Deduplicate Identical In-Flight Requests — HIGH (50-80% fewer network requests) - 4.3 Eliminate Sequential Data Fetch Waterfalls — HIGH (2-5x faster page loads) - 4.4 Preload Data at Route Level Before Component Mounts — HIGH (200-1000ms eliminated) - 4.5 Use Stale-While-Revalidate for Cache Freshness — HIGH (0ms perceived load for returning visitors)

  1. Core Web Vitals — MEDIUM-HIGH

- 5.1 Instrument Real User Monitoring with web-vitals — MEDIUM-HIGH (enables data-driven optimization) - 5.2 Optimize Images with Responsive Sizing and Lazy Loading — MEDIUM-HIGH (40-70% bandwidth reduction) - 5.3 Optimize Interaction to Next Paint with Yielding — MEDIUM-HIGH (INP from 500ms+ to under 200ms) - 5.4 Optimize Largest Contentful Paint with Priority Loading — MEDIUM-HIGH (200-1000ms LCP improvement) - 5.5 Prevent Cumulative Layout Shift with Size Reservations — MEDIUM-HIGH (CLS from 0.25+ to under 0.1)

  1. State & Subscription Performance — MEDIUM-HIGH

- 6.1 Derive State Instead of Syncing for Zero Extra Renders — MEDIUM-HIGH (eliminates double-render cycle) - 6.2 Separate Server State from Client State Management — MEDIUM-HIGH (reduces state management code by 40%) - 6.3 Split Contexts to Isolate High-Frequency Updates — MEDIUM-HIGH (5-50x fewer re-renders) - 6.4 Use Atomic State for Independent Reactive Values — MEDIUM-HIGH (3-10x fewer unnecessary re-renders) - 6.5 Use Selector-Based Subscriptions for Granular Updates — MEDIUM-HIGH (reduces re-renders to only affected components)

  1. Profiling & Measurement — MEDIUM

- 7.1 Benchmark with Production Builds Only — MEDIUM (prevents false positives from dev-mode overhead) - 7.2 Enforce Performance Budgets in CI — MEDIUM (catches 90% of perf issues before merge) - 7.3 Profile Before Optimizing to Target Real Bottlenecks — MEDIUM (10x more effective optimization effort) - 7.4 Read Flame Charts to Identify Hot Render Paths — MEDIUM (identifies exact function causing 80% of render time) - 7.5 Use React Performance Tracks for Render Analysis — MEDIUM (pinpoints render bottlenecks in minutes)

  1. Memory Management — LOW-MEDIUM

- 8.1 Avoid Closure-Based Memory Leaks in Event Handlers — LOW-MEDIUM (prevents MB-scale memory retention) - 8.2 Cancel Async Operations on Unmount — LOW-MEDIUM (prevents stale updates and memory retention) - 8.3 Clean Up Effects to Prevent Subscription Memory Leaks — LOW-MEDIUM (prevents linear memory growth) - 8.4 Dispose Heavy Resources in Cleanup Functions — LOW-MEDIUM (prevents 5-50MB per resource retention) - 8.5 Use Heap Snapshots to Detect Component Retention — LOW-MEDIUM (identifies 10-100MB memory growth)

References

  1. https://react.dev
  2. https://react.dev/blog/2025/10/07/react-compiler-1
  3. https://web.dev/articles/vitals
  4. https://tanstack.com/virtual
  5. https://developer.chrome.com/docs/devtools/performance

Related Skills

  • For React 19 API best practices, see react skill
  • For Next.js App Router optimization, see nextjs-16-app-router skill
  • For client-side form handling, see react-hook-form skill

平台分布

Codex

36.48%
按下载量换算490

Claude

27.69%
按下载量换算372

Cursor

19.66%
按下载量换算264

Gemini CLI

10.02%
按下载量换算135

安全审计

Gen Agent Trust Hub

通过

Socket

通过

Snyk

通过

权限和风险

需要联网

该 Skill 可能需要联网访问来源站点、仓库或外部 API;具体网络访问范围需要结合源码和 README 复核。

安装前确认

本站仅展示第三方公开信息,不托管安装包,不提供自动安装或运行环境。安装前应自行审查源码、依赖和命令行为。目前只有一个公开来源,建议同时核对源仓库。

继续浏览同类 Skills