vite-react-project-structure

Define standardized file layouts for Vite + React projects.

Updated Sep 6, 2025
One-click install
npx skills add https://github.com/kabaka/oscar-export-analyzer --skill vite-react-project-structure
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: vite-react-project-structure
Source: https://github.com/kabaka/oscar-export-analyzer/tree/main/.github/skills/vite-react-project-structure
Command: npx skills add https://github.com/kabaka/oscar-export-analyzer --skill vite-react-project-structure

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Provides a standardized blueprint for organizing Vite + React projects, reducing onboarding time and confusion when creating new components, hooks, utilities, or feature modules.

Core Features & Use Cases

  • Directory conventions: guidance on placing code under src/components, src/hooks, src/utils, and src/features.
  • Naming standards: file extensions and naming conventions to improve readability and maintainability.
  • Use cases: starting new features, migrating legacy code, onboarding new teammates.

Quick Start

Create a new feature module under src/features/ following the documented directory structure and naming conventions.

Frequently Asked Questions about vite-react-project-structure

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

FAQPage Schema
What is the best way to organize a Vite and React project structure?

The best way to organize a Vite and React project structure is to use a standardized file layout with directories like src/components, src/hooks, src/utils, and src/features. This ensures consistent module organization and maintainable code.

How do I structure feature modules and components in React?

To structure feature modules and components in React, place reusable code under src/components, src/hooks, and src/utils, while grouping domain logic into src/features. This streamlines development and clarifies module boundaries.

Where should I place test files in a Vite React project?

Test files in a Vite React project should be placed according to standardized directory naming conventions and module boundaries. This test placement strategy maintains a scalable codebase and improves onboarding.

Does this React project structure guide apply to existing legacy codebases?

Yes, this React project structure guide applies to existing legacy codebases. It provides directory conventions and naming standards that are specifically useful for migrating legacy code and onboarding new teammates.

Why do I need standardized file extensions and naming conventions for React?

You need standardized file extensions and naming conventions for React to improve code readability and maintainability. Enforcing these standards reduces confusion when creating new components, hooks, utilities, or feature modules.