Menü
React performance for AFENDA-HYBRID: runtime rendering (re-renders, keys, virtualization) and build-time delivery (bundles, tree-shaking, code splitting, compiler directives). Use when fixing slow lists, grids, or large client bundles.
Accessibility for React UIs in AFENDA-HYBRID: semantic HTML, ARIA, keyboard support, focus management, and testing. Use for grids, dialogs, bulk selection, notifications, and command surfaces.
React and Next.js App Router architecture for AFENDA-HYBRID: Server vs Client Components, composition, state placement, package layering (ui-core → view-engine → erp-view-pack → apps/web). Use when designing components, fixing import/layer violations, or RSC boundaries.
Implementation patterns for AFENDA-HYBRID React code: custom hooks, compound components, error boundaries / error.tsx, forms, server actions, and optimistic updates.
Meta-skill: React Quality Orchestrator for AFENDA-HYBRID. Coordinates architecture, performance, accessibility, and design-pattern skills for audits, scoring (Component Quality Index), and confidence-tiered refactors. Use for full-route reviews, legacy refactors, and governance checks.
Official Storybook AI workflow — MCP server, manifests, MCP toolsets (development, docs, testing), and documentation best practices. Use when writing or fixing stories, connecting agents to Storybook, using design-system components without guessing props, or running Storybook tests from an agent. Sources are linked inline.
Vitest (Vite-powered) testing — Jest-compatible API, vi mocks, coverage, environments, projects/workspaces. Use when writing or fixing tests, vitest.config.ts, coverage, or monorepo test commands in AFENDA-HYBRID (@afenda/db, @afenda/ui-core, view-engine, erp-view-pack). Prefer https://vitest.dev for Vitest 4.x when reference snippets disagree.
| name | react-performance |
| description | React performance for AFENDA-HYBRID: runtime rendering (re-renders, keys, virtualization) and build-time delivery (bundles, tree-shaking, code splitting, compiler directives). Use when fixing slow lists, grids, or large client bundles. |
| metadata | {"author":"AFENDA team","version":"2026.03.23","source":"React docs + AFENDA-HYBRID codebase analysis","official_docs":"https://react.dev"} |
Performance work splits into two domains. Diagnose which domain applies before changing code.
useMemo/useCallbackimport(), route-level splitting, dependency audits"use memo" / "use no memo" only when justified (document why)Provenance: see GENERATION.md.
Version alignment: React 19; confirm compiler and Next bundler behavior against current project config.
| Domain | Topic | Reference |
|---|---|---|
| Runtime | Re-renders, keys, splitting | rendering-optimization |
| Build-time | Compiler modes and directives | compiler-directives |
| Build-time | Bundles, imports, barrels | bundle-analysis |
| Runtime | Virtualized lists/grids | virtualization |
This skill does not:
@afenda/db)| Area | Enforce |
|---|---|
| ui-core | Primitives stay lean; avoid heavy optional deps in hot paths; document virtualization helpers if added |
| view-engine | List/kanban renderers: prefer virtualization for large datasets; stable row keys |
| erp-view-pack | Selection and bulk UIs: minimize re-renders on selection changes (narrow subscriptions) |
| apps/web | Route-level code splitting; defer heavy client-only modules behind dynamic where appropriate |