Laravel Boost Guidelines

The Laravel Boost guidelines are specifically curated by Laravel maintainers for this application. These guidelines should be followed closely to enhance the user's satisfaction building Laravel applications.

Foundational Context

This application is a Laravel application and its main Laravel ecosystems package & versions are below. You are an expert with them all. Ensure you abide by these specific packages & versions.

• php - 8.4
• laravel/framework (LARAVEL) - v13
• laravel/prompts (PROMPTS) - v0
• laravel/socialite (SOCIALITE) - v5
• livewire/livewire (LIVEWIRE) - v4
• laravel/breeze (BREEZE) - v2
• laravel/mcp (MCP) - v0
• laravel/pint (PINT) - v1
• laravel/sail (SAIL) - v1
• phpunit/phpunit (PHPUNIT) - v11
• prettier (PRETTIER) - v3
• tailwindcss (TAILWINDCSS) - v4

Conventions

• You must follow all existing code conventions used in this application. When creating or editing a file, check sibling files for the correct structure, approach, naming.
• Use descriptive names for variables and methods. For example, isRegisteredForDiscounts, not discount().
• Check for existing components to reuse before writing a new one.

Verification Scripts

• Do not create verification scripts or tinker when tests cover that functionality and prove it works. Unit and feature tests are more important.

Application Structure & Architecture

• Stick to existing directory structure - don't create new base folders without approval.
• Do not change the application's dependencies without approval.

Frontend Bundling

• If the user doesn't see a frontend change reflected in the UI, it could mean they need to run npm run build, npm run dev, or composer run dev. Ask them.

Replies

• Be concise in your explanations - focus on what's important rather than explaining obvious details.

Documentation Files

• You must only create documentation files if explicitly requested by the user.

=== boost rules ===

Laravel Boost

• Laravel Boost is an MCP server that comes with powerful tools designed specifically for this application. Use them.

Artisan

• Use the list-artisan-commands tool when you need to call an Artisan command to double check the available parameters.

URLs

• Whenever you share a project URL with the user you should use the get-absolute-url tool to ensure you're using the correct scheme, domain / IP, and port.

Tinker / Debugging

• You should use the tinker tool when you need to execute PHP to debug code or query Eloquent models directly.
• Use the database-query tool when you only need to read from the database.

Reading Browser Logs With the browser-logs Tool

• You can read browser logs, errors, and exceptions using the browser-logs tool from Boost.
• Only recent browser logs will be useful - ignore old logs.

Searching Documentation (Critically Important)

• Boost comes with a powerful search-docs tool you should use before any other approaches. This tool automatically passes a list of installed packages and their versions to the remote Boost API, so it returns only version-specific documentation specific for the user's circumstance. You should pass an array of packages to filter on if you know you need docs for particular packages.
• The 'search-docs' tool is perfect for all Laravel related packages, including Laravel, Inertia, Livewire, Filament, Tailwind, Pest, Nova, Nightwatch, etc.
• You must use this tool to search for Laravel-ecosystem documentation before falling back to other approaches.
• Search the documentation before making code changes to ensure we are taking the correct approach.
• Use multiple, broad, simple, topic based queries to start. For example: ['rate limiting', 'routing rate limiting', 'routing'].
• Do not add package names to queries - package information is already shared. For example, use test resource table, not filament 4 test resource table.

Available Search Syntax

• You can and should pass multiple queries at once. The most relevant results will be returned first.

1. Simple Word Searches with auto-stemming - query=authentication - finds 'authenticate' and 'auth'
2. Multiple Words (AND Logic) - query=rate limit - finds knowledge containing both "rate" AND "limit"
3. Quoted Phrases (Exact Position) - query="infinite scroll" - Words must be adjacent and in that order
4. Mixed Queries - query=middleware "rate limit" - "middleware" AND exact phrase "rate limit"
5. Multiple Queries - queries=["authentication", "middleware"] - ANY of these terms

=== php rules ===

PHP

• Always use curly braces for control structures, even if it has one line.

