coding-standards

Apply consistent rules for naming, immutability, error handling, and type safety across all files. Use descriptive verb-noun function names, spread operators instead of mutation, try-catch around async calls, and explicit interfaces instead of the any type.

Write functional components with typed props interfaces and default parameter values. Extract reusable logic into custom hooks like useDebounce, use functional state updates to avoid stale closures, and memoize expensive computations with useMemo and useCallback.

Define a Zod schema describing the expected shape, then parse the request body inside the route handler. Return a 400 response with a consistent error structure containing success, error, and validation details when parsing fails.

The core principles like KISS, DRY, YAGNI, immutability, and error handling apply to any JavaScript or TypeScript project. React hooks, Next.js App Router structure, and Supabase query examples are framework-specific sections.

Watch for functions longer than 50 lines, nesting deeper than a few levels, and unexplained magic numbers. Fix them by splitting logic into smaller functions, using early returns to flatten conditionals, and replacing literals with named constants.