Does it provide guidance on boolean naming?

Yes, it enforces a 'Question Word' prefixing strategy using is, has, can, or should to make conditional logic more readable and self-documenting.

Does this skill support specific software architectures?

Yes, it is highly optimized for Clean Architecture, Domain-Driven Design (DDD), and Modular Monolith structures, providing specific patterns for each layer.

How does it handle file naming conventions?

It promotes a kebab-case pattern with descriptive suffixes, such as user.repository.ts, to ensure files are easily searchable and their purpose is immediately clear.

What is the recommended style for interfaces and classes?

It follows modern standards using PascalCase for both, while specifically avoiding the 'I' prefix for interfaces in favor of technology-specific implementation names.

Can it help me refactor existing variable names?

Absolutely. The skill can scan your code for ambiguous names or magic numbers and suggest intention-revealing alternatives that improve maintainability.

Code Naming Conventions

Name: Code Naming Conventions
Author: marcioaltoe

bymarcioaltoe

•

Developer Tools

Enforces consistent, readable, and maintainable naming standards for files, directories, and code elements across the entire development lifecycle.

About

This skill acts as an expert architectural guide to ensure your codebase remains professional, searchable, and intuitive. It implements industry best practices for Clean Architecture and Modular Monoliths, covering everything from kebab-case file suffixes to semantic boolean prefixing. By applying a standardized approach to naming entities, use cases, and repositories, it helps teams maintain the Ubiquitous Language of their domain while reducing cognitive load during code reviews and refactoring.

Key Features

Semantic naming patterns for PascalCase classes and camelCase functions
Best-practice boolean prefixing using is, has, can, and should descriptors
Standardized kebab-case file naming with descriptive suffixes like .entity and .use-case
Clear separation of interface definitions from technology-specific implementations
Architectural directory organization distinguishing between collections and feature modules
7 GitHub stars

Use Cases

Restructuring legacy codebases to follow Clean Architecture or DDD patterns
Ensuring consistent naming during the creation of new domain services and DTOs
Reviewing existing code for naming consistency and intention-revealing variables

About

Key Features

Semantic naming patterns for PascalCase classes and camelCase functions
Best-practice boolean prefixing using is, has, can, and should descriptors
Standardized kebab-case file naming with descriptive suffixes like .entity and .use-case
Clear separation of interface definitions from technology-specific implementations
Architectural directory organization distinguishing between collections and feature modules
7 GitHub stars

Use Cases

Restructuring legacy codebases to follow Clean Architecture or DDD patterns
Ensuring consistent naming during the creation of new domain services and DTOs
Reviewing existing code for naming consistency and intention-revealing variables