Constructors

• Use PHP 8 constructor property promotion in __construct().
  • public function __construct(public GitHub $github) { }
• Do not allow empty __construct() methods with zero parameters.

Type Declarations

• Always use explicit return type declarations for methods and functions.
• Use appropriate PHP type hints for method parameters.

Comments

• Prefer PHPDoc blocks over comments. Never use comments within the code itself unless there is something very complex going on.

PHPDoc Blocks

• Add useful array shape type definitions for arrays when appropriate.

Enums

• Typically, keys in an Enum should be TitleCase. For example: FavoritePerson, BestLake, Monthly.

=== herd rules ===

Laravel Herd

• The application is served by Laravel Herd and will be available at: https?://[kebab-case-project-dir].test. Use the get-absolute-url tool to generate URLs for the user to ensure valid URLs.
• You must not run any commands to make the site available via HTTP(s). It is always available through Laravel Herd.

=== laravel/core rules ===

Do Things the Laravel Way

• Use php artisan make: commands to create new files (i.e. migrations, controllers, models, etc.). You can list available Artisan commands using the list-artisan-commands tool.
• If you're creating a generic PHP class, use artisan make:class.
• Pass --no-interaction to all Artisan commands to ensure they work without user input. You should also pass the correct --options to ensure correct behavior.

Database

• Always use proper Eloquent relationship methods with return type hints. Prefer relationship methods over raw queries or manual joins.
• Use Eloquent models and relationships before suggesting raw database queries
• Avoid DB::; prefer Model::query(). Generate code that leverages Laravel's ORM capabilities rather than bypassing them.
• Generate code that prevents N+1 query problems by using eager loading.
• Use Laravel's query builder for very complex database operations.

Model Creation

• When creating new models, create useful factories and seeders for them too. Ask the user if they need any other things, using list-artisan-commands to check the available options to php artisan make:model.

APIs & Eloquent Resources

• For APIs, default to using Eloquent API Resources and API versioning unless existing API routes do not, then you should follow existing application convention.

Controllers & Validation

• Always create Form Request classes for validation rather than inline validation in controllers. Include both validation rules and custom error messages.
• Check sibling Form Requests to see if the application uses array or string based validation rules.

Queues

• Use queued jobs for time-consuming operations with the ShouldQueue interface.

Authentication & Authorization

• Use Laravel's built-in authentication and authorization features (gates, policies, Sanctum, etc.).

URL Generation

• When generating links to other pages, prefer named routes and the route() function.

Configuration

• Use environment variables only in configuration files - never use the env() function directly outside of config files. Always use config('app.name'), not env('APP_NAME').

Testing

• When creating models for tests, use the factories for the models. Check if the factory has custom states that can be used before manually setting up the model.
• Faker: Use methods such as $this->faker->word() or fake()->randomDigit(). Follow existing conventions whether to use $this->faker or fake().
• When creating tests, make use of php artisan make:test [options] <name> to create a feature test, and pass --unit to create a unit test. Most tests should be feature tests.

Vite Error

• If you receive an "Illuminate\Foundation\ViteException: Unable to locate file in Vite manifest" error, you can run npm run build or ask the user to run npm run dev or composer run dev.

=== laravel/v13 rules ===

Laravel 13

• Use the search-docs tool to get version specific documentation.
• Since Laravel 11, Laravel has a new streamlined file structure which this project uses.

Laravel 13 Structure

• No middleware files in app/Http/Middleware/.
• bootstrap/app.php is the file to register middleware, exceptions, and routing files.
• bootstrap/providers.php contains application specific service providers.
• No app\Console\Kernel.php - use bootstrap/app.php or routes/console.php for console configuration.
• Commands auto-register - files in app/Console/Commands/ are automatically available and do not require manual registration.

Database

• When modifying a column, the migration must include all of the attributes that were previously defined on the column. Otherwise, they will be dropped and lost.
• Laravel 11+ allows limiting eagerly loaded records natively, without external packages: $query->latest()->limit(10);.

