Home

claude-kit

One command sets up any Laravel project for Claude Code — engineering rules, a Stop-hook + pre-commit quality gate, skills, PHPStan/Pint/Pest, feature-doc scaffolding, and stack-aware frontend tooling.

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

---

What you get, at a glance

flowchart LR
    A([php artisan claude-kit:install]) --> B{Interactive<br/>configurator}
    B --> C[.claude/<br/>settings + skills]
    B --> D[CLAUDE.md<br/>engineering rules]
    B --> E[Quality gate<br/>Pint · PHPStan · Pest]
    B --> F[Frontend tooling<br/>ESLint · Prettier · types]
    B --> G[Docs + CI<br/>features/ · workflows]
    C & D & E & F & G --> H([A guarded, consistent project])
    classDef k fill:#6366f1,stroke:#4338ca,color:#fff;
    class A,H k;

Loading

Guides

Page	What it covers
📥 Installation	Install and run it for the first time
⚙️ Usage	The interactive flow, flags, and re-running
🔧 Configuration	Env toggles, the .claude-kit.json manifest, customising
🎨 Frontend stacks	Vue / React / Blade / API-only detection
✅ Quality gate	Pint, PHPStan, Pest, and the three hooks
🧠 Skills	Bundled skills + finding more via skills.sh
🏗️ Architecture	How the package is built (the hybrid model)
🚀 Publishing	Releasing and Packagist
⬆️ Upgrading	Moving between versions
❓ FAQ	Common questions

Three ideas in one minute

• Hybrid updates. Machinery lives in vendor/…/runtime/ and auto-updates via composer update; content (rules, skills, configs) is copied into your repo so you own it.
• One gate, everywhere. The pre-commit hook, Claude's Stop hook, and CI all run the same quality-checks.sh.
• You choose everything. The installer asks what you want — Pint? PHPStan level? test runner? which hooks and skills? — nothing is forced.

Tip

New here? Start with Installation, then skim Usage to see the prompts you'll answer.

---

_{🏠 Home · Installation →}