naming-conventions

To enforce kebab-case naming, standardize all directory and file names to use lowercase letters separated by hyphens. This approach ensures codebase consistency, reducing confusion and improving maintainability for all team members.

Organizing files within a Single Source of Truth structure requires specific layout guidance that standardizes where code artifacts live. This standardization supports developer onboarding and codebase navigation by providing a predictable directory structure.

Standardize script-generated file paths by applying naming conventions to temporary files, including those in `.ai/.tmp/` directories. This ensures even automated and transient code artifacts adhere to project standards and maintain consistency.

Yes, standardizing code structure supports developer onboarding by making the codebase easier to navigate. When all directories, files, and identifiers adhere to predictable kebab-case rules, new team members can locate and understand code artifacts faster.

Using kebab-case for code organization provides a consistent and predictable naming convention across directories and files. This standardization reduces confusion when navigating the codebase and ensures all related files follow established project standards.

Yes, you can define skill naming standards alongside standard file and directory naming conventions. This ensures all individual skills and their related code artifacts adhere to the same kebab-case rules and SSOT layout guidance.