Models

• Casts can and likely should be set in a casts() method on a model rather than the $casts property. Follow existing conventions from other models.

=== livewire/core rules ===

Livewire Core

• Use the search-docs tool to find exact version specific documentation for how to write Livewire & Livewire tests.
• Use the php artisan make:livewire [Posts\\CreatePost] artisan command to create new components
• State should live on the server, with the UI reflecting it.
• All Livewire requests hit the Laravel backend, they're like regular HTTP requests. Always validate form data, and run authorization checks in Livewire actions.

Livewire Best Practices

• Livewire components require a single root element.

• Use wire:loading and wire:dirty for delightful loading states.

• Add wire:key in loops:

  @foreach ($items as $item)
      <div wire:key="item-{{ $item->id }}">
          {{ $item->name }}
      </div>
  @endforeach
  

• Prefer lifecycle hooks like mount(), updatedFoo() for initialization and reactive side effects:

Testing Livewire

<code-snippet name="Testing a Livewire component exists within a page" lang="php">
    $this->get('/posts/create')
    ->assertSeeLivewire(CreatePost::class);
</code-snippet>

=== livewire/v3 rules ===

Livewire 3

Key Changes From Livewire 2

• These things changed in Livewire 2, but may not have been updated in this application. Verify this application's setup to ensure you conform with application conventions.
  • Use wire:model.live for real-time updates, wire:model is now deferred by default.
  • Components now use the App\Livewire namespace (not App\Http\Livewire).
  • Use $this->dispatch() to dispatch events (not emit or dispatchBrowserEvent).
  • Use the components.layouts.app view as the typical layout path (not layouts.app).

New Directives

• wire:show, wire:transition, wire:cloak, wire:offline, wire:target are available for use. Use the documentation to find usage examples.

Alpine

• Alpine is now included with Livewire, don't manually include Alpine.js.
• Plugins included with Alpine: persist, intersect, collapse, and focus.

Lifecycle Hooks

• You can listen for livewire:init to hook into Livewire initialization, and fail.status === 419 for the page expiring:

Livewire.hook('message.failed', (message, component) => {
    console.error(message);
});

});

=== pint/core rules ===

Laravel Pint Code Formatter

• You must run vendor/bin/pint --dirty before finalizing changes to ensure your code matches the project's expected style.
• Do not run vendor/bin/pint --test, simply run vendor/bin/pint to fix any formatting issues.

=== phpunit/core rules ===

PHPUnit Core

• This application uses PHPUnit for testing. All tests must be written as PHPUnit classes. Use php artisan make:test --phpunit <name> to create a new test.
• If you see a test using "Pest", convert it to PHPUnit.
• Every time a test has been updated, run that singular test.
• When the tests relating to your feature are passing, ask the user if they would like to also run the entire test suite to make sure everything is still passing.
• Tests should test all of the happy paths, failure paths, and weird paths.
• You must not remove any tests or test files from the tests directory without approval. These are not temporary or helper files, these are core to the application.

Running Tests

• Run the minimal number of tests, using an appropriate filter, before finalizing.
• To run all tests: php artisan test.
• To run all tests in a file: php artisan test tests/Feature/ExampleTest.php.
• To filter on a particular test name: php artisan test --filter=testName (recommended after making a change to a related file).

=== tailwindcss/core rules ===

Tailwind Core

• Use Tailwind CSS classes to style HTML, check and use existing tailwind conventions within the project before writing your own.
• Offer to extract repeated patterns into components that match the project's conventions (i.e. Blade, JSX, Vue, etc..)
• Think through class placement, order, priority, and defaults - remove redundant classes, add classes to parent or child carefully to limit repetition, group elements logically
• You can use the search-docs tool to get exact examples from the official documentation when needed.

Spacing

• When listing items, use gap utilities for spacing, don't use margins.

Dark Mode

• If existing pages and components support dark mode, new pages and components must support dark mode in a similar way, typically using dark:.

=== tailwindcss/v4 rules ===

Tailwind 4

• Always use Tailwind CSS v4 - verify you're using only classes supported by this version.

=== tests rules ===

Test Enforcement

• Every change must be programmatically tested. Write a new test or update an existing test, then run the affected tests to make sure they pass.
• Run the minimum number of tests needed to ensure code quality and speed. Use php artisan test with a specific filename or filter.

Laravel Starter (based on Laravel 13.x)

Laravel Starter is a Laravel 13.x based simple starter project. Most of the commonly needed features of an application like Authentication, Authorisation, Users and Role management, Application Backend, Backup, Log viewer are available here. It is modular, so you may use this project as a base and build your own modules. A module can be used in any Laravel Starter based project. Here Frontend and Backend are completely separated with separate routes, controllers, and themes as well.

Please let me know your feedback and comments.

Application Demo

Check the following demo project. It is just a straight installation of the project without any modification.

Demo URL: https://laravel.nasirkhn.com

You may use the following account credentials to access the application backend.

User: super@admin.com
Pass: secret

User: user@user.com
Pass: secret

Custom Commands

We have created a number of custom commands for the project. The commands are listed below with a brief about their use of it.

Install / Setup

See the canonical Installation section below for the full setup flow and all supported options for php artisan starter:install.

Update

After pulling changes from the repository, run:

php artisan starter:update

This runs composer update, checks for new module migrations, runs outstanding migrations, and clears all caches.

Create New Module

To create a module use the following command, replacing MODULE_NAME with the name of your module.

php artisan module:build MODULE_NAME

You may want to use the --force option to overwrite an existing module. If you use this option, it will replace all the existing files with the default stub files.

php artisan module:build MODULE_NAME --force

Clear All Cache

php artisan clear-all

or

composer clear-all

This clears application caches including config, route, view, and permission cache. If you prefer Composer scripts, composer clear-all is also available.

Code Style Fix

We are now using Laravel Pint to make the code style stay as clean and consistent as the Laravel Framework. Use the following command to apply CS-Fix.

composer pint

Along with Laravel Pint, we are using prettier to format the blade templates. You can install the prettier extension in your favorite editor. The following command will format the blade templates.

npm run format

npm is the supported package manager for this project. Avoid mixing npm and yarn lockfiles on the same checkout, especially on Windows, because native packages such as esbuild and Tailwind's platform binaries can fail to resolve or unlink cleanly after a mixed install.

If you are intentionally using yarn, remove the existing install state first so Yarn can rebuild it from scratch.

Remove-Item -Recurse -Force node_modules
Remove-Item -Force yarn.lock
yarn cache clean
yarn install
yarn format

Role - Permissions

Several custom commands are available to add and update role-permissions. Please read the Role - Permission Wiki page, where you will find the list of commands with examples.

Features

The Laravel Starter comes with several features which are the most common in almost all applications. It is a template project which means it is intended to be built in a way that it can be used for other projects.

It is a modular application, and some modules are installed by default. It will be helpful to use it as a base for future applications.

• Admin feature and public views are completely separated as Backend and Frontend namespace.
• Major features are developed as Modules. A module like Posts, Comments, and Tags are separated from the core features like User, Role, Permission

Core Features

• User Authentication
• Social Login
  • Google
  • Facebook
  • Github
  • Build in a way adding more is much easier now
• User Profile with Avatar
• Role-Permissions for Users
• Dynamic Menu System
• Language Switcher
• Localization enabled across the project
• Backend Theme
  • Bootstrap 5, CoreUI
  • Fontawesome 6
  • Dark Mode
• Frontend Theme
  • Tailwind
  • Fontawesome 6
  • Dark Mode
• Article Module
  • Posts
  • Categories
  • Tags
  • Comments
  • WYSIWYG editor (laravel-jodit)
  • File browser
• Application Settings
• External Libraries
  • Bootstrap 5
  • Fontawesome 6
  • CoreUI
  • Tailwind
  • Datatables
  • Select2
  • Date Time Picker
  • Jodit WYSIWYG Editor
• Backup (Source, Files, Database as Zip)
• Log Viewer
• Notification
  • Dashboard and details view

Companion Packages

Laravel Starter is built on top of a set of focused, reusable packages that are also available independently for any Laravel application.

Package	Description
nasirkhan/module-manager	Powerful module management with version tracking, migration management, dependency resolution, and full module lifecycle commands (module:status, module:build, module:enable, etc.)
nasirkhan/laravel-cube	Versatile collection of reusable UI Blade components (buttons, modals, cards, forms, navigation, and more) with dual Tailwind CSS and Bootstrap 5 support and built-in dark mode
nasirkhan/laravel-jodit	Integrates the Jodit WYSIWYG editor via a single Blade component (<x-jodit::editor>), with Livewire support and a built-in server-side file browser/uploader
nasirkhan/laravel-sharekit	Reusable Blade-powered social sharing buttons with metadata auto-detection, popup sharing, native Web Share API support, copy-link action, and page-scoped asset loading

User Guide

Installation

This is the single source of truth for installing Laravel Starter from a fresh checkout. You may find more background in the Installation Wiki.

From GitHub Template (recommended)

If you created a new repository from this GitHub template, or cloned it directly:

# 1. Install PHP dependencies
composer install

# 2. Run the interactive setup wizard — handles .env, database, migrations, seeding, and npm assets
php artisan starter:install

Or as a single shortcut after composer install:

composer setup

For a true one-liner from a fresh clone, convenience scripts are included:

# Linux / macOS
bash setup.sh

# Windows (PowerShell)
.\setup.ps1

Both scripts run composer install and then launch php artisan starter:install. Pass any starter:install flags through, e.g. bash setup.sh --demo.

The setup wizard will guide you through environment configuration, database selection, migrations, seeding, and building frontend assets. When finished it prints the app URL and default login credentials.

Available options:

Option	Description
--skip-db	Skip database setup
--skip-seed	Skip database seeding
--skip-npm	Skip npm install and asset build
--demo	Seed with demo data (no prompt)

If you only need to rerun cache clearing after setup, use:

php artisan clear-all

Via Composer create-project

composer create-project nasirkhan/laravel-starter

This runs migrations automatically. Afterwards run the setup wizard to seed and build assets:

php artisan starter:install --skip-db

After creating the new permissions use the following commands to update cached permissions.

php artisan cache:forget spatie.permission.cache

Database Seeding

Two seeder categories are available:

• Essential (always run): users, roles, permissions, menu — AuthTableSeeder, MenuDatabaseSeeder
• Dummy data (optional): posts, categories, tags — disabled via SEED_DUMMY_DATA=false in .env

# Full seed (essential + dummy data)
php artisan migrate:fresh --seed

# Essential data only
php artisan db:seed-essential --fresh

# Add or refresh demo content at any time
php artisan laravel-starter:insert-demo-data
php artisan laravel-starter:insert-demo-data --fresh

For production, set SEED_DUMMY_DATA=false and use --force:

php artisan db:seed-essential --fresh --force

Docker and Laravel Sail

This project is configured with Laravel Sail. You can use all the docker functionalities here. To install using docker and sail:

1. Clone or download the repository
2. Go to the project directory and run composer install
3. Create .env file by copying the .env-sail. You may use the command to do that cp .env-sail .env
4. Update the database name and credentials in .env file
5. Run the command sail up (consider adding this to your alias: alias sail='[ -f sail ] && sh sail || sh vendor/bin/sail')
6. Run the command sail artisan migrate --seed
7. Link storage directory: sail artisan storage:link
8. Since Sail is already up, you can just visit http://localhost:80

Reporting a Vulnerability

If you discover any security-related issues, please send an e-mail to Nasir Khan Saikat via nasir8891@gmail.com instead of using the issue tracker.

Screenshots

Home Page

Login Page

Posts Page

Backend Dashboard

---

---