coding-standards

You can enforce cross-project coding standards by adopting a shared ruleset that governs naming, immutability, formatting, and error-handling for TypeScript, React, and server-side code. This ensures readability and consistency across teams.

Standardizing code quality during onboarding and reviews involves applying reusable rules for descriptive naming, immutability defaults, and modular design. This aligns practices across projects and ensures long-term maintainability.

Yes, you can use a single coding standards ruleset for both frontend and backend JavaScript. The guidelines are framework-agnostic and provide specific guidance for TypeScript/JavaScript, React, and server-side code.

Yes, this coding standards skill works with existing linting configurations by providing a reusable ruleset that guides linting, code review, and refactoring to ensure common standards are applied consistently across projects.

You should not use framework-agnostic coding standards when your project requires highly specialized architectural patterns or framework-specific conventions that override general naming, formatting, and immutability guidelines.