ck:project-organization

Organize project files into standardized directories using frontmatter and naming rules.

1|Updated Mar 5, 2026
One-click install
npx skills add https://github.com/hotriluan/alkana_web --skill ck-project-organization
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: ck:project-organization
Source: https://github.com/hotriluan/alkana_web/tree/main/.opencode/skills/project-organization
Command: npx skills add https://github.com/hotriluan/alkana_web --skill ck-project-organization

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

Organizes and standardizes a project's files and folders to reduce confusion, duplication, and misplacement of assets.

Core Features & Use Cases

  • Structured templates for plans, docs, and assets to ensure consistent output.
  • Enforced naming conventions and top-level categories to improve discoverability.
  • Deterministic placement of new files based on frontmatter and directory guidelines, across new and existing projects.

Quick Start

Run the organizer on your project root to establish a standardized file layout.

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 my project's folder structure and file naming conventions?▼

To standardize project structure, run the organizer on your project root to enforce directory rules, deterministic file placement, and consistent naming conventions across all assets.

What is the best way to organize existing project assets without duplicating files?▼

Reorganizing existing project assets requires enforcing deterministic placement based on frontmatter and top-level categories, which reduces confusion, misplacement, and file duplication.

Can I use frontmatter to automatically place new docs and plans into the correct directories?▼

Yes, you can use frontmatter-driven discovery to enforce deterministic placement for new files, ensuring docs, plans, and tests are automatically routed to the correct project directories.

Does this project organization approach work for both new and existing repositories?▼

Yes, this approach applies to both establishing layouts for new projects and reorganizing existing assets, applying directory rules and structured templates to standardize any repository.

When do I need to use structured templates for project structure standardization?▼

You need structured templates for project structure standardization when you want to ensure consistent output across plans, docs, and assets while improving discoverability through enforced top-level categories.