coding-standards

Apply naming conventions like verb-noun function names and descriptive variables, organize files by feature directories, and run prettier --check after every change. Use the provided good/bad code examples as review criteria.

Define a typed props interface, use functional components with destructured props and default values, and memoize expensive computations with useMemo and callbacks with useCallback. Avoid untyped props and nested ternary rendering.

Use npx -w <workspace-name> prettier --check . to target a specific workspace. First check package.json for a format:check script, then fall back to npx prettier --check . in the project root.

Watch for functions over 50 lines, nesting deeper than a few levels, and unexplained magic numbers. Fix them by splitting functions, using early returns, and replacing literals with named constants like MAX_RETRIES.

Comment only to explain why, not what the code does, such as documenting a deliberate performance tradeoff. Use JSDoc with param, returns, and example tags for public APIs, and skip comments that restate obvious operations.