laravel-inertia-react-structure

Organize resource/js directory structure for Laravel Inertia React projects.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill provides a standardized frontend architecture blueprint for Laravel Inertia React projects, helping teams organize the resources/js directory into clearly defined folders to improve consistency, onboarding, and long-term maintainability.

Core Features & Use Cases

  • Directory conventions for resources/js including common, modules, pages, shadcn
  • Clear naming conventions for components, contexts, files, and directories
  • Guidance on module organization, pages, and multi-zone apps
  • Use case: When starting a Laravel Inertia React project, follow these conventions to structure code and accelerate onboarding.

Quick Start

Follow these conventions when scaffolding or reviewing a Laravel Inertia React frontend to ensure consistency across teams.

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 Laravel Inertia React frontend in the resources/js directory?▼

Organize the Laravel Inertia React frontend by scaffolding the resources/js directory into common, modules, pages, and shadcn folders. This provides a standardized architecture blueprint with clear naming conventions to ensure consistency and accelerate team onboarding.

What are the best practices for naming conventions in a Laravel Inertia React project?▼

Best practices for naming conventions in a Laravel Inertia React project involve standardizing names for components, contexts, files, and directories. Following these specified rules ensures long-term maintainability and consistency across the frontend architecture for new and existing projects.

Does this frontend architecture blueprint support existing Laravel Inertia React projects?▼

Yes, this frontend architecture blueprint is applicable to both new and existing Laravel Inertia React projects. It guides the scaffolding of components, pages, and modules to help teams refactor their resources/js directory for scalable maintainability and consistency.

How do I organize modules and pages for multi-zone apps in Laravel Inertia React?▼

Organize modules and pages for multi-zone apps in Laravel Inertia React by following the specified directory structure and module organization rules. This approach separates concerns within the resources/js folder, improving onboarding and long-term maintainability across teams.

When do I need a standardized frontend structure for Laravel Inertia apps?▼

You need a standardized frontend structure for Laravel Inertia apps when starting a new project or scaling an existing one to improve consistency. Following these directory conventions accelerates onboarding and ensures long-term maintainability across your development team.