nextjs

pproenca/dot-skills · updated Apr 8, 2026

MDX-style export adds YAML metadata + attribution linking explainx.ai and this canonical listing URL.

$npx skills add https://github.com/pproenca/dot-skills --skill nextjs
0 commentsdiscussion
summary

Comprehensive performance optimization guide for Next.js 16 App Router applications, maintained by the Next.js Community. Contains 40 rules across 8 categories, prioritized by impact to guide automated refactoring and code generation.

skill.md

Next.js Community Next.js 16 App Router Best Practices

Comprehensive performance optimization guide for Next.js 16 App Router applications, maintained by the Next.js Community. Contains 40 rules across 8 categories, prioritized by impact to guide automated refactoring and code generation.

When to Apply

Reference these guidelines when:

  • Writing new Next.js 16 App Router code
  • Configuring caching strategies with 'use cache' directive
  • Implementing server components and data fetching
  • Setting up routing with parallel and intercepting routes
  • Creating server actions for form handling and mutations

Rule Categories by Priority

Priority Category Impact Prefix
1 Build & Bundle Optimization CRITICAL build-
2 Caching Strategy CRITICAL cache-
3 Server Components & Data Fetching HIGH server-
4 Routing & Navigation HIGH route-
5 Server Actions & Mutations MEDIUM-HIGH action-
6 Streaming & Loading States MEDIUM stream-
7 Metadata & SEO MEDIUM meta-
8 Client Components LOW-MEDIUM client-

Quick Reference

1. Build & Bundle Optimization (CRITICAL)

  • build-optimize-package-imports - Configure optimizePackageImports for Icon Libraries
  • build-dynamic-imports - Use Dynamic Imports for Heavy Components
  • build-barrel-files - Avoid Barrel File Imports in App Router
  • build-turbopack-config - Enable Turbopack File System Caching
  • build-external-packages - Configure Server External Packages for Node Dependencies

2. Caching Strategy (CRITICAL)

  • cache-use-cache-directive - Use the 'use cache' Directive for Explicit Caching
  • cache-revalidate-tag - Use revalidateTag with cacheLife Profiles
  • cache-fetch-options - Configure Fetch Cache Options Correctly
  • cache-revalidate-path - Use revalidatePath for Route-Level Cache Invalidation
  • cache-react-cache - Use React cache() for Request Deduplication
  • cache-segment-config - Configure Route Segment Caching with Exports

3. Server Components & Data Fetching (HIGH)

  • server-parallel-fetching - Fetch Data in Parallel in Server Components
  • server-component-streaming - Stream Server Components for Progressive Loading
  • server-data-colocation - Colocate Data Fetching with Components
  • server-preload-pattern - Use Preload Pattern for Critical Data
  • server-avoid-client-fetching - Avoid Client-Side Data Fetching for Initial Data
  • server-error-handling - Handle Server Component Errors Gracefully

4. Routing & Navigation (HIGH)

  • route-parallel-routes - Use Parallel Routes for Independent Content
  • route-intercepting-routes - Use Intercepting Routes for Modal Patterns
  • route-prefetching - Configure Link Prefetching Appropriately
  • route-proxy-ts - Use proxy.ts for Network Boundary Logic
  • route-not-found - Use notFound() for Missing Resources

5. Server Actions & Mutations (MEDIUM-HIGH)

  • action-server-action-forms - Use Server Actions for Form Submissions
  • action-pending-states - Show Pending States with useFormStatus
  • action-error-handling - Handle Server Action Errors Gracefully
  • action-optimistic-updates - Use Optimistic Updates for Instant Feedback
  • action-revalidation - Revalidate Cache After Mutations

6. Streaming & Loading States (MEDIUM)

  • stream-suspense-boundaries - Place Suspense Boundaries Strategically
  • stream-loading-tsx - Use loading.tsx for Route-Level Loading States
  • stream-error-tsx - Use error.tsx for Route-Level Error Boundaries
  • stream-skeleton-matching - Match Skeleton Dimensions to Actual Content
  • stream-nested-suspense - Nest Suspense for Progressive Disclosure

7. Metadata & SEO (MEDIUM)

  • meta-generate-metadata - Use generateMetadata for Dynamic Metadata
  • meta-sitemap - Generate Sitemaps Dynamically
  • meta-robots - Configure Robots for Crawl Control
  • meta-opengraph-images - Generate Dynamic OpenGraph Images

8. Client Components (LOW-MEDIUM)

  • client-use-client-boundary - Minimize 'use client' Boundary Scope
  • client-children-pattern - Pass Server Components as Children to Client Components
  • client-hydration-mismatch - Avoid Hydration Mismatches
  • client-third-party-scripts - Load Third-Party Scripts Efficiently

How to Use

Read individual reference files for detailed explanations and code examples:

Related Skills

  • For React 19 fundamentals, see react-19 skill
  • For data fetching patterns, see tanstack-query skill
  • For client-side forms, see react-hook-form skill

Full Compiled Document

For the complete guide with all rules expanded: AGENTS.md

how to use nextjs

How to use nextjs on Cursor

AI-first code editor with Composer

1

Prerequisites

Before installing skills in Cursor, ensure your development environment meets these requirements:

  • Cursor installed and configured on your development machine
  • Node.js version 16.0+ with npm package manager (verify with node --version)
  • Active project directory or workspace where you want to add nextjs
