coding-standards

Activate this Skill when reviewing a pull request or refactoring a module. It checks naming conventions, immutability patterns, error handling, and code smells like long functions and deep nesting, providing concrete pass/fail examples for each rule.

It covers descriptive variable and verb-noun function naming, spread-operator immutability, typed interfaces instead of any, parallel async/await with Promise.all, and comprehensive try/catch error handling with meaningful error messages.

Use it for cross-project baseline rules like naming, readability, and code-smell review. For React composition, hooks, backend architecture, or API design details, defer to the narrower frontend-patterns, backend-patterns, or api-design skills it references.

Yes, it includes baseline React guidance: typed functional components, custom hooks like useDebounce, functional state updates, clear conditional rendering, memoization with useMemo and useCallback, and lazy loading with Suspense.

It flags three main anti-patterns with fixes: functions longer than 50 lines (split into smaller functions), nesting beyond five levels (use early returns), and magic numbers (replace with named constants like MAX_RETRIES).