project-structure

Define standardized project structures and naming conventions for full-stack MVP development.

Updated Aug 23, 2026
One-click install
npx skills add https://github.com/GolfNext/golfnext-tool-kiosk-support-page --skill project-structure-golfnext
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: project-structure
Source: https://github.com/GolfNext/golfnext-tool-kiosk-support-page/tree/main/.claude/plugins/mvp-dev-stack/skills/project-structure
Command: npx skills add https://github.com/GolfNext/golfnext-tool-kiosk-support-page --skill project-structure-golfnext

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill provides a clear, opinionated structure for full-stack MVP projects, ensuring consistency and maintainability across different developers and projects.

Core Features & Use Cases

  • Monorepo Structure: Defines a recommended layout for monorepos with separate client and server directories.
  • Next.js Full-Stack Structure: Offers an alternative structure for projects using Next.js for both frontend and API.
  • Naming Conventions: Enforces consistent naming for components, hooks, utilities, types, API routes, and files.
  • Key Config Files: Provides essential configurations for TypeScript, .gitignore, and .env.example.
  • MVP Decisions: Outlines recommended technologies for a fast MVP development experience.
  • Use Case: When starting a new project, use this skill to quickly set up a well-organized directory structure and establish coding conventions from the outset.

Quick Start

Apply the project-structure skill to set up a new monorepo project.

Frequently Asked Questions about project-structure

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

FAQPage Schema
What is the best way to structure a full-stack MVP project?

A standardized project structure for full-stack MVPs uses either a monorepo layout with separate client and server directories or a Next.js full-stack architecture. This approach enforces consistent file organization and naming conventions to streamline developer onboarding.

How do I set up a monorepo with Next.js and TypeScript?

Set up a Next.js and TypeScript monorepo by applying a standardized project structure that defines separate client and server directories. This enforces naming conventions for components and hooks while providing essential TypeScript configuration files.

What naming conventions should I use for Next.js API routes and utilities?

For Next.js API routes and utilities, you should use standardized naming conventions that enforce consistency across components, hooks, types, and files. This ensures consistent file organization and facilitates easier developer onboarding across full-stack projects.

Can I use this project structure for both monorepo and Next.js full-stack architectures?

Yes, this project structure supports both monorepo and Next.js full-stack architectures. It defines a recommended monorepo layout with separate client and server directories, alongside an alternative Next.js structure for combined frontend and API development.

What key configuration files are needed for a TypeScript monorepo?

Key configuration files needed for a TypeScript monorepo include TypeScript configurations, a `.gitignore` file, and a `.env.example` file. These essential configurations are provided to establish a consistent development environment for full-stack MVP development.