ck:project-organization

To standardize project structure, this skill organizes top-level categories like src, docs, plans, tests, scripts, assets, and config while enforcing consistent file naming and markdown templates across your repository. It provides standardized skeletons to accelerate project kickoffs and reduce onboarding time.

The best way to organize existing project assets is through guided reorganization, which maps current files into a scalable, repeatable layout. This enforces predictable top-level categories and nesting guidelines to ensure consistent file locations across plans, docs, and code.

Yes, you can use standardized markdown templates for docs and plans to ensure consistent content structure. This skill provides built-in markdown guidelines and templates to reduce formatting confusion and accelerate project documentation kickoffs.

Yes, the project structure supports optional directories including scripts, references, and assets. While enforcing core top-level categories like src and config, it flexibly accommodates optional folders to fit varying project requirements and scales.

You need to reorganize file locations and nesting when your project lacks a predictable layout, causing team confusion and onboarding delays. Applying standardized top-level categories and naming conventions ensures a scalable, repeatable structure across all assets.