coding-standards

Apply a shared baseline of conventions covering descriptive naming, immutability via spread operators, typed interfaces instead of any, and structured error handling. Pair the conventions with linting and type-checking rules so violations surface during review.

Use descriptive names that reveal intent, such as marketSearchQuery instead of q. Functions should follow a verb-noun pattern like fetchMarketData or calculateSimilarity, and booleans should read as predicates like isUserAuthenticated.

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

Direct mutation like items.push or user.name = value breaks React's change detection and can cause stale renders. Always create new objects or arrays with the spread operator so state updates trigger reliable re-renders.

Replace nested conditionals with early returns that guard each precondition, and split functions over roughly 50 lines into smaller single-purpose helpers. Replace magic numbers with named constants like MAX_RETRIES to clarify intent.