coding-standards

You can enforce coding standards by applying unified naming, formatting, and architectural guidelines. This skill provides concrete rules for TypeScript and React projects, prescribing specific conventions for component organization, variable naming, and immutability to improve maintainability.

Best practices for error handling and testing in Node.js include adopting strict conventions to reduce defects and improve reliability. This skill establishes universal rules for immutability, error handling, and testing standards to guide your Node.js application architecture and ensure consistent code quality.

Yes, these coding standards are applicable to JavaScript and Node.js projects. They are designed to be universal across modern web applications, guiding architectural decisions, code smells detection, and documentation practices for both frontend and backend development.

To audit your current project, review your codebase against established naming, formatting, and architectural guidelines. This skill helps you identify code smells, verify immutability rules, and implement a shared linting and formatting workflow to streamline team collaboration.

Code drift happens when teams lack unified coding standards, leading to inconsistent styles and brittle patterns. You can prevent it by establishing universal rules for documentation, component organization, and architectural decisions to streamline onboarding and maintain code quality across your team.