folder-structure-designer
Design a folder structure people actually file into — shallow, purpose-first, with a home for everything and an inbox for the undecided, sized to the team that must maintain it. Use when asked organize our shared drive, design a folder structure for the project, where should things live, or our files are chaos. Produces the structure with its placement rules, the depth and naming constraints, the _inbox convention, and the migration-lite plan for the existing mess.
npx skills add mohitagw15856/pm-claude-skills --skill folder-structure-designer --agent claude-code
Same command for any agent — swap --agent for codex, cursor, copilot.
Weekly change comes from our own snapshots, not the repository page — it measures attention, not adoption.
# Folder Structure Designer Skill Folder structures fail by ambition: seven levels deep, a taxonomy only its author understands, and within a month everyone files into `misc/` or nowhere. The structure that survives is shallow (three levels max), organized by *how people look for things* (purpose, then project — not file type, not org chart), and honest about human behavior: there's an `_inbox` for the undecided, a placement rule for every top-level folder, and search is embraced as half the system rather than defeated. ## What This Skill Produces - **The structure** — top levels with per-folder placement rules ("goes here if…"), three levels deep maximum - **The conventions** — `_inbox` for undecided, `_archive` per area, the naming rule (see [filename-convention](../filename-convention/SKILL.md)) - **The one-page guide** — the structure explained in ten lines, postable where the team will see it - **The migration-lite plan** — new structure now, old mess frozen and drained opportunistically (never the big-bang reorganization that stalls at 30%) ## Required Inputs Ask for these if not provided: - **Who files and who finds** — team size, roles, and the honest filing culture (a stru
- What This Skill Produces
- Required Inputs
- Framework: The Structure Rules
- Output Format
- The Structure
- The One-Page Guide
- Migration-Lite
- Quality Checks
- Anti-Patterns
What does the folder-structure-designer skill do?
Design a folder structure people actually file into — shallow, purpose-first, with a home for everything and an inbox for the undecided, sized to the team that must maintain it. Use when asked organize our shared drive, design a folder structure for the project, where should things live, or our files are chaos. Produces the structure with its placement rules, the depth and naming constraints, the _inbox convention, and the migration-lite plan for the existing mess.
How do I install it?
Run `npx skills add mohitagw15856/pm-claude-skills --skill folder-structure-designer --agent claude-code` — it drops the skill into your project so the agent can pick it up. Swap the --agent value for codex, cursor or copilot if you use one of those.
Where does this skill come from?
From mohitagw15856/pm-claude-skills, a repository with 1,255 stars. We read it straight from the repository tree rather than a submitted listing, so what you see here is what is actually published.
Is a popular skill a good skill?
Not necessarily. Stars measure attention, not adoption — a repository can trend for a week and be abandoned. That is why we show the weekly change from our own snapshots next to the total, instead of a single flattering number.