agentleFS
Sign inStart free
salmandevsalmandev/everything-gemini/skills/fullstack-nextjs/SKILL.md

fullstack-nextjs

Skill2 starsChanged 28 days agoApache-2.0View on GitHub

Specialized engineering workflow for Next.js App Router, React Server Components (RSC), Server Actions, and API routes. Use when building or debugging modern Next.js applications.

The file

We split this skill into the rules it gives an agent

6 rules. About 0 are common, 3 are distinctive, and 3 are very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈3

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 3

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Very specific:

    'use client' Boundary: Only mark components with 'use client' when they require browser event listeners (onClick, onChange), React state …

    line 15
  2. Distinctive:

    Push Client Boundaries Down: Keep client components at the leaves of the component tree to maximize server-side rendering performance.

    line 16
  3. Very specific:

    Use 'use server' functions for mutations.

    line 19
  4. Distinctive:

    Always validate input arguments using Zod schemas inside Server Actions before performing database queries.

    line 20
  5. Very specific:

    Avoid accessing window, localStorage, or navigator during initial render.

    line 24
  6. Distinctive:

    Ensure identical HTML output between SSR and hydration (e.g.

    line 25

≈ “Common” is an estimate: at least 1 in 5 of the 350,495 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

Fullstack Next.js Engineering

This skill provides patterns for Next.js (App Router), React Server Components (RSC), and Server Actions.

Core Directives

1. Server vs. Client Components

  • Default to Server Components: Fetch data directly on the server without useEffect or client-side fetch.
  • 'use client' Boundary: Only mark components with 'use client' when they require browser event listeners (onClick, onChange), React state (useState, useReducer), or browser APIs.
  • Push Client Boundaries Down: Keep client components at the leaves of the component tree to maximize server-side rendering performance.

2. Server Actions & Mutations

  • Use 'use server' functions for mutations.
  • Always validate input arguments using Zod schemas inside Server Actions before performing database queries.
  • Revalidate cache paths using revalidatePath() or revalidateTag() after data mutations.

3. Hydration Bug Prevention

  • Avoid accessing window, localStorage, or navigator during initial render.
  • Ensure identical HTML output between SSR and hydration (e.g. avoid rendering random IDs or localized date strings on initial render without a client wrapper).

For architectural layouts and route handler patterns, see references/app-router-patterns.md.

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

Check your setup, free