nextjs-v16
Next.js v16 Skills
This skill covers best practices and patterns for developing with Next.js version 16, focusing on cache components, server-side rendering, and robust error handling.
Cache Components
Purpose
Implement efficient caching strategies to optimize performance and reduce server load using Next.js 16's cache components feature.
Key Concepts
-
"use cache" Directive
- Mark functions as cacheable to enable automatic memoization
- Applied at the function level in server components
- Revalidates based on
cacheLife()configuration - Use for data fetching and computationally expensive operations
More from violabg/dev-recruit
nextjs-performance-architecture
A comprehensive guide to Next.js performance patterns, combining Data Fetching Colocation, the Donut Pattern, and the 'use cache' directive for optimal application architecture.
5shadcn
Manages shadcn components and projects — adding, searching, fixing, debugging, styling, and composing UI. Provides project context, component docs, and usage examples. Applies when working with shadcn/ui, component registries, presets, --preset codes, or any project with a components.json file. Also triggers for "shadcn init", "create an app with --preset", or "switch to --preset".
5ai-integration
Integrating AI and LLM capabilities into applications for enhanced functionalities. Use when implementing AI features, processing data with ML models, building generative workflows, or integrating AI APIs.
5prisma
Database management with Prisma ORM including schema modeling, migrations, and query optimization. Use when working with database schemas, managing data models, running migrations, or optimizing database queries.
5general-development
General software development practices including code review, testing strategies, and CI/CD integration. Use when implementing features, writing tests, setting up deployment pipelines, or conducting peer reviews.
4architecture
Architectural decision-making framework. Requirements analysis, trade-off evaluation, ADR documentation. Use when making architecture decisions or analyzing system design.
3