skills.rest
DatTran26
DatTran26COMMUNITY
Explore all skills by this author →
GitHub

ck:project-organization

Organize project files into standardized categories with kebab-case naming and templates.

Updated Apr 9, 2026
Search Tags:#planning#templates#structure#organize#naming-conventions#project#file-management
One-click install
npx skills add https://github.com/DatTran26/KienTruThiHanh --skill ck-project-organization-dattran26
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: ck:project-organization
Source: https://github.com/DatTran26/KienTruThiHanh/tree/main/.agents/skills/project-organization
Command: npx skills add https://github.com/DatTran26/KienTruThiHanh --skill ck-project-organization-dattran26

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

Organize and standardize project structure by defining consistent locations for docs, plans, tests, scripts, assets, and config, plus uniform naming and content templates across a repository.

Core Features & Use Cases

  • Establish top-level categories and subfolders (docs, plans, tests, scripts, assets, config, guides) to improve discovery and governance.
  • Enforce naming conventions, including kebab-case slugs, date-based plan folders, and evergreen content rules to reduce drift.
  • Provide reusable templates and guidance for planning, documentation, and ADRs to streamline collaboration and onboarding.

Quick Start

Create or reorganize your project structure using the defined categories and templates to align with the SKILL's standards.

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 structure and file naming conventions?▼

Standardize project structure by defining consistent top-level categories like docs, plans, tests, and config, while enforcing kebab-case naming for files. This reduces drift and improves discovery across the repository.

What's the best way to organize documentation and planning files in a repository?▼

Organize documentation and plans by separating evergreen docs under non-timestamped names and placing time-sensitive plans into date-based folders. This layout streamlines collaboration and keeps governance clear.

How do I enforce kebab-case naming and date-based timestamps for project files?▼

Enforce kebab-case naming for file slugs and apply date-based timestamps specifically for plan and report folders. Evergreen docs remain under non-timestamped names to maintain a uniform repository structure.

Does this project organization approach work for any project type and scale?▼

Yes, it applies to any project type and scale. Establish top-level categories and subfolders to improve asset discovery, governance, and onboarding without being limited to a specific platform or framework.

When should I use date-based folders versus evergreen names for docs?▼

Use date-based folders for time-sensitive plans and reports, and use non-timestamped evergreen names for permanent documentation. This distinction prevents content drift and maintains consistent file management.

Related Skills

Explore More Software Engineering Skills→
lrbjklrbjk

unity-project-scout

Assess Unity projects for version, render pipeline, packages, asmdefs, and folder structure.

Community
Intermediate
HerbertGaoHerbertGao
1

openspec-onboard

Guide new contributors through the complete OpenSpec workflow in a codebase.

Community
Advanced
NammDevNammDev
2

assets-organizing

Organize asset outputs by topic, date format, and slug into standardized folders.

Community
Intermediate
012e012e
1

nx-generate

Generate code scaffolding and migrations using Nx generators in a monorepo.

Community
Advanced