Standardize naming conventions across code, tests, and public interfaces.
npx skills add https://github.com/alexfalkowski/bin --skill naming-standards
Please help me install this Agent Skill. Skill: naming-standards Source: https://github.com/alexfalkowski/bin/tree/main/skills/naming-standards Command: npx skills add https://github.com/alexfalkowski/bin --skill naming-standards
This skill addresses the ambiguity and maintenance costs associated with inconsistent naming in codebases, public APIs, and documentation. It provides a structured framework to ensure that names accurately reflect domain concepts and contracts.
Use the naming-standards skill to review the proposed module name and public interface for the new authentication service.
High-intent search queries and answers about installing and using this skill.
Standardize domain vocabulary by applying a structured review framework to ensure new function names align with existing project conventions, accurately reflect domain concepts, and reduce maintenance overhead. This methodology covers code, tests, and public APIs.
Evaluate API naming risk by applying a clear set of review criteria to determine whether a name accurately reflects its domain contract and communicates intended behavior to future maintainers, ensuring long-term compatibility and readability.
Yes, this approach works for legacy refactoring by providing a vocabulary stewardship methodology that ensures newly named modules and public interfaces align with established project vocabulary and clearly communicate their intended behavior.
Naming conventions improve code clarity by resolving ambiguity in codebases and public interfaces. Consistent vocabulary ensures names accurately reflect domain concepts, which reduces long-term maintenance costs and improves architectural readability.
Yes, you can standardize naming across code, tests, and public interfaces. The framework requires adherence to established project conventions and language-specific idioms to ensure vocabulary consistency across all architectural layers.
Standardize vocabulary for API design when ambiguity and maintenance costs from inconsistent naming threaten domain clarity. This is critical during architectural reviews and refactoring tasks where vocabulary consistency ensures contracts accurately reflect domain concepts.
knowletValidate code placement against Clean Architecture, DDD, and CQRS dependency rules.
fsollaOrchestrate an eight-phase refactoring process to reduce technical debt in legacy codebases.
t-stringsEnforce centralized validation standards across repository code and CI pipelines.
rysweetReview changed code via git diffs and apply fixes for reuse, quality, and efficiency.
