Nextjs React Typescript

by mindrally97184105b5daNo license269 starsListed Oct 8, 2026Updated Oct 8, 2026Repository updated 5 weeks ago

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

Instructions onlySoftware Development
AI-generated overview

Coding conventions for building Next.js App Router apps with TypeScript, React, Shadcn UI, Radix UI and Tailwind.

What it does
Provides a set of coding standards and conventions for TypeScript, Node.js, Next.js App Router and React work. It covers code style and file structure, naming, TypeScript usage, syntax and formatting, UI and styling with Shadcn UI, Radix and Tailwind, performance optimization, and key Next.js conventions. It produces guidance rather than files or scripts.
When to use it
Use it when writing or reviewing Next.js App Router and React code in TypeScript. It is suited to projects using Shadcn UI, Radix UI and Tailwind CSS that want consistent structure, naming and performance practices.
Requirements
No tools, packages or credentials are required; it is instructions only and ships no scripts.

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

Source and attribution

Source:mindrally/skillsinnextjs-react-typescriptat commit9718410

License: No license

Content belongs to its original authors. SourceWeft indexes it from a public repository.

Report or request removal