coding-standards

Apply baseline conventions for descriptive naming, immutability via spread operators, and comprehensive error handling. Combine these rules with linting and type-checking configuration so violations surface automatically during review and CI.

Use descriptive names that reveal intent, such as marketSearchQuery instead of q. Functions follow a verb-noun pattern like fetchMarketData or isValidEmail, while booleans use is/has prefixes.

Use it for cross-cutting concerns like naming, immutability, readability, and code smell review. For React composition, hooks architecture, or backend API layering, defer to the narrower frontend-patterns or backend-patterns skills.

Direct mutation breaks change detection, causes stale state in async updates, and makes debugging harder. Always create new objects with the spread operator and use functional state updates like setCount(prev => prev + 1).

Watch for functions longer than 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.