How do I install the Folder Org skill?

Run npx skillmds add ruchernchong/folder-org in your terminal (requires Node.js), paste this page's agent-chat prompt into Claude, Cursor, or any MCP-connected agent, or download the SKILL.md file and copy it into your agent's skills directory.

Is Folder Org safe to use?

This skill has not completed SkillMD's automated safety review yet. Capability flags: docs only. SkillMD never runs a skill's scripts for you; review the SKILL.md before installing.

Which AI agents work with Folder Org?

This skill is tagged as working with Claude Code, Claude.ai, OpenAI Codex. SKILL.md is an open format, so most agents that read a skills directory can load it too.

Is Folder Org free to use?

Yes. Installing skills from SkillMD is free, and the skill stays under its author's original license.

Who published Folder Org?

ruchernchong (@ruchernchong) published this skill. Their other Agent Skills are listed on their SkillMD profile.

Folder Org by ruchernchong — Agent Skill

Name: Folder Org
Rating: 4.2 (5 reviews)
Author: ruchernchong

File contents

Folder Structure

Core Principle: Colocation

Place code as close to where it's relevant as possible. Things that change together should be located together.

Organization Approaches

Feature-Based (Recommended for Frontend)

Group by domain - all related code in one place:

src/features/
├── auth/
│   ├── components/
│   ├── hooks/
│   ├── auth.service.ts
│   └── auth.test.ts
├── users/
└── products/

Layer-Based (Common for Backend)

Group by technical layer:

src/
├── controllers/
├── services/
├── models/
├── routes/
└── middleware/

Monorepo

apps/           # Applications
├── web/
├── api/
packages/       # Shared libraries (by domain, not language)
├── types/
├── utils/
└── ui/

Where to Put Things

Type	Location
Shared types	`types/` or `packages/types/`
Utilities	`lib/` or `utils/` (split by domain)
Config	`config/` or root
Unit tests	Colocate: `foo.test.ts` next to `foo.ts`
E2E tests	`e2e/` or `tests/e2e/`
Mocks/fixtures	`__mocks__/` or `test/mocks/`

Naming Conventions

Type	Convention
Files	`kebab-case.ts`
Unit tests	`*.test.ts`
E2E tests	`*.e2e.ts`
Schemas	`*.schema.ts`

Anti-Patterns

Catch-all files: Avoid utils.ts, helpers.ts - split by domain
Deep nesting: Keep < 4 levels, use descriptive names instead
Separated unit tests: Don't put all in __tests__/ - colocate instead
Language grouping: In monorepos, group by domain not language
Bloated barrels: Avoid index.ts with 50+ re-exports

---name: folder-orgdescription: Project code structure and file organization. Use when creating files, organizing components, or deciding where code should live. (project)--- # Folder Structure ## Core Principle: Colocation > Place code as close to where it's relevant as possible. Things that change together should be located together. ## Organization Approaches ### Feature-Based (Recommended for Frontend) Group by domain - all related code in one place: ``` src/features/ ├── auth/ │ ├── components/ │ ├── hooks/ │ ├── auth.service.ts │ └── auth.test.ts ├── users/ └── products/ ``` ### Layer-Based (Common for Backend) Group by technical layer: ``` src/ ├── controllers/ ├── services/ ├── models/ ├── routes/ └── middleware/ ``` ### Monorepo ``` apps/ # Applications ├── web/ ├── api/ packages/ # Shared libraries (by domain, not language) ├── types/ ├── utils/ └── ui/ ``` ## Where to Put Things | Type | Location | |------|----------| | Shared types | `types/` or `packages/types/` | | Utilities | `lib/` or `utils/` (split by domain) | | Config | `config/` or root | | Unit tests | Colocate: `foo.test.ts` next to `foo.ts` | | E2E tests | `e2e/` or `tests/e2e/` | | Mocks/fixtures | `__mocks__/` or `test/mocks/` | ## Naming Conventions | Type | Convention | |------|------------| | Files | `kebab-case.ts` | | Unit tests | `*.test.ts` | | E2E tests | `*.e2e.ts` | | Schemas | `*.schema.ts` | ## Anti-Patterns - **Catch-all files**: Avoid `utils.ts`, `helpers.ts` - split by domain - **Deep nesting**: Keep < 4 levels, use descriptive names instead - **Separated unit tests**: Don't put all in `__tests__/` - colocate instead - **Language grouping**: In monorepos, group by domain not language - **Bloated barrels**: Avoid `index.ts` with 50+ re-exports

Frequently asked questions