Przejdź do treści
Biblioteka skilli
Programowanie · Nauka i wyjaśnianie

nextjs-react-expert

/nextjs-react-expert

Podaje zasady wydajności React i Next.js od największego wpływu: wodospady zapytań, paczki, ponowne renderowanie i cache.

Repozytorium
redevkit ↗
Licencja
MIT
Ostatnia zmiana repozytorium
12.11.2026

Ocena i bezpieczeństwo

100/ 100Klasa: dobry
Format25 / 25
Frontmatter z nazwą i opisem, poprawna nazwa, opis do 1024 znaków, nazwa zgodna z folderem.
Odkrywalność25 / 25
Opis mówi, kiedy użyć skilla, ma sensowną długość i jest w 3. osobie.
Treść35 / 35
Co najmniej 150 słów i do 500 linii, nagłówki, listy kroków, przykłady albo kod.
Higiena15 / 15
Bez zaślepek typu TODO, bez ścieżek Windows, z licencją.
Ryzykobrak sygnałów w skanie
Pliki w paczce
10
Skrypty
0
Komentarze HTML
0
Adresy URL w SKILL.md
0
Przestarzałość

Brak sygnałów. Repozytorium zmienione 12.11.2026, bez odwołań do wycofanych modeli i API.

Licencja

MIT, otwarta: można używać i zmieniać, z zachowaniem informacji o autorze.

Co robi i kiedy

Podaje zasady wydajności React i Next.js od największego wpływu: wodospady zapytań, paczki, ponowne renderowanie i cache.

Oryginalny opis (EN)

React and Next.js performance rules by impact (waterfalls, bundles, re-renders, caching); use when writing React code.

Jak działa

  1. Selective Reading Rule
  2. Content Map
  3. Quick Decision Tree
  4. Impact Priority (comprehensive optimization)
  5. Automated Check
  6. Performance Review Checklist
  7. Anti-Patterns
  8. How to Use This Skill
  9. Related Skills
Sekcje z nagłówków SKILL.md, w oryginale · 121 linii, 781 słów
Podgląd SKILL.md
---
name: nextjs-react-expert
description: React and Next.js performance rules by impact (waterfalls, bundles, re-renders, caching); use when writing React code.
paths: "**/*.jsx, **/*.tsx, **/next.config.*, **/app/**/*.ts, **/pages/**/*.ts"
---

# Next.js & React Performance Expert

> Based on Vercel Engineering's React best practices (Next.js 16 / React 19 era), prioritized
> by impact, plus Next.js 16 Cache Components.
> **Philosophy:** eliminate waterfalls first, optimize bundles second, then micro-optimize.

## Selective Reading Rule

Read **only** the sections relevant to the task. For performance reviews, start with the
CRITICAL sections (1-2), then move to HIGH and MEDIUM.

## Content Map

| Section | Impact | When to read |
| --- | --- | --- |
| [1-async-eliminating-waterfalls](references/1-async-eliminating-waterfalls.md) | 🔴 CRITICAL | Slow page loads, sequential API calls, data-fetching waterfalls |
| [2-bundle-bundle-size-optimization](references/2-bundle-bundle-size-optimization.md) | 🔴 CRITICAL | Large bundles, slow Time to Interactive, First Load issues |
| [3-server-server-side-performance](references/3-server-server-side-performance.md) | 🟠 HIGH | Slow SSR, API route optimization, server-side waterfalls |
| [4-client-client-side-data-fetching](references/4-client-client-side-data-fetching.md) | 🟡 MEDIUM-HIGH | Client data management, SWR patterns, deduplication |
| [5-rerender-re-render-optimization](references/5-rerender-re-render-optimization.md) | 🟡 MEDIUM | Excessive re-renders, memoization |
| [6-rendering-rendering-performance](references/6-rendering-rendering-performance.md) | 🟡 MEDIUM | Rendering bottlenecks, virtualization, images |
| [7-js-javascript-performance](references/7-js-javascript-performance.md) | ⚪ LOW-MEDIUM | Micro-optimizations, caching, hot loops |
| [8-advanced-advanced-patterns](references/8-advanced-advanced-patterns.md) | 🔵 VARIABLE | `useLatest`, init-once, event handler refs |
| [9-cache-components](references/9-cache-components.md) | 🔴 CRITICAL (Next.js 16+ only) | `use cache`, `cacheLife`, `cacheTag`, Partial Prerendering |

## Quick Decision Tree

```text
Slow page loads / long Time to Interactive  → sections 1, 2
Bundle over budget (see checklist)           → section 2 (dynamic imports, barrel imports)
Slow server-side rendering                   → section 3 (parallel fetching, streaming)
Too many re-renders / UI lag                 → section 5 (memo, useMemo, useCallback)
Rendering bottlenecks                        → section 6 (virtualization, layout thrashing)
Client-side data fetching problems           → section 4 (SWR deduplication)
Advanced patterns                            → section 8
Next.js 16+ caching and PPR                  → section 9
```

## Impact Priority (comprehensive optimization)

1. **CRITICAL:** waterfalls (each one adds a full network round trip), bundle size (affects
   TTI and LCP), and Cache Components on Next.js 16+.
2. **HIGH:** server-side performance.
3. **MEDIUM:** client data fetching, re-renders, rendering.
4. **LOW:** JavaScript micro-optimizations, advanced patterns.

