ck:project-organization

To organize project files into standardized locations, you need a system that applies predictable path resolution rules for documentation, plans, tests, scripts, and assets across mixed project structures.

Standardizing naming conventions involves applying consistent kebab-case patterns alongside timestamped and evergreen document formats to ensure project assets and markdown files remain predictable.

Kebab-case naming for timestamped and evergreen documents works by enforcing lowercase letters with hyphens, applying specific date-stamped or variant patterns to distinguish time-sensitive plans from permanent guides.

Yes, directory structure rules apply to mixed project structures by enforcing safe path resolution to correctly route docs, tests, scripts, and configuration files into their designated project folders.

Yes, this project organization approach supports markdown body templates by enforcing specific section order rules and structured formatting for plans, reports, journals, guides, and specs.

You should avoid automated file path resolution when your project requires custom directory structures that deviate from standardized predictable locations, or when existing naming patterns conflict with strict kebab-case enforcement.