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.