claude-kit

---

claude-kit packages a battle-tested setup so every Laravel project — and every developer — gets the same guardrails instead of hand-copying config between repos: a Stop-hook + pre-commit quality gate, reusable Claude Code skills, PHPStan level 7 + strict-rules, Pint, Pest with an optional coverage floor, an architecture test suite that actually runs, feature-doc scaffolding, and stack-aware frontend tooling (Vue, React, Livewire, Blade, or none).

Who it's for

• Teams putting Claude Code, Cursor, or GitHub Copilot to work on a Laravel codebase and wanting consistent, enforced conventions.
• Anyone who wants one command for PHPStan + Pint + Pest + git hooks instead of wiring them by hand.
• Projects that need AI coding guardrails an agent can't skip — the same gate runs at commit time, at the end of every Claude turn, and in CI.

Table of contents

• Requirements
• Installation
• What it installs
• Choosing what to install
• The hybrid update model
• The quality gate
• Documentation
• Contributing
• Security
• License

Requirements

• PHP 8.2+
• Laravel 11, 12, or 13
• Claude Code (to use the rules, hooks, and skills)
• A coverage driver (pcov or Xdebug) only if you ask the gate to enforce coverage

Installation

composer require --dev mohamed-ashraf-elsaed/claude-kit
php artisan claude-kit:install

claude-kit itself depends only on Laravel — it will not pull Pint, PHPStan, or a test runner into your project, and it will not move a version you already have. The installer detects your frontend stack (Inertia + Vue, Inertia + React, Livewire, Blade, or API-only), asks which parts to scaffold, works out the exact tooling your answers need, and offers to install it:

The selected tooling is not installed yet: laravel/pint, larastan/larastan, pestphp/pest
Run `composer require --dev laravel/pint larastan/larastan pestphp/pest` now? (yes/no) [yes]

Anything already in your project is left out of that list. Decline it, or run with --no-interaction, and the command is printed for you to run yourself.

[!NOTE] If that command fails on Pest, it is an upstream conflict, not claude-kit. Current Pest releases conflict with phpunit/phpunit newer than 12.5.30, and the Laravel 13 skeleton pins a newer PHPUnit — so composer require --dev pestphp/pest cannot resolve on a fresh Laravel 13 app even with claude-kit uninstalled. Re-running the same command with -W resolves it by letting composer downgrade PHPUnit to 12.5.30. claude-kit never adds -W for you; accepting that downgrade is your decision.

Then:

composer install   # wires the git pre-commit hook
composer lint      # once, to normalize Laravel's shipped files
npm install        # only if a frontend stack was set up

Not published to Packagist yet? Install straight from GitHub by adding this to your composer.json and running composer require --dev mohamed-ashraf-elsaed/claude-kit:dev-main:

{
    "repositories": [
        { "type": "vcs", "url": "https://github.com/mohamed-ashraf-elsaed/claude-kit" }
    ]
}

What it installs

Part	What lands in your project
.claude core	.claude/settings.json (hook wiring + permission allowlist, deep-merged into any existing file), the reusable skills for your stack, and .mcp.json (Laravel Boost).
CLAUDE.md	Short and specific: project identity, the quality gate, the feature-doc rule, and an index of the installed rules — inside claude-kit:begin/end markers, so re-running refreshes it without touching your own additions.
Rules	.claude/rules/ — one file per selected architecture layer, a clean-code rule (strict / balanced / relaxed), a stack-specific frontend rule, and the always-on anti-overengineering + anti-assumption rules. Path-scoped where it makes sense, so they load only when relevant.
Agents	Read-only design-reviewer (output vs the stated design) and docs-reviewer (output vs supplied docs).
Workflow skills	/commit, /deploy (both you-only), /dead-code, /codemap.
Quality gate	phpstan.neon (your level, Larastan and strict-rules toggles), pint.json, a generated tests/Arch/ArchTest.php matching your layers — plus a tests/Arch testsuite added to your phpunit.xml so it actually runs — .githooks/pre-commit, an edit-time PHPStan hook, and merged composer scripts.
Frontend	Stack-matching eslint.config.js / .prettierrc / tsconfig.json, plus merged package.json scripts and devDependencies. Skipped for API-only projects.
Docs	features/_TEMPLATE/ + features/README.md, .editorconfig, .gitattributes.
CI	Generic GitHub Actions tests.yml and lint.yml.

Nothing is clobbered. An identical file is left alone, a file you have edited is asked about (keep / replace / show diff), settings.json and CLAUDE.md are merged rather than replaced, and composer.json / package.json keep your entries. The conventions claude-kit writes are opinionated defaults — read them and adapt them to how your team actually works.

Choosing what to install

claude-kit:install is a fully interactive configurator — it asks what you want rather than assuming:

여기까지가 README 앞부분입니다. 나머지는 원문에서 읽을 수 있습니다. README 전문 보기 ↗