laravel-inertia-react-structure

Define scalable frontend directory and naming conventions for Laravel Inertia React applications.

Updated Aug 27, 2026
One-click install
npx skills add https://github.com/samzzi/dotfiles --skill laravel-inertia-react-structure
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: laravel-inertia-react-structure
Source: https://github.com/samzzi/dotfiles/tree/main/config/claude/skills/laravel-inertia-react-structure
Command: npx skills add https://github.com/samzzi/dotfiles --skill laravel-inertia-react-structure

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Frontend structure conventions for Laravel Inertia React projects provide a clear, scalable layout for organizing components, pages, modules, and helper utilities, reducing cognitive load and onboarding time for new developers.

Core Features & Use Cases

  • Directory guidelines for resources/js/common, modules, pages, and shadcn to ensure consistency across projects.
  • Naming conventions: Components use PascalCase, helpers/hooks/constants stores use camelCase, directories use kebab-case.
  • Page and module organization patterns, including Admin vs client areas and how to add Inertia pages with consistent naming.

Quick Start

Follow these guidelines when scaffolding a new Laravel Inertia React frontend: create the four base directories under resources/js, apply the naming conventions, and organize new components, pages, and modules accordingly.

Frequently Asked Questions about laravel-inertia-react-structure

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

FAQPage Schema
How do I structure a scalable Laravel Inertia React frontend?

Organize new components, pages, and modules under four base directories in resources/js: common, modules, pages, and shadcn. Apply PascalCase for components, camelCase for helpers and constants, and kebab-case for directories to ensure consistency.

What naming conventions should I use for Laravel Inertia React components and directories?

Use PascalCase for React components, camelCase for helpers, hooks, and constants stores, and kebab-case for directories. Following these conventions ensures consistent component organization and predictable imports across your frontend architecture.

How do I organize Admin and client areas in an Inertia React application?

Organize Admin and client areas using page and module patterns within the resources/js directories. This multi-zone structure separates user interfaces while maintaining consistent Inertia page naming conventions across both areas.

When do I need frontend structure guidelines for my Laravel Inertia React project?

You need frontend structure guidelines when scaffolding a new Laravel Inertia React project or scaling an existing one. They provide a clear layout for components, pages, and modules, reducing cognitive load and onboarding time for new developers.

What's the best way to scaffold a new Inertia React frontend in Laravel?

The best way is to create the four base directories under resources/js and apply standard naming conventions immediately. Organize new components, pages, and modules according to these guidelines from the start to ensure project consistency.