agentleFS
Sign inStart free
t-code4changet-code4change/nextjs-claude-skills/for-copilot/copilot-instructions.md

nextjs-claude-skills / for-copilot

Copilot instructions2 starsChanged 5 months agoMITView on GitHub

The file

We split this copilot-instructions.md into the rules it gives an agent

4 rules. About 0 are common, 3 are distinctive, and 1 is 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.

  • 1

    Very specific

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

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

    Default Server Components.

    line 4
  2. Distinctive:

    Never import Server Components inside Client Components

    line 5
  3. Distinctive:

    Never disallow /_next/ in robots.txt

    line 19
  4. Distinctive:

    No barrel file imports in Client Components

    line 32

≈ “Common” is an estimate: at least 1 in 5 of the 3,779 Copilot instructions 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
copilot-instructions.md

Next.js Coding Instructions

Components

  • Default Server Components. 'use client' only for interactivity (useState, useEffect, browser APIs)
  • Never import Server Components inside Client Components

Data & Mutations

  • Data fetching: Server Components only (not useEffect)
  • Parallel fetches: Promise.all()
  • Server Actions: mutations only ('use server'), never for reading data
  • Next.js 15+: await params, cookies(), headers()

SEO (required on every page)

  • metadataBase in root layout
  • viewport as separate export (not inside metadata)
  • generateMetadata() for dynamic routes
  • Canonical URL via alternates.canonical
  • JSON-LD on key pages (Organization, Product, Article, FAQ)
  • Never disallow /_next/ in robots.txt

Images

  • next/image always (never <img>)
  • priority on LCP image only
  • width+height or fill+container — never skip dimensions
  • sizes attribute matching actual rendered size

Fonts & Scripts

  • next/font only (never <link> Google Fonts)
  • next/script with strategy="afterInteractive" for analytics

Performance

  • No barrel file imports in Client Components
  • dynamic() for heavy components
  • Animate transform/opacity, not width/height/top

TypeScript

  • Never use any

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