How do I install the Project Structure skill?

Run npx skillmds@latest add majiayu000/project-structure 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 Project Structure safe to use?

This skill has not completed SkillMD's automated safety review yet. Independent scanners report: SkillSpector: PASS, Skill Scanner: PASS. Capability flags: docs only. SkillMD never runs a skill's scripts for you; review the SKILL.md before installing.

Which AI agents work with Project Structure?

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 Project Structure free to use?

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

Who published Project Structure?

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

Project Structure by majiayu000 — Agent Skill

Name: Project Structure
Rating: 4.2 (5 reviews)
Author: majiayu000

Project Structure

Provides comprehensive project folder structure design guidelines and best practices. Defines standard directory organizations for diverse project types including monorepos, web frameworks, backend services, libraries, and extensions. Ensures scalable, maintainable architecture through consistent file organization patterns. Specializes in separation of concerns, modular architecture, and tooling integration. Use when: designing new project structures, organizing monorepo workspaces with tools like Turborepo/Nx, structuring NestJS backend projects, organizing React/Next.js frontend applications, designing Go service architectures, creating NPM package structures, organizing VSCode extension projects, structuring Chrome extension codebases, planning directory hierarchies, migrating legacy project structures, or establishing code organization conventions for teams.

majiayu000 Updated Sep 9, 2026 567 repo stars

File contents

Project Structure Guide

Monorepo

project-root/
├── src/                         # All services/apps
├── infra/                       # Shared infrastructure
├── docs/                        # Documentation
├── .devcontainer/               # Dev Container configuration
├── .github/                     # Workflows, templates
├── .vscode/                     # VSCode settings
├── .claude/                     # Claude settings
├── .gemini/                     # Gemini settings
├── package.json                 # Root package.json. For releases, version management
├── go.work                      # Go workspace (when using Go)
├── justfile                     # Just task runner
├── .gitignore
├── .prettierrc
├── .prettierignore
└── README.md

Next.js

project-root/
├── app/
│   ├── (routes)/           # Pages (route groups)
│   ├── actions/            # Server Actions (internal mutations)
│   └── api/                # API Routes (external integrations only)
├── components/             # Shared components
├── lib/                    # Utilities and clients
├── public/                 # Static assets
├── middleware.ts           # Edge/Node.js middleware
├── next.config.js
├── package.json
└── tsconfig.json

Go

project-root/
├── cmd/                    # Execution entry points (main.go)
├── internal/               # Private packages
├── pkg/                    # Public packages
├── configs/                # Configuration files
├── scripts/                # Utility scripts
├── tests/                  # Integration tests
├── docs/                   # Documentation
├── go.mod
└── go.sum

---name: project-structuredescription: Provides comprehensive project folder structure design guidelines and best practices. Defines standard directory organizations for diverse project types including monorepos, web frameworks, backend services, libraries, and extensions. Ensures scalable, maintainable architecture through consistent file organization patterns. Specializes in separation of concerns, modular architecture, and tooling integration. Use when: designing new project structures, organizing monorepo workspaces with tools like Turborepo/Nx, structuring NestJS backend projects, organizing React/Next.js frontend applications, designing Go service architectures, creating NPM package structures, organizing VSCode extension projects, structuring Chrome extension codebases, planning directory hierarchies, migrating legacy project structures, or establishing code organization conventions for teams.--- # Project Structure Guide ## Monorepo ``` project-root/ ├── src/ # All services/apps ├── infra/ # Shared infrastructure ├── docs/ # Documentation ├── .devcontainer/ # Dev Container configuration ├── .github/ # Workflows, templates ├── .vscode/ # VSCode settings ├── .claude/ # Claude settings ├── .gemini/ # Gemini settings ├── package.json # Root package.json. For releases, version management ├── go.work # Go workspace (when using Go) ├── justfile # Just task runner ├── .gitignore ├── .prettierrc ├── .prettierignore └── README.md ``` ## Next.js ``` project-root/ ├── app/ │ ├── (routes)/ # Pages (route groups) │ ├── actions/ # Server Actions (internal mutations) │ └── api/ # API Routes (external integrations only) ├── components/ # Shared components ├── lib/ # Utilities and clients ├── public/ # Static assets ├── middleware.ts # Edge/Node.js middleware ├── next.config.js ├── package.json └── tsconfig.json ``` ## Go ``` project-root/ ├── cmd/ # Execution entry points (main.go) ├── internal/ # Private packages ├── pkg/ # Public packages ├── configs/ # Configuration files ├── scripts/ # Utility scripts ├── tests/ # Integration tests ├── docs/ # Documentation ├── go.mod └── go.sum ```

Frequently asked questions