ck:project-organization

Organize project files into standard directories with kebab-case naming.

Updated Apr 2, 2026
One-click install
npx skills add https://github.com/EdgeHunt/EdgeHunt --skill ck-project-organization-edgehunt
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: ck:project-organization
Source: https://github.com/EdgeHunt/EdgeHunt/tree/main/.claude/skills/project-organization
Command: npx skills add https://github.com/EdgeHunt/EdgeHunt --skill ck-project-organization-edgehunt

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

Organize and standardize project file layouts, naming conventions, and documentation templates across any repository to reduce confusion and improve collaboration.

Core Features & Use Cases

  • Standardizes top-level categories (plans, docs, tests, scripts, assets) and enforces kebab-case naming.
  • Provides ready-made templates and guidance for Markdown bodies and ADRs.
  • Scans and organizes existing assets, proposes a migration plan, and can execute changes after confirmation.

Quick Start

Organize the current project by applying the standard directory layout and naming conventions, creating missing folders (plans, docs, tests, assets) as needed.

Frequently Asked Questions about ck:project-organization

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I standardize project directory structure and naming conventions?

Standardize project structure by applying categorized directory layouts for plans, docs, tests, scripts, and assets, while enforcing kebab-case naming conventions across all files to maintain consistent project organization.

What is the best way to reorganize existing project assets and file layouts?

Reorganize existing project assets by scanning the current file layout, generating a migration plan to standard directory categories, and executing path changes after explicit user confirmation.

Can I use markdown templates for project documentation and ADRs?

Yes, you can apply ready-made structured Markdown body templates and ADR formats to standardize project documentation within the dedicated docs and plans directories.

Does project structure organization work for any repository type?

Yes, project structure organization applies to any project type by standardizing top-level directory categories and file naming conventions to enforce consistent output paths across diverse repositories.

What are the limitations of enforcing directory categorization and kebab-case naming?

Enforcing directory categorization and kebab-case naming requires migrating existing non-standard file paths, which requires careful execution of the proposed migration plan to avoid disrupting current workflows.