coding-standards

To enforce coding standards across NestJS and React projects, apply unified conventions for module structure, naming patterns, import ordering, and dependency injection to reduce technical debt and onboarding friction.

Best practices for Tailwind design token usage involve defining specific UI tokens to maintain visual consistency across React and Next.js components, ensuring uniform styling and reducing design drift across the application.

Yes, this coding conventions skill works without additional dependencies, providing standalone guidelines for TypeScript, NestJS, and React environments to standardize code reviews and feature implementation directly.

To standardize NestJS module structure and naming conventions, name files in kebab-case, organize imports systematically, and use constructor-based dependency injection to ensure uniform code organization across modules.

Standardized coding conventions for TypeScript backend and frontend development are needed to reduce coding inconsistency, facilitate knowledge transfer, and enable rapid feature development by providing a single reference for developers.