best▌

PrimeNG rules for component imports, table performance, and theming. Use with the core angular-best-practices skill for comprehensive Angular coverage.

$23

Validate .NET/C# code against comprehensive best practices for your solution and project. \n \n Covers 10+ practice areas including XML documentation, design patterns, dependency injection, async/await, testing standards, and error handling \n Enforces specific patterns: primary constructors for DI, Command Handler pattern with generics, interface segregation, and Factory pattern for object creation \n Includes resource management with ResourceManager for localization, structured logging via Mic

React patterns for hooks, effects, refs, and component design with escape hatch guidance. \n \n Effects synchronize with external systems only (WebSocket, third-party libraries, browser APIs); most component logic should avoid Effects entirely \n Common anti-patterns: derived state, expensive calculations, prop-change resets, and event handling all belong outside Effects—use render calculations, useMemo, key props, and event handlers instead \n Effect dependencies must never be suppressed; use u

Comprehensive Next.js development guidelines covering file structure, RSC patterns, data fetching, optimization, and error handling. \n \n Covers 15+ topic areas including file conventions, route segments, RSC boundaries, async patterns, metadata generation, and image/font optimization \n Provides runtime selection guidance, directive usage, and error handling strategies with specific file conventions like error.tsx and not-found.tsx \n Includes data fetching patterns, route handler best practic

Principles and decision-making for Node.js development in 2025. Learn to THINK, not memorize code patterns.

Guide AI agents in building secure, production-ready Electron applications with React. This skill provides security patterns, type-safe IPC communication, project setup guidance, packaging and code signing workflows, and tools for analysis, scaffolding, and type generation.

23 performance optimization rules for React and Vite across build, code splitting, development, assets, environment, and bundle analysis. \n \n Covers six rule categories prioritized by impact: build optimization and code splitting (critical), development and asset handling (high), environment config and bundle analysis (medium) \n Includes route-based lazy loading with React.lazy() and Suspense, manual vendor chunk separation, and strategic prefetching patterns \n Provides recommended vite.conf

Comprehensive performance optimization guide for React and Next.js applications, maintained by Vercel. Contains 45 rules across 8 categories, prioritized by impact to guide automated refactoring and code generation.

Server Components by default, client interactivity on demand, with structured data fetching and caching strategies. \n \n Server Components handle data fetching and static content; Client Components ('use client') manage forms, state, and event handlers. Split responsibilities when both are needed. \n Data fetching uses static caching by default, with ISR (time-based revalidation) and dynamic (no-store) options for different freshness requirements. \n Routing relies on file conventions (page.tsx