Global Coding Style

About

This skill ensures long-term maintainability and readability across NestJS API and shared package directories by applying rigorous coding standards. It automates the enforcement of project-specific ESLint and Prettier configurations, such as 120-character line widths and single-quote styles, while promoting strict TypeScript practices like the elimination of 'any' types and the use of optional chaining. By standardizing file naming into kebab-case and organizing imports into logical, alphabetical blocks, this skill helps developers focus on logic while keeping the codebase consistent and professional.

Key Features

• Applies consistent Prettier formatting including 120-character line width and trailing commas.
• 0 GitHub stars
• Automates import organization by grouping external, workspace, and internal modules alphabetically.
• Implements NestJS-specific patterns like @Injectable decorators and private constructors for immutable objects.
• Enforces strict TypeScript rules including no-explicit-any and mandatory nullish coalescing.
• Standardizes file naming using kebab-case and class naming with PascalCase conventions.

Use Cases

• Performing code quality reviews to remove dead code, unused imports, and non-standard syntax.
• Refactoring existing TypeScript code to align with project-wide ESLint and Prettier standards.
• Scaffolding new NestJS controllers, services, and DTOs with correct naming and directory structures.