## Automated Check

In the verify command's audit step (not during implementation), when its orchestrator did not already run it, run `.redevkit/audits/react_performance_checker.py <project_path>` with the Python interpreter
detected per `.redevkit/audits/README.md` (`--fail-on-warnings` makes advisory warnings
blocking). Without Python, record `SKIPPED (no Python)` and review sections 1-2 by hand plus
the framework's build output (`next build` prints route sizes). Bundle and Lighthouse audits
are in `{{SKILL:performance-profiling}}`.

## Performance Review Checklist

**Critical (must fix):**

- [ ] No sequential data fetching for independent requests
- [ ] Bundle within budget: the one in `plan.md` or `DESIGN.md` when set; otherwise the
  `bundle_analyzer.py` defaults (per file: warn above 250 KiB, fail above 750 KiB; total
  JavaScript: fail above 2048 KiB)
- [ ] No barrel imports in app code
- [ ] Dynamic imports for large components
- [ ] Parallel data fetching where possible

**High:**

- [ ] Server Components used where appropriate
- [ ] API routes optimized (no N+1 queries)
- [ ] Suspense boundaries around data fetching
- [ ] Static generation or caching where possible

**Medium:**

- [ ] Expensive computations memoized
- [ ] Long lists virtualized (> 100 items)
- [ ] Images through `next/image`
- [ ] No unnecessary re-renders

**Low (polish):**

- [ ] Hot-path loops optimized
- [ ] RegExp literals hoisted
- [ ] Property access cached in loops

## Anti-Patterns

| ❌ Don't | ✅ Do |
| --- | --- |
| Sequential `await` for independent work | `Promise.all()` |
| Import a whole library for one function | Import the specific module |
| Barrel re-exports (`index.ts`) in app code | Direct imports |
| Load large components eagerly | `dynamic(() => import('./Heavy'))` |
| Fetch in `useEffect` without deduplication | SWR / React Query or server fetching |
| Client Components where Server Components work | Server Components by default |
| Optimize without measuring | React DevTools Profiler, Chrome DevTools first |

## How to Use This Skill

- **New features:** apply sections 1-2 while building, Server Components by default
  (section 3), memoize only expensive work (section 5).
- **Performance reviews:** section 1, then 2, then 3, then the rest as needed.
- **Slow page reported:** identify the symptom, use the decision tree, read that section,
  measure before and after.

## Related Skills

| Need | Skill |
| --- | --- |
| API design | `{{SKILL:api-patterns}}` |
| Database optimization | `{{SKILL:database-design}}` |
| Tests | `{{SKILL:testing-patterns}}` |
| UI/UX principles | `{{SKILL:frontend-design}}` |
| Styling with Tailwind | `{{SKILL:tailwind-patterns}}` |
| Deployment | `{{SKILL:deployment-procedures}}` |

> **Remember:** every sequential `await` is a potential waterfall, every `import` potential
> bundle bloat, every unnecessary re-render wasted work. Measure, don't guess.
Pliki w paczce (10)
  • SKILL.md 6 KB
  • references/1-async-eliminating-waterfalls.md 9 KB
  • references/2-bundle-bundle-size-optimization.md 6 KB
  • references/3-server-server-side-performance.md 13 KB
  • references/4-client-client-side-data-fetching.md 7 KB
  • references/5-rerender-re-render-optimization.md 15 KB
  • references/6-rendering-rendering-performance.md 10 KB
  • references/7-js-javascript-performance.md 17 KB
  • references/8-advanced-advanced-patterns.md 4 KB
  • references/9-cache-components.md 3 KB

Wersje

RepozytoriumWynikLicencja
Ta strona · Reprograme/redevkit100MIT
vudovn/antigravity-kit100MIT
frankxai/claude-skills-library90MIT

Migawka bazy z 13.11.2026 · wersja paczki 5528658fbf64 (skrót SHA-256 całej paczki)

Pobrania w ostatnich 30 dniach: 0 · ranking

Zgłoś problem z tym skillem: szkodliwa treść, błędny opis albo prośba autora o usunięcie.

Podobne skille

  • 100react-best-practices
    Podpowiada zasady wydajności React i Next.js: wodospady, rozmiar bundla, renderowanie po stronie serwera i rerendery.
  • 90react-best-practices
    Podpowiada reguły wydajności React i Next.js od Vercel, od najważniejszych: wodospady danych, bundle i zbędne renderowania.
  • 100react-performance
    Audytuje wydajność React i Next.js: wodospady zapytań, rozmiar bundle, memoizację, wirtualizację list i wskaźniki Core Web Vitals.
  • 100react-performance
    Podpowiada reguły wydajności dla aplikacji React i Next.js, od kaskad asynchronicznych po rozmiar bundla i re-rendery.
  • 100nextjs-app-router-expert
    Wspiera pracę z architekturą Next.js 14 i 15 z App Router: React Server Components, Server Actions, wzorce routingu, pobieranie danych, cache, streaming i optymalizacja wdrożenia.
  • 100react-best-practices
    Usuwa wodospady zapytań, zmniejsza bundle i ogranicza zbędne re-rendery w kodzie React i Next.js, także w Server Components.

Uwagi i zgłoszenia

Wiadomość trafi do Bartosza Sokolińskiego. Adres e-mail jest potrzebny tylko do odpowiedzi. Szczegóły w polityce prywatności.