folder-org

Organize software projects with feature-based, layer-based, or monorepo folder structures.

1|Updated Jan 8, 2026
One-click install
npx skills add https://github.com/ruchernchong/claude-kit --skill folder-org
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: folder-org
Source: https://github.com/ruchernchong/claude-kit/tree/main/skills/folder-org
Command: npx skills add https://github.com/ruchernchong/claude-kit --skill folder-org

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill helps teams organize codebases by enforcing clear folder structures and colocated components, reducing confusion and onboarding time.

Core Features & Use Cases

  • Feature-based organization: group related features under src/features with components, hooks, and tests colocated.
  • Layer-based organization: separate by technical layers like controllers, services, models, routes, middleware.
  • Monorepo guidance: structure apps/ and packages/ to support multiple platforms while sharing utilities and types.
  • Naming conventions: consistent file names and folder names to improve discoverability.

Quick Start

Start by choosing an organization approach (feature-based, layer-based, or monorepo) and create top-level directories accordingly. Place related files next to each other (colocation) and keep tests beside source files. Document the chosen structure in a README so the team follows it consistently.

Frequently Asked Questions about folder-org

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

FAQPage Schema
How do I structure a monorepo with shared types and utilities?

Organize a monorepo by separating top-level apps/ and packages/ directories to support multiple platforms while sharing utilities and types. This layout reduces duplication and keeps shared dependencies consistent across different applications within the same repository.

What is the best way to organize frontend and backend codebases?

Organize frontend and backend codebases by enforcing colocated layouts that group related components, hooks, and tests next to each other. Choose feature-based grouping under src/features or layer-based separation across controllers, services, and models to reduce cognitive load.

How do I set up feature-based folder organization for my project?

Set up feature-based folder organization by creating directories under src/features and grouping related components, hooks, and tests inside each feature folder. Keep tests beside source files to reduce cognitive load and speed up team onboarding.

When should I use layer-based architecture instead of feature-based organization?

Use layer-based architecture instead of feature-based organization when separating code by technical layers like controllers, services, models, routes, and middleware. This approach codifies conventions for technical responsibilities rather than grouping by business features.

Does colocation work for both source files and tests in a monorepo?

Colocation works for both source files and tests by keeping them placed next to each other within the chosen folder structure. Whether using feature-based, layer-based, or monorepo architectures, colocating tests beside sources reduces cognitive load and speeds up onboarding.