project-structure

Classify project folders and recommend workspace, repository, and layout structures.

1|Updated May 13, 2026
One-click install
npx skills add https://github.com/LeeorNahum/project-structure-skill --skill project-structure-leeornahum
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: project-structure
Source: https://github.com/LeeorNahum/project-structure-skill/tree/main
Command: npx skills add https://github.com/LeeorNahum/project-structure-skill --skill project-structure-leeornahum

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) and assets (resource) components.

What problem does it solve?

Projects often accumulate confusing, inconsistent folder and repository structure as they grow, leading to wasted time navigating files, duplicated work, and unclear ownership of deliverables. This Skill eliminates that problem by providing clear, opinionated guidance for selecting the correct workspace, repo, and folder shape upfront, before structure debt accumulates.

Core Features & Use Cases

  • Project Boundary Classification: Accurately classify any folder as a workspace container, planning repo, full project root, web/app monorepo, firmware/library repo, device folder, brand folder, or standalone artifact repo.
  • Opinionated Layout & Naming Rules: Get pre-defined folder shapes, Title-Dash-Case naming conventions, and gitignore strategies tailored to each project type.
  • Nested Repo & Skill Guidance: Clear rules for Git posture, nested canonical deliverable repos, and local skill installation under .agents/skills/.
  • Use Case: For example, if you are starting a new hardware product with separate web, firmware, and device design components, this Skill will recommend the correct full project root shape with dedicated organizer folders for each surface, plus the appropriate Git settings for the root and nested repos.

Quick Start

Use the project-structure skill to classify your current project folder and receive a recommended folder shape, list of first files to create, and initial setup tasks tailored to your project type.

Frequently Asked Questions about project-structure

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

FAQPage Schema
How do I choose the right folder structure for my project repository?

Project structure guidance classifies your folder as a workspace container, full project root, or firmware repo, then provides an opinionated folder layout, Title-Dash-Case naming conventions, and gitignore strategy tailored to that specific project type.

What is the best way to organize a monorepo with web, firmware, and device folders?

The best way to organize a multi-component monorepo is using a full project root shape with dedicated organizer folders for each surface, applying nested canonical deliverable repo boundaries and appropriate Git settings for the root and nested repositories.

How do I set up Git and nested repo boundaries when scaffolding a new project?

Set up Git and nested repo boundaries by applying the Skill's boundary rules, which define the correct Git posture and gitignore strategy for your root repository while establishing clear separation for nested canonical deliverable repos.

What naming conventions should I use for project scaffolding and folder organization?

For project scaffolding and folder organization, use Title-Dash-Case naming conventions to enforce consistency across workspace containers, brand folders, device folders, and standalone artifact repositories.

When should I split or reorganize an existing project's folder structure?

You should split or reorganize a project's folder structure when it accumulates messy, inconsistent shapes, causing wasted navigation time and duplicated work, by auditing and reclassifying folders into standardized workspace or repo layouts.

Can I use this project structure guidance for local workspace containers and planning repos?

Yes, you can use this project structure guidance for local workspace containers and planning repos, as it provides specific folder shapes, initial setup tasks, and local skill installation rules under the `.agents/skills/` directory.