coding-standards

Apply a shared baseline of conventions covering naming, immutability, error handling, and file organization, then check code against it during reviews. This Skill provides that baseline with concrete good and bad examples for TypeScript and React.

Always use the spread operator to create updated copies of objects and arrays instead of mutating them directly. For example, use `{ ...user, name: 'New Name' }` rather than assigning `user.name` in place.

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

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

It includes baseline REST conventions, consistent response envelopes, and Zod-based input validation examples. Deeper endpoint architecture and service-layer design are delegated to dedicated backend or API design skills.