agentleFS
MindrallyMindrally/skills/nextjs-react-typescript/SKILL.md

nextjs-react-typescript

Skill275 starsChanged 34 days agoApache-2.0View on GitHub

Expert in TypeScript, Node.js, Next.js App Router, React, Shadcn UI, Radix UI and Tailwind

4 other projects use a version of this, 4 of them edited.

Adopted by

Most recently taken up by

The file

We split this skill into the rules it gives an agent

11 rules. 10 are common, 0 are distinctive, and 1 is very specific to this project.

  • 10

    Common

    Most of the 4 edited versions we read keep these.

  • 0

    Distinctive

    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. Common:

    Write concise, technical TypeScript code with accurate examples

    line 15
  2. Common:

    Use descriptive variable names with auxiliary verbs (e.g., isLoading, hasError)

    line 18
  3. Common:

    Use lowercase with dashes for directories (e.g., components/auth-wizard)

    line 23
  4. Common:

    Use TypeScript for all code.

    line 28
  5. Common:

    Avoid enums; use maps instead

    line 29
  6. Common:

    Use functional components with TypeScript interfaces

    line 30
  7. Common:

    Use the "function" keyword for pure functions

    line 34
  8. Common:

    Avoid unnecessary curly braces in conditionals

    line 35
  9. Common:

    Use dynamic loading for non-critical components

    line 47
  10. Common:

    Use 'nuqs' for URL search parameter state management

    line 52
  11. Very specific:

    Follow Next.js documentation for Data Fetching, Rendering, and Routing

    line 55

“Common” is measured: kept by at least 6 in 10 of the 4 edited versions of this file we could read. “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

Next.js React TypeScript

You are an expert in TypeScript, Node.js, Next.js App Router, React, Shadcn UI, Radix UI and Tailwind.

Code Style and Structure

  • Write concise, technical TypeScript code with accurate examples
  • Employ functional and declarative programming patterns; steer clear of classes
  • Prioritize iteration and modularization over code duplication
  • Use descriptive variable names with auxiliary verbs (e.g., isLoading, hasError)
  • Organize files: exported component, subcomponents, helpers, static content, types

Naming Conventions

  • Use lowercase with dashes for directories (e.g., components/auth-wizard)
  • Favor named exports for components

TypeScript Usage

  • Use TypeScript for all code; prefer interfaces over types
  • Avoid enums; use maps instead
  • Use functional components with TypeScript interfaces

Syntax and Formatting

  • Use the "function" keyword for pure functions
  • Avoid unnecessary curly braces in conditionals
  • Use declarative JSX

UI and Styling

  • Leverage Shadcn UI, Radix, and Tailwind for components and styling
  • Implement responsive design with Tailwind CSS using a mobile-first approach

Performance Optimization

  • Minimize 'use client', 'useEffect', and 'setState'; favor React Server Components
  • Wrap client components in Suspense with fallback
  • Use dynamic loading for non-critical components
  • Optimize images: use WebP format, include size data, implement lazy loading

Key Conventions

  • Use 'nuqs' for URL search parameter state management
  • Optimize Web Vitals (LCP, CLS, FID)
  • Limit 'use client' to Web API access in small components; avoid for data fetching or state management
  • Follow Next.js documentation for Data Fetching, Rendering, and Routing

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.