ck:project-organization

To standardize project structure, apply consistent directory categories and naming conventions across code, docs, plans, tests, assets, and config folders. This enforces a canonical layout that speeds up onboarding and automates file placement during scaffolding or migrations.

The best way to scaffold with naming conventions is to generate a canonical folder layout with predefined rules for nesting and categorization. This ensures outputs, scripts, and references are placed in standardized paths across diverse project types.

Yes, you can use this project organization approach for migrations and reorganization tasks. It evaluates existing files and moves them into standardized directory paths based on defined rules for category placement, naming, and nesting.

Yes, directory pattern standardization works across different languages and teams by applying a consistent project layout. It uses universal top-level directories like src, docs, tests, and config to maintain uniform structure regardless of the specific tech stack.

You need standardized directory categories for automation and AI agents because predictable output paths and naming conventions allow automated tools to reliably locate, generate, and organize project content without manual intervention.

A limitation of enforcing a canonical folder layout is that rigid nesting and category placement rules may require custom configurations for highly specialized project types that demand non-standard directory structures or unique asset organization.