2

Execute installation command

Execute the skills CLI command in your project's root directory to begin installation:

$npx skills add https://github.com/pproenca/dot-skills --skill nextjs

The skills CLI fetches nextjs from GitHub repository pproenca/dot-skills and configures it for Cursor.

3

Select Cursor when prompted

The CLI will show a list of available agents. Use arrow keys to navigate and space to select Cursor:

◆ Which agents do you want to install to?
│ ── Universal (.agents/skills) ── always included ────
│ • Amp
│ • Antigravity
│ • Cline
│ • Codex
│ ●Cursor(selected)
│ • Cursor
│ • Windsurf
4

Verify installation

Confirm successful installation by checking the skill directory location:

.cursor/skills/nextjs

Reload or restart Cursor to activate nextjs. Access the skill through slash commands (e.g., /nextjs) or your agent's skill management interface.

Security & Verification Notice

We perform automated surface-level scans (Gen AI Scanner, Socket, Snyk) during installation. These checks detect common vulnerabilities but do not guarantee complete security. Always review skill source code and verify the publisher's reputation before production use.

Skills execute code in your development environment. Always verify the publisher's identity, review recent commits, and test in isolated environments before production deployment.

List & Monetize Your Skill

Submit your Claude Code skill and start earning

GET_STARTED →

Use Cases

Task Automation & Efficiency

Automate repetitive workflows and reduce manual effort

Example

Generate reports, summarize documents, draft communications

Save 3-5 hours per week on routine tasks

Knowledge Enhancement

Learn new skills, understand complex topics, get expert guidance

Example

Explain concepts, provide examples, suggest learning resources

Accelerate learning and skill development by 2x

Quality Improvement

Enhance output quality through reviews, suggestions, and refinements

Example

Review drafts, suggest improvements, catch errors

Improve work quality by 30-40% with less effort

Implementation Guide

Prerequisites

  • Claude Desktop or compatible AI client with skill support
  • Clear understanding of task or problem to solve
  • Willingness to iterate and refine outputs

Time Estimate

15-45 minutes depending on use case complexity

Installation Steps

  1. 1.Install skill using provided installation command
  2. 2.Test with simple use case relevant to your work
  3. 3.Evaluate output quality and relevance
  4. 4.Iterate on prompts to improve results
  5. 5.Integrate into regular workflow if valuable

Common Pitfalls

  • Expecting perfect results without iteration
  • Not providing enough context in prompts
  • Using skill for tasks outside its intended scope
  • Accepting outputs without review and validation

Best Practices

✓ Do

  • +Start with clear, specific prompts
  • +Provide relevant context and constraints
  • +Review and refine all outputs before using
  • +Iterate to improve output quality
  • +Document successful prompt patterns

✗ Don't

  • Don't use without understanding skill limitations
  • Don't skip validation of outputs
  • Don't share sensitive information in prompts
  • Don't expect skill to replace human judgment

💡 Pro Tips

  • Be specific about desired format and style
  • Ask for multiple options to choose from
  • Request explanations to understand reasoning
  • Combine AI efficiency with human expertise

When to Use This

✓ Use When

Use when skill capabilities match your task, clear ROI on time saved, and you can validate outputs. Best for repetitive tasks, learning, and quality improvement.

✗ Avoid When

Avoid when task requires deep expertise you can't validate, involves sensitive decisions, or when learning process is more valuable than speed of completion.

Learning Path

  1. 1Familiarize yourself with skill capabilities and limitations
  2. 2Start with low-risk, non-critical tasks
  3. 3Progress to more complex and valuable use cases
  4. 4Build expertise through regular use and experimentation

Discussion

Product Hunt–style comments (not star reviews)
  • No comments yet — start the thread.
general reviews

Ratings

4.548 reviews
  • Chinedu Shah· Dec 24, 2024

    I recommend nextjs for anyone iterating fast on agent tooling; clear intent and a small, reviewable surface area.

  • Advait Abbas· Dec 16, 2024

    nextjs fits our agent workflows well — practical, well scoped, and easy to wire into existing repos.

  • Daniel Torres· Dec 16, 2024

    Registry listing for nextjs matched our evaluation — installs cleanly and behaves as described in the markdown.

  • Dhruvi Jain· Dec 12, 2024

    nextjs has been reliable in day-to-day use. Documentation quality is above average for community skills.

  • Yusuf Martinez· Dec 8, 2024

    Useful defaults in nextjs — fewer surprises than typical one-off scripts, and it plays nicely with `npx skills` flows.

  • Valentina Kapoor· Nov 27, 2024

    We added nextjs from the explainx registry; install was straightforward and the SKILL.md answered most questions upfront.

  • Li Agarwal· Nov 15, 2024

    Keeps context tight: nextjs is the kind of skill you can hand to a new teammate without a long onboarding doc.

  • Daniel Diallo· Nov 7, 2024

    nextjs reduced setup friction for our internal harness; good balance of opinion and flexibility.

  • Oshnikdeep· Nov 3, 2024

    Solid pick for teams standardizing on skills: nextjs is focused, and the summary matches what you get after install.

  • Mei Khanna· Nov 3, 2024

    nextjs is among the better-maintained entries we tried; worth keeping pinned for repeat workflows.

showing 1-10 of 48

1 / 5