PHPackages                             adiachenko/starter-kit-laravel - PHPackages - PHPackages  [Skip to content](#main-content)[PHPackages](/)[Directory](/)[Categories](/categories)[Trending](/trending)[Leaderboard](/leaderboard)[Changelog](/changelog)[Analyze](/analyze)[Collections](/collections)[Log in](/login)[Sign up](/register)

1. [Directory](/)
2. /
3. [Framework](/categories/framework)
4. /
5. adiachenko/starter-kit-laravel

ActiveProject[Framework](/categories/framework)

adiachenko/starter-kit-laravel
==============================

The skeleton application for the Laravel framework.

v0.7.0(1mo ago)08MITPHPPHP ^8.4

Since Feb 11Pushed 1mo agoCompare

[ Source](https://github.com/adiachenko/starter-kit-laravel)[ Packagist](https://packagist.org/packages/adiachenko/starter-kit-laravel)[ RSS](/packages/adiachenko-starter-kit-laravel/feed)WikiDiscussions main Synced 1mo ago

READMEChangelogDependencies (26)Versions (8)Used By (0)

Laravel Starter Kit
===================

[](#laravel-starter-kit)

What's Different from the Official Laravel Starter
--------------------------------------------------

[](#whats-different-from-the-official-laravel-starter)

- PHP `>=8.4` baseline with `declare(strict_types=1)` enforced by Pint.
- The default boilerplate is lean and backend/API-friendly rather than frontend-scaffold-heavy.
- `AppServiceProvider` comes preconfigured with useful safeguards like immutable dates and stricter Eloquent.
- Models are unguarded by default because policing request input is not their job.
- Tooling is already wired: Pest (parallel tests), PHPStan + Larastan at max level, and Rector for refactors.
- Tinker is intentionally kept in `require-dev`, not production dependencies, as a safer default.
- Improved testing setup with clear conventions and a dedicated suite for external dependencies.
- Laravel Boost configuration prompts are included during setup, and sensible `.gitignore` rules for Boost are preconfigured. Comes bundled with .ai directory as a starting point for your own AI overrides.
- SQLite is set as the default database, offering a clean, minimal starting point that you can easily customize for your preferred database setup.
- Formatting is consistent out of the box: Pint for PHP and Prettier for everything else.

Installation
------------

[](#installation)

Create application (replace `example-app` with desired project name):

```
composer create-project adiachenko/starter-kit-laravel --prefer-dist example-app
```

> Keep in mind that `composer create-project` already does most of the setup for you. It will install dependencies, create .env file, generate app key, and prompt you to configure Laravel Boost.

Navigate to your project and complete the setup:

```
cd example-app

# Initialize git repo
git init
sh install-git-hooks.sh

# Optionally, scaffold API routes with Sanctum or Passport (add --passport flag)
php artisan install:api
```

Installed Git hooks:

- `pre-commit` runs `composer format`
- `pre-push` runs `composer analyse`

If you use [Fork](https://git-fork.com/) and hooks misbehave, see [this issue](https://github.com/fork-dev/Tracker/issues/996).

Development Commands
--------------------

[](#development-commands)

CommandPurpose`composer test`Run Feature and Unit test suites (`pest --compact --parallel`).`composer test:external`Run the External test suite (`--testsuite=External`).`composer format`Run Laravel Pint and Prettier formatting.`composer analyse`Run static analysis (`phpstan`).`composer refactor`Apply Rector refactors.`composer coverage`Run tests with local coverage (`pest --coverage`).`composer coverage:herd`Run coverage via Laravel Herd tooling.Tests Structure and Conventions
-------------------------------

[](#tests-structure-and-conventions)

The tests are organized into three test suites:

- `tests/Feature`: default starting point for validating application behavior. Test **from the outside in** by calling endpoints directly. Organize feature tests in subfolders by interface type: `Web`, `Api`, or `Mcp` for HTTP endpoints, `Console` for Artisan commands, etc.
- `tests/Unit`: tests for individual classes aligned with `app/` namespaces; strict isolation is not required (using database or involving related classes is acceptable).
- `tests/External`: tests real interactions with external services (no mocking), organized by provider or domain.

If unsure, always start with `Feature` tests and work inward toward `Unit` tests as complexity grows.

Do not place unmocked external integration checks in `Feature` or `Unit`; keep them in `tests/External`.

Test descriptions should follow the pattern: `  [when ] [for ]`.

Additional Folders
------------------

[](#additional-folders)

Not strictly Laravel-official, but adopted as common practices in the community:

- `app/Actions`: invokable classes for encapsulating business logic.
- `app/Data`: data transfer objects (DTOs).
- `app/Enums`: self-explanatory.
- `app/Services`: for calling external services.

PhpStorm Setup
--------------

[](#phpstorm-setup)

Recommended setup for consistent formatting:

- `Settings | Editor | Code Style`: ensure "Enable EditorConfig support" is checked.
- `Settings | PHP | Quality Tools | Laravel Pint`: use ruleset from `pint.json`
- `Settings | PHP | Quality Tools`: set Laravel Pint as external formatter
- `Settings | Tools | Actions on Save`: enable reformat on save
- `Settings | Languages & Frameworks | JavaScript | Prettier`: use automatic config, enable "Run on save", and prefer Prettier config. Include `md` in Prettier file extensions.

VSCode/Cursor Setup
-------------------

[](#vscodecursor-setup)

VSCode and Cursor will automatically detect formatting settings defined in the `.vscode/` folder – no additional setup is needed beyond installing the suggested extensions.

###  Health Score

38

—

LowBetter than 85% of packages

Maintenance90

Actively maintained with recent releases

Popularity4

Limited adoption so far

Community6

Small or concentrated contributor base

Maturity46

Maturing project, gaining track record

 Bus Factor1

Top contributor holds 100% of commits — single point of failure

How is this calculated?**Maintenance (25%)** — Last commit recency, latest release date, and issue-to-star ratio. Uses a 2-year decay window.

**Popularity (30%)** — Total and monthly downloads, GitHub stars, and forks. Logarithmic scaling prevents top-heavy scores.

**Community (15%)** — Contributors, dependents, forks, watchers, and maintainers. Measures real ecosystem engagement.

**Maturity (30%)** — Project age, version count, PHP version support, and release stability.

###  Release Activity

Cadence

Every ~8 days

Total

7

Last Release

47d ago

### Community

Maintainers

![](https://www.gravatar.com/avatar/8d2e8da5aef0dbee0a910f2759dc0ffd36f6925aa32c6b0c95bdffcaf481bf0f?d=identicon)[adiachenko](/maintainers/adiachenko)

---

Top Contributors

[![adiachenko](https://avatars.githubusercontent.com/u/10194667?v=4)](https://github.com/adiachenko "adiachenko (25 commits)")

---

Tags

frameworklaravel

###  Code Quality

TestsPest

Static AnalysisPHPStan, Rector

Code StyleLaravel Pint

### Embed Badge

![Health badge](/badges/adiachenko-starter-kit-laravel/health.svg)

```
[![Health](https://phpackages.com/badges/adiachenko-starter-kit-laravel/health.svg)](https://phpackages.com/packages/adiachenko-starter-kit-laravel)
```

###  Alternatives

[codewithdennis/larament

Larament is a time-saving starter kit to quickly launch Laravel 13.x projects. It includes FilamentPHP 5.x pre-installed and configured, along with additional tools and features to streamline your development workflow.

3691.5k](/packages/codewithdennis-larament)[kompo/kompo

Laravel & Vue.js FullStack Components for Rapid Application Development

11812.4k21](/packages/kompo-kompo)

PHPackages © 2026

[Directory](/)[Categories](/categories)[Trending](/trending)[Changelog](/changelog)[Analyze](/